Repository navigation
chore: version packages (rc) - #307
Merged
Merged
Conversation
github-actions
Bot
force-pushed
the
changeset-release/main
branch
5 times, most recently
from
October 9, 2026 18:08
d240466 to
96131cf
Compare
This was referenced Oct 9, 2026
github-actions
Bot
force-pushed
the
changeset-release/main
branch
from
October 9, 2026 19:05
96131cf to
756902e
Compare
elliotBraem
added a commit
that referenced
this pull request
Oct 9, 2026
* fix(ci): stop changeset release PRs from failing structurally PR #307 (chore: version packages) failed three checks that cannot pass on a release PR by construction: - Runtime image smoke boots identity-driven against the published config, so it compares the PR's framework train against bundles the last deploy published — a deploy-parity check the deploy train (with its bos mf check gate) owns post-merge. Skip it on changeset-release/main; the image's self-contained boot path stays covered by the regression browser start:* modes. - init.full resolved better-near-auth from npm, where the bumped rc version does not exist until publish. Pack it as a third framework tarball so child installs stay hermetic. - intent stale flags the version-marker drift every release PR creates by construction; skip the PR-time gate there — markers are reconciled by the post-publish review flow. Also: assert in container-build that every built remote stamps the same every-plugin train as the framework package (fails the build before staging/boot instead of 503-ing at smoke), and decouple two unit tests from the live framework version. * refactor: apply review findings — loop tarball copies, uniform train-assert paths - framework-packages.ts: the stage-pack-then-copy pattern for the two dependency framework packages is now one loop, so pack ordering (everything-dev consumes the transitive copies) is structural instead of incidental - container-build.ts: assertFederationTrain callers all pass root-relative dist paths the same way, and a train mismatch now lists the dists already checked * fix(regression): unbreak container-build — hoist authWorkspace, extract typed helpers The review-driven assertion referenced authWorkspace outside the if-block where it was declared; the Docker dist-builder stage crashed with a ReferenceError after all builds succeeded, failing every image-building job (runtime image smoke, regression browser/http start modes). scripts/ is covered by no workspace typecheck, so only the Docker runtime caught it. - hoist the auth app-slot derivation to module level and share it between build() and stage() (stage() duplicated the same expression) - extract resolveAuthWorkspace + checkFederationTrain into typed package code (packages/everything-dev/src/federation-train.ts) with unit tests — the orchestrator keeps only a thin throwing wrapper that accumulates the checked-dists list - drop the script's local readBuildReport duplicate in favor of the package helper (schema-validated) Verified by running scripts/regression/container-build.ts locally: all 7 dists stamp every-plugin@2.10.1 and staging completes.
github-actions
Bot
force-pushed
the
changeset-release/main
branch
2 times, most recently
from
October 9, 2026 21:17
09f71f4 to
6efb9a2
Compare
github-actions
Bot
force-pushed
the
changeset-release/main
branch
from
October 9, 2026 21:20
6efb9a2 to
e7aaa4c
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
1 participant
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
better-near-auth@2.0.0-rc.0
every-plugin@3.0.0-rc.0
everything-dev@2.0.0-rc.0
@everything-dev/auth-plugin@2.0.0-rc.0
api@1.1.0-rc.0
@every-plugin/template@1.4.0-rc.0
@everything-dev/proposals-plugin@1.2.0-rc.0
@everything-dev/registry-plugin@1.5.0-rc.0
@everything-dev/votes-plugin@1.2.0-rc.0
@everything-dev/ai-plugin@0.1.1-rc.0
host@2.0.0-rc.0
ui@2.0.0-rc.0