Repository navigation
chore: release 0.6.0 - #134
Merged
Merged
Conversation
The rewrite ships as 0.6.0 rather than 1.0.0. It is a rewrite with a wholly different core, and inbound, webhooks, queues, verification and parsing are still to be reintroduced against it — calling that 1.0 would promise a stability the surface has not earned yet. Docs retargeted accordingly: the migration guide is 0.5 → 0.6, and it no longer tells anyone to pin 0.5 for a driver, because every driver is here. Dependencies are already current — `bun outdated` reports nothing — and the toolchain has no pnpm left in it. The only two mentions remaining are the README offering it as one of four ways a consumer can install the package, and the migration note explaining the change. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01GQAPDWLnDrdYHKhou3Ntvb
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.
Ships the rewrite as 0.6.0, not 1.0.0.
It is a rewrite with a wholly different core, and
inbound,webhook,queue,verifyandparseare still to be reintroduced against it. Calling that 1.0 would promise a stability the surface has not earned yet; 0.6 says what it is.Docs retargeted: the migration guide is now 0.5 → 0.6, and it no longer tells anyone to pin
0.5.xfor a driver, because every driver is here.State of the tree at this tag
isolatedDeclarations, coverage floors, version consistency across three files, export-map parity between npm and JSR, JSR publishability, bundle budgets, ATTWHousekeeping in this PR
Dependencies are already current —
bun outdatedreports nothing.pnpm is fully out of the toolchain. The only two mentions left are the README offering it as one of four ways a consumer can install the package, and the migration note explaining the change.
🤖 Generated with Claude Code
https://claude.ai/code/session_01GQAPDWLnDrdYHKhou3Ntvb