Repository navigation
Conversation
chore: merge main into dev
chore: merge main into dev
chore: merge main into staging
…-components--qubic-static-api chore(release): 1.29.0-rc.1
feat: add Vitron VTR token metadata
…rocedure-ids fix(smart_contracts): read enum-based procedure ids and update Nostromo
chore: merge main into dev
dev already contains all of main, so one merge promotes both. Conflicts were release-please bookkeeping only: - package.json: took 1.32.0; the rc channel re-bumps it on the next staging release, and its state lives in the staging manifest. - CHANGELOG.md: union - kept 1.32.0 and 1.31.0 from dev and preserved staging's 1.29.0-rc.1 entry, which dev does not have. .release-please-manifest.staging.json keeps staging's 1.29.0-rc.1. All other files match dev exactly.
chore: merge dev (incl. main) into staging
…-components--qubic-static-api chore(release): 1.29.0-rc.2
feat: add Bitget 3 exchange address
The staging rc manifest was last seeded at the release-please migration (1.28.0) and never reseeded since. The prerelease versioning strategy only increments the prerelease counter off the last rc, so every staging release produced another candidate for 1.29.0 (rc, rc.1, rc.2) even though 1.32.0 had already shipped stable. Reseed to the last stable release so the next staging release is a candidate for 1.33.0, exactly as 1.28.0 -> 1.29.0-rc worked at migration time. The strategy itself is kept: it is what appends -rc when the base version is stable. Removing it would produce a plain 1.33.0 with no rc suffix.
fix(release): make staging rc track the stable version line
Only conflict was release-please bookkeeping: - .release-please-manifest.staging.json: took 1.32.0 from dev (the #218 reseed), replacing staging's 1.29.0-rc.2. package.json and CHANGELOG.md keep staging's rc state; the next staging release re-bumps them. All other files match dev exactly.
…-components--qubic-static-api chore(release): 1.33.0-rc
sallymoc
approved these changes
Oct 26, 2026
This branch was successfully deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
No description provided.