Skip to content

release: 0.7.0, bool.files goes stable - #31

Merged
HomemadeToast57 merged 1 commit into
mainfrom
jack/release-0.7.0
Sep 18, 2026
Merged

HomemadeToast57 merged 1 commit into
mainfrom
jack/release-0.7.0

Conversation

@HomemadeToast57

Copy link
Copy Markdown
Collaborator

Promotes the three 0.7.0-next prereleases to stable 0.7.0. No code change: version bump plus one consolidated changelog entry.

Release order

  1. Merge this.
  2. Publish a GitHub release tagged v0.7.0 from main. The publish workflow reads the version, sees no prerelease suffix, and publishes to latest.
  3. Confirm with npm view bool-sdk@latest version before merging codehs/bool#1263, which seeds ^0.7.0. That PR merging first would break project creation: the sandbox resolves the range on every boot.

Verification

  • bun run typecheck, bun test (207 pass), bun run build

🤖 Generated with Claude Code

Promote 0.7.0-next.0 through -next.2 to stable with no code change. The
platform's bool-files rollout seeds ^0.7.0 for every new v2 project, and
a caret range only resolves what is on the latest tag, so this release
has to land on npm before that platform change merges.

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
@HomemadeToast57
HomemadeToast57 merged commit d07da36 into main Sep 18, 2026
3 checks passed
@HomemadeToast57
HomemadeToast57 deleted the jack/release-0.7.0 branch September 18, 2026 21:40
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