chore: version packages#220
Merged
Merged
Conversation
df10c75 to
387e973
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
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.0
Minor Changes
16f6bb8: Stop a run from the dashboard
The dashboard now has a Stop button that interrupts the running build from the browser, instead of only from the terminal. It POSTs to a new
/stoproute that aborts the run'sAbortSignal, whichrunFrameworkchecks between phases and the driver honours mid-turn (it kills the current agent turn). The run ends cleanly as stopped (not failed): the CLI prints■ Stoppedand exits 0, the dashboard shows a stopped status, and the persisted run recordsstatus: "stopped"so--resumeshows it that way.startDashboardgains anonStopoption (wire it tocontroller.abort()); the page hides the button when no stop handler is wired (e.g. a read-only--resumeview). Theendevent gained an optionalstoppedflag.Part of Epic: The AI framework — turnkey end-to-end AI orchestration for building software (web-app first) #110 (first interactive slice of AI framework: presentation layer — headless server + CLI/web chat UIs #165's web client). Closes Dashboard: a Stop button to interrupt the running build #218.
Patch Changes
c7eae83: Label the dashboard session link honestly
Our runs are headless, which is deliberately not Remote-Controlled, so the default
https://claude.ai/codelink is a generic entry point, not a live per-run session. The dashboard now labels it Open Claude Code instead of "live session"; the "live session" label is kept only for a real user-supplied--session-link. The real session id (the local transcript id, usable withclaude --resume) is still shown.The README's session section is rewritten to be accurate: to steer a session live in the browser you start your own interactive
claude auth login+claude --remote-control --name <run>session and open it from claude.ai/code, which is a separate process from an orchestration run. Corrects the overpromise from Live claude.ai/code session link via Remote Control #212. Closes Label the dashboard session link honestly + document the Remote Control steer path #221.@gemstack/example-framework-demo@0.0.2
Patch Changes
@gemstack/example-framework-discovery@0.0.2
Patch Changes