Release 0.13.0 - #857
Open
blove wants to merge 1 commit into
Open
Release 0.13.0#857blove wants to merge 1 commit into
blove wants to merge 1 commit into
Conversation
Run `pnpm run version` (changeset version + chart appVersion sync) on main c075436, consuming the 14 pending patch changesets, then retarget only the lines it added from 0.12.1 to 0.13.0: a minor changeset on the 0.x fixed group would promote every package to 1.0.0. The fixed group of 21 packages and both charts' appVersion go to 0.13.0. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
![github-actions[bot]](https://avatars.githubusercontent.com/in/15368?s=60&v=4){kind=small}
This branch was successfully deployed
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.
Release 0.13.0
This prepares the fixed group of 21 B4.run packages at 0.13.0 from main
980ba8a37. Both charts'appVersionmoves to 0.13.0 (b4-app chart 0.2.21, b4-sandbox-infra chart 0.1.25). It consumes the 14 pending changesets and updates the package and example changelogs. This supersedes #856 (0.12.1).All pending changesets are
patch. The 0.x fixed-group Changesets config promotes aminorchangeset to 1.0.0, so this follows the 0.12.0 pattern (#822): runpnpm run version, then retarget only the lines that command added, from 0.12.1 to 0.13.0 (111 occurrences). Older CHANGELOG sections are untouched. There are no changes to source, the publishing workflow, or the charts beyond the version bump.What ships
editFiletool and rangedreadFile; staged workspaces (sandbox.stagedWorkspaces, source upload plusworkspaceonPOST /threads); read a thread's workspace over HTTP (sandbox.workspaceRead: "http", newthread.workspaceoperation).sandbox.threaddecides each thread's workspace, image and policy once at first admission. A thread can have its own permission allow-list and keeps "Always" grants on the thread's record.nodebuild target now carries the thread access policy in its build. A missing policy file at boot refuses to start instead of serving thread endpoints ungated.responseSchemaoncreateAgentHarness/defineEval; recordings that replay would reject now fail at record time; aimock^1.43.0.EPIPE. The sandboxnetworkdefault is now honest:{ mode: "allow" }with no unenforced denylist.Verification
0.13.0and both charts'appVersionis 0.13.0. No0.12.1remains and no changeset files remain.pnpm build,node scripts/check-docs.mjs(which scans the generated CHANGELOGs),pnpm check:release-inventory,pnpm test:release-integrity,pnpm test:sync-chart-appversion,pnpm verify:typescript-tooling-pack(smoke passed at 0.13.0), andgit diff --check.🤖 Generated with Claude Code