ci: release packages - #36
Conversation
|
@coderabbitai review |
commit: |
41edd69 to
2153f5a
Compare
|
@coderabbitai review |
2153f5a to
9ef59fe
Compare
|
@coderabbitai review |
1 similar comment
|
@coderabbitai review |
✅ Action performedReview finished.
|
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (11)
💤 Files with no reviewable changes (5)
📝 WalkthroughWalkthroughThis PR prepares release metadata for the Node SDK, the main application, and the VS Code extension. It adds changelog entries, updates package versions, adds one changeset, and removes superseded changesets. ChangesRelease metadata
Estimated code review effort: 2 (Simple) | ~10 minutes Possibly related PRs
🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
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
@pythoughts/pythinker-code@0.12.0
Minor Changes
#35
2ce6b5e- Show the plan before a Dynamic Workflow runs, and let a good one be saved as a commandManual mode used to approve every
DynamicWorkflowcall outright. That approvalonly ever fired in manual mode — auto and yolo approve earlier in the chain — so
the one mode whose purpose is to ask was the one mode that never saw what it was
agreeing to. A
DynamicWorkflowcall in manual mode now asks, and the approvalcarries the fan-out: how many subagents, the task list, the prompt template, the
worker model, and the summed size of the prompts about to be sent. "Approve for
this session" is keyed to that workflow's description rather than granting every
future
DynamicWorkflowcall./workflow save <name>writes the last run back out as a skill under.pythinker-code/skills/, so a fan-out that worked can be re-run by name.#38
44efbc7- Let a release declare a minimum supported version, so a client below it is offered the update without waiting for its staged rollout batch.#38
44efbc7- Show update availability and live download progress in the status row under the prompt, replacing the startup banner chip that was computed once and never refreshed.Patch Changes
#37
12069a8- Stop offering updates to versions that were never published: the update channel now advertises only the release that is actually available for download.#38
44efbc7- Stop offering an update with no build for the running platform, give every installer network call a timeout, expire a stale install lease instead of blocking updates forever, and say which version is installing and why a failed one stopped retrying.@pythoughts/pythinker-code-sdk@0.13.0
Minor Changes
#35
2ce6b5e- Show the plan before a Dynamic Workflow runs, and let a good one be saved as a commandManual mode used to approve every
DynamicWorkflowcall outright. That approvalonly ever fired in manual mode — auto and yolo approve earlier in the chain — so
the one mode whose purpose is to ask was the one mode that never saw what it was
agreeing to. A
DynamicWorkflowcall in manual mode now asks, and the approvalcarries the fan-out: how many subagents, the task list, the prompt template, the
worker model, and the summed size of the prompts about to be sent. "Approve for
this session" is keyed to that workflow's description rather than granting every
future
DynamicWorkflowcall./workflow save <name>writes the last run back out as a skill under.pythinker-code/skills/, so a fan-out that worked can be re-run by name.pythinker-code@0.8.6
Patch Changes
2ce6b5e]:Summary by CodeRabbit
New Features
/workflow save <name>to save the latest workflow run as a reusable skill.Bug Fixes
Release Updates