chore(release): v0.21.0#14
Merged
Merged
Conversation
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.
Prepares v0.21.0 across 6 files. The release workflow passed every validation gate and created the tag, but repository rules rejected its direct push to
main; this PR lands that exact tagged commit before publishing.Why
PR #13 made the published
effect-dbruntime Node-native and added supported-version verification. That is a user-facing feature, so the release script selected the next minor version: v0.21.0.The repository release workflow completed build, behavior, type, package, and live integration checks. Its final
git pushwas only partially accepted:v0.21.0was created successfullymainbecause required checks apply to direct pushesThis branch points at the exact commit already referenced by the tag. Merging it restores the intended source history without moving or recreating the tag.
Key Changes
Version:
effect-qbandeffect-dbto 0.21.0effectdbRelease notes:
Mechanical changes:
Risks & Testing Needed
Existing tag:
v0.21.0already points to this commit.→ Do not squash, amend, or recreate the release commit.
Publish state: npm and the GitHub Release are not published yet.
→ Dispatch
Publishwithtag=v0.21.0only after this PR is merged.Repository rules: direct release commits cannot update
mainwithout required checks.→ Merge this PR normally after CI passes; follow up on the workflow design separately if desired.
Not tested:
Build status: release validation passed before the direct push was rejected
Test Plan
bun run build bun test bun run test:types bunx npm pack --dry-run bun run test:integrationExpected:
v0.21.0tag commitRollback
If publishing has started, do not delete or reuse v0.21.0; publish a corrective version instead.