Repository navigation
chore: version packages (rc) - #909
Merged
Merged
Conversation
github-actions
Bot
force-pushed
the
changeset-release/main
branch
from
November 20, 2026 13:46
1726f38 to
b12c812
Compare
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.
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 main, this PR will be updated.
mainis currently in pre mode so this branch has prereleases rather than normal releases. If you want to exit prereleases, runchangeset pre exitonmain.Releases
everything-dev@2.0.0-rc.46
Patch Changes
▶phase headers (Preflight → Build → Release → Publish → Verify → Promote) with a consistent ✓/…/✗ line grammar, nearblocks explorer links for every transaction hash, boot-gate polls reporting elapsed time instead of attempt counts, and deploy failures rendered as structured what-happened / why-it-matters / what-to-do blocks keyed off the failed leg. The gas prepayment and signing-key preflight checks now read from the FastNEAR free RPC (NEAR_READ_RPC_URLoverrides) instead of the signing stack's pinned RPC, and their skip warnings name the endpoint and the real error.secrets/connectSrcarray at the same path previously deleted the key entirely (the union helper returnedundefined, which the merge customizer assigned through). The union now always yields an array, restoring associativity and the self-merge fixpoint property of config resolution. Surfaced by a new property-based law suite (tests/unit/merge-properties.test.ts) checking merge associativity, child precedence, parent-null shadowing, idempotence on resolved configs, digest atomicity, and publish-canonicalization invariants (local:targets never publish, seed never publishes).bos status/bos devno longer report false-clean when a check itself fails: the boot composition audit prints what it skipped and why, the deployed-vs-served version check reports an unreachable published config instead of silently vanishing (and is now actually rendered, including the split-brain verdict), and the parent runtime check distinguishes "no published config" from an unreachable registry with the real cause. Device-flow approvals print elapsed-time progress every 30s under aDelegate keyphase header instead of dead air mid-deploy.