chore: version packages#227
Merged
Merged
Conversation
github-actions
Bot
force-pushed
the
changeset-release/main
branch
4 times, most recently
from
e2ef9b1 to
4670188
Compare
github-actions
Bot
force-pushed
the
changeset-release/main
branch
from
4670188 to
fc28010
Compare
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.
This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to main, this PR will be updated.
Releases
@gemstack/framework@0.5.2
Patch Changes
1d3ce64: Fix the Claude Code driver treating a non-zero agent exit as success when the agent had already streamed some text. A crash mid-build now fails the turn (surfacing stderr or the partial text) instead of resolving as a result the loop can score production-grade.
45b13b2: Default the CLI to bypassPermissions so the headless loop can build/verify
Every framework turn is a headless
claude -pinvocation, which can't answer aninteractive approval. The driver's library default (
acceptEdits) auto-approvesedits but not Bash, so installs/builds/tests were silently denied: the
production-grade checklist tried
npm run build/ dev-boot, hit "Build needsinteractive approval which isn't available," failed pass 1 as "could not be
executed this session," and the loop ground on listing blockers it couldn't
verify.
The
frameworkCLI now defaults its Claude Code driver tobypassPermissionssothe full loop (install, build, test, dev-boot) runs unattended and the checklist
verifies for real. This is a permissive default appropriate to a headless
autonomous builder;
--permission-mode <mode>still overrides it (e.g.--permission-mode acceptEditsfor the old, conservative behavior), and--dangerously-skip-permissionsstill takes precedence. TheClaudeCodeDriverlibrary default is unchanged (still
acceptEdits); only the CLI opts up.Closes Headless driver defaults to acceptEdits, so the checklist can't build/verify the app #225.
1259282: Fail closed when a checklist reply omits the required
{ blockers }verdict. A verdict-less reply was scored as empty-blockers (production-grade) and stopped the loop; it now surfaces a blocker so the loop re-prompts instead of declaring the app done off an unverifiable reply.