Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Updates to core, ui, lightspark-sdk, lightspark-cli #433

Merged
merged 10 commits into from
Oct 22, 2024
Merged

Conversation

github-actions[bot]
Copy link
Contributor

If this change should result in new package versions please add a changeset before merging. You can do so by clicking the link provided by changeset bot below.

GitOrigin-RevId: f46c5464222d9a5f04e0d49a20e6b71fc7a7d811
@github-actions github-actions bot requested a review from a team as a code owner October 19, 2024 00:30
Copy link
Contributor Author

github-actions bot commented Oct 19, 2024

The following public packages have changed files:

Changed Current version
@lightsparkdev/lightspark-cli 0.0.61
@lightsparkdev/lightspark-sdk 1.8.7
@lightsparkdev/core 1.2.5
@lightsparkdev/ui 1.0.13

There are 3 existing changesets for this branch. If additional changes have been made that require different versions for any package simply add another changeset. Any packages that depend on the planned releases will be updated and released automatically in a separate PR.

Each changeset corresponds to an update in the CHANGELOG for the packages listed in the changeset. Therefore, you should add a changeset for each noteable package change that this PR contains. For example, if a PR adds two features - one feature for packages A and B and one feature for package C - you should add two changesets. One changeset for packages A and B and one changeset for package C, with a description of each feature. The feature description will end up being the CHANGELOG entry for the packages in the changeset.

The following releases are planned based on the existing changesets:

Planned releases Update
@lightsparkdev/lightspark-cli patch
@lightsparkdev/core patch
@lightsparkdev/lightspark-sdk patch
@lightsparkdev/ui patch
@lightsparkdev/crypto-wasm patch
@lightsparkdev/oauth patch

Last updated by commit c488cc6

coreymartin and others added 9 commits October 21, 2024 19:08
GitOrigin-RevId: 0df904955c938479249f058ed2eaf6fbcf582cb6
Site and ops fonts aren't working because their main font is
"Montserrat" which is not handled in the font string switch.

GitOrigin-RevId: c5fb234b816e4bd51a54772f80836af5e93429f6
Bumps [secp256k1](https://github.com/cryptocoinjs/secp256k1-node) from
5.0.0 to 5.0.1.
<details>
<summary>Commits</summary>
<ul>
<li><a
href="https://github.com/cryptocoinjs/secp256k1-node/commit/b3f874ff796a041b5b0e3eed343ab2ed265c8fd1"><code>b3f874f</code></a>
5.0.1</li>
<li><a
href="https://github.com/cryptocoinjs/secp256k1-node/commit/9a15fff274f83a6ec7f675f1121babcc0c42292f"><code>9a15fff</code></a>
elliptic: fix key verification in loadCompressedPublicKey</li>
<li><a
href="https://github.com/cryptocoinjs/secp256k1-node/commit/dc37f41f2abfe87853b54bcd7d1b556db41b0c64"><code>dc37f41</code></a>
Update elliptic to 6.5.7 (CVE-2024-42461) (<a
href="https://redirect.github.com/cryptocoinjs/secp256k1-node/issues/206">#206</a>)</li>
<li>See full diff in <a
href="https://github.com/cryptocoinjs/secp256k1-node/compare/v5.0.0...v5.0.1">compare
view</a></li>
</ul>
</details>
<br />

[![Dependabot compatibility
score](https://dependabot-badges.githubapp.com/badges/compatibility_score?dependency-name=secp256k1&package-manager=npm_and_yarn&previous-version=5.0.0&new-version=5.0.1)](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores)

Dependabot will resolve any conflicts with this PR as long as you don't
alter it yourself. You can also trigger a rebase manually by commenting
`@dependabot rebase`.

[//]: # (dependabot-automerge-start)
[//]: # (dependabot-automerge-end)

---

<details>
<summary>Dependabot commands and options</summary>
<br />

You can trigger Dependabot actions by commenting on this PR:
- `@dependabot rebase` will rebase this PR
- `@dependabot recreate` will recreate this PR, overwriting any edits
that have been made to it
- `@dependabot merge` will merge this PR after your CI passes on it
- `@dependabot squash and merge` will squash and merge this PR after
your CI passes on it
- `@dependabot cancel merge` will cancel a previously requested merge
and block automerging
- `@dependabot reopen` will reopen this PR if it is closed
- `@dependabot close` will close this PR and stop Dependabot recreating
it. You can achieve the same result by closing it manually
- `@dependabot show <dependency name> ignore conditions` will show all
of the ignore conditions of the specified dependency
- `@dependabot ignore this major version` will close this PR and stop
Dependabot creating any more for this major version (unless you reopen
the PR or upgrade to it yourself)
- `@dependabot ignore this minor version` will close this PR and stop
Dependabot creating any more for this minor version (unless you reopen
the PR or upgrade to it yourself)
- `@dependabot ignore this dependency` will close this PR and stop
Dependabot creating any more for this dependency (unless you reopen the
PR or upgrade to it yourself)
You can disable automated security fix PRs for this repo from the
[Security Alerts
page](https://github.com/lightsparkdev/webdev/network/alerts).

</details>

Signed-off-by: dependabot[bot] <[email protected]>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
GitOrigin-RevId: e519259cac1cf9136614a4715e26259a64c729db
GitOrigin-RevId: 00b6d504049ab5672147ae53f06fad564c134a84
GitOrigin-RevId: beae699a80ed52f16f9bebe83e8eded623395778
@coreymartin coreymartin changed the title [uma-bridge] New connected bank account indicator Updates to core, ui Oct 22, 2024
@coreymartin coreymartin changed the title Updates to core, ui Updates to core, ui, lightspark-sdk, lightspark-cli Oct 22, 2024
@coreymartin coreymartin merged commit 80c16c1 into main Oct 22, 2024
10 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants