Skip to content

chore(release): v0.21.0#14

Merged
relsunkaev merged 1 commit into
mainfrom
release/v0.21.0
Jul 23, 2026
Merged

chore(release): v0.21.0#14
relsunkaev merged 1 commit into
mainfrom
release/v0.21.0

Conversation

@relsunkaev

Copy link
Copy Markdown
Owner

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-db runtime 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 push was only partially accepted:

  • v0.21.0 was created successfully
  • the release commit was rejected from main because required checks apply to direct pushes
  • publish was not dispatched

This 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:

  • bumps the workspace to 0.21.0
  • bumps effect-qb and effect-db to 0.21.0
  • updates the CLI version reported by effectdb
  • updates workspace versions in the Bun lockfile

Release notes:

  • records the Node-native CLI runtime
  • records Effect Platform filesystem, path, crypto, and terminal boundaries
  • records level-aware Effect CLI logging
  • records Node 22/24 packed and live integration coverage

Mechanical changes:

  • generated by the repository release script
  • no source behavior changed beyond the version string

Risks & Testing Needed

Existing tag: v0.21.0 already 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 Publish with tag=v0.21.0 only after this PR is merged.

Repository rules: direct release commits cannot update main without required checks.
→ Merge this PR normally after CI passes; follow up on the workflow design separately if desired.

Not tested:

  • nothing beyond the release workflow's existing platform scope

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:integration

Expected:

  • package and CLI versions report 0.21.0
  • changelog contains the 0.21.0 section
  • the branch head equals the peeled v0.21.0 tag commit

Rollback

git revert <release-merge-commit>

If publishing has started, do not delete or reuse v0.21.0; publish a corrective version instead.

@relsunkaev
relsunkaev merged commit 8dcfb3f into main Jul 23, 2026
5 checks passed
@relsunkaev
relsunkaev deleted the release/v0.21.0 branch July 23, 2026 01:05
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant