Repository navigation
chore: version packages (rc) - #633
Merged
Merged
Conversation
github-actions
Bot
force-pushed
the
changeset-release/main
branch
from
October 27, 2026 13:28
fa2f836 to
5b5f009
Compare
This was referenced Oct 27, 2026
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.25
Patch Changes
1e43560: Dev-boot readiness probes no longer wedge:
probeHttpOkawaitedfetchRaw's nestedEffect.runPromisefrom inside the probe fiber, which intermittently stalled the boot until the 90s probe deadline. The probe (and the host-manifest fetch) now run Effect-native with the same deadline and fail-loud semantics. Also: the dev session's graceful-shutdown force backstop is a forkedEffect.sleepfiber (forkDetach) instead of a rawsetTimeout, and a new unit suite (tests/unit/dev-session-processes.test.ts) drives the realrunDevSessionagainst real detached children and watcher grandchildren to lock the process-death contract at unit speed.The Go framework regression suite boots the confined death-contract fixture (
tests/regression/fixtures/death-contract— a minimal authored config whose five services are fake node servers) for every test but one, cutting the suite's boots from 60–120s of full-stack webpack each to ~4s (the orphan test went 213s → 4.6s); the remaining full-stack boot (sigterm) keeps proving the real rspack/rsbuild watcher shape dies. CI runs the suite with two stack slots instead of serial and a 12-minute timeout instead of 35 — the RAM-saturation failure class is gone.ac9f906: Let a plugin entry set
ui: falseto drop the ui attached from the app it extends. A consumer of another app's plugin otherwise loads that app's whole UI on every page, and two core UI containers both nameduicollide on the page (Plugin entries that extend another app pull in that app's UI, and every core UI container is namedui#636).