Repository navigation
chore: version packages (rc) - #674
Open
github-actions[bot] wants to merge 1 commit into
Open
github-actions[bot] wants to merge 1 commit into
github-actions[bot] wants to merge 1 commit into
Conversation
github-actions
Bot
force-pushed
the
changeset-release/main
branch
2 times, most recently
from
October 31, 2026 03:57
2d7ed4f to
8b9ce07
Compare
github-actions
Bot
force-pushed
the
changeset-release/main
branch
from
October 31, 2026 19:20
8b9ce07 to
7c2901a
Compare
This branch has not been 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.
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.28
Patch Changes
auth: { variables, secrets }(or a remote-onlyapi: { variables, secrets }) had that slot counted as authored, so the deploy train left it unpinned and the auth server (or api) kept following the parent's live config pointer — under a host and auth UI pinned to the child's release. A slot now counts as authored only when it names a code source (production,development,pin,extends,proxy, a bare plugin ref, orui: false); configuration-only entries get the release'sproduction+pinstamped with theirvariables/secretskept. Affected children pick this up on their next deploy after upgrading.data.action: "rejoin-organization". Child apps can configure the joined screen through theonboardauth variable:links.next/links.home(with an{organizationId}placeholder) andlinks.explorefor the success and error panels (defaults stay/build,/dashboard,/explore;next: falsehides the build link), pluscommunity.url, an app endpoint that returns the joined community's page and channels for a "Visit {community}" button and channel links.