chore: back-merge master into develop before the release - #20
Merged
Conversation
chore: release v0.2.0
chore: release v0.2.3
chore: release v0.2.4
…ts current major (#10) The generated bump took ai across two majors and did not compile; ai and @ai-sdk/* stay where they are and the rest of the update lands. Also migrates biome.json to the 2.5 schema and formats devcontainer.json.
The dependency update went to master directly, so develop never received it and the release PR would not merge. This brings it back: the held-back AI SDK pins, the Biome 2.5 config, and the devcontainer Node bump. The auto-merge resolved package.json to master's 0.3.0, which would have released the version that is already out. Set back to 0.4.0. Co-Authored-By: Claude <noreply@anthropic.com>
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
1 participant
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.
Unblocks the release PR #19, which GitHub reports as conflicting.
The dependency update (#10) was merged straight into
master, sodevelopnever receivedit. Four files diverged:
package.json,bun.lock,biome.json,.devcontainer/devcontainer.json.One thing worth flagging
Git's automatic merge resolved
package.jsonto master's 0.3.0, silently discarding the0.4.0 set for this release. Left alone, the release would have shipped the version that is
already out, and the tag step would have refused it. Restored to 0.4.0.
Everything else is taken as-is from master: the AI SDK held at its current major, Biome on
the 2.5 config, devcontainer Node 26.8.1.
Test plan
bun installagainst the merged lockfilebun run typecheck— cleanbun run lint— no errorsbun run test— 721 pass / 0 failbun run build— succeeds