Repository navigation
changesets: Release / Deploy (v2) - #1037
0xsequence-changesets-release-bot[bot] wants to merge 1 commit into
Conversation
Codex Review SummaryThis comment shows the latest Codex review activity on this pull request.
ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings. |
![chatgpt-codex-connector[bot]](https://avatars.githubusercontent.com/in/1144995?s=60&v=4){kind=small}
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 146231c925
ℹ️ About Codex in GitHub
Codex has been enabled to automatically review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".
| @@ -1 +1 @@ | |||
| export const VERSION = '2.3.28' | |||
| export const VERSION = '2.3.47' | |||
There was a problem hiding this comment.
When this release is merged, @0xsequence/provider, 0xsequence, and the other bumped packages become 2.3.48, but this shared runtime version remains 2.3.47 because @0xsequence/core and the rest of the linked package set were not bumped. Provider transports send this constant as clientVersion, so 2.3.48 clients will identify themselves as 2.3.47; additionally, ci:stage-release skips already-published 2.3.47 packages, contrary to the PUBLISHING.md invariant that every package is staged at one version. Include core and the remaining linked packages in the 2.3.48 release so the runtime metadata and staged package set agree.
Useful? React with 👍 / 👎.
146231c to
2341fb9
Compare
This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to v2, this PR will be updated.
Releases
0xsequence@2.3.48
Patch Changes
ae4d243,8b23a52]:@0xsequence/account@2.3.48
Patch Changes
ae4d243,8b23a52]:@0xsequence/auth@2.3.48
Patch Changes
ae4d243]:@0xsequence/guard@2.3.48
Patch Changes
@0xsequence/migration@2.3.48
Patch Changes
@0xsequence/network@2.3.48
Patch Changes
8b23a52]:@0xsequence/provider@2.3.48
Patch Changes
8b23a52]:@0xsequence/react-native@2.3.48
Patch Changes
@0xsequence/relayer@2.3.48
Patch Changes
8b23a52Thanks @0xPolygonBot! - Update generated relayer RPC client to the latest relayer schema, adding aGetMetaTxnStatusmethod@0xsequence/sessions@2.3.48
Patch Changes
#1036
ae4d243Thanks @taylanpince! - Throw a descriptive error when the Arweave GraphQL gateway returns a non-2xx response, instead of failing to parse an HTML error page as JSONUpdated dependencies []:
@0xsequence/waas@2.3.48
Patch Changes
@0xsequence/waas-ethers@2.3.48
Patch Changes
@0xsequence/wallet@2.3.48
Patch Changes
8b23a52]: