chore: prepare 1.4.5 release#91
Merged
Merged
Conversation
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.
Summary
Prepare the
1.4.5patch release for the Copilot tool-guidance upgrade.This release ships the generated Copilot guidance changes that make skill loading and tool usage task-triggered instead of ambient. It also refreshes every version-bearing release surface to
1.4.5, adds the dedicated release note, and updates the philosophy history for the patch.Highlights
parallel-exploration,systematic-debugging,test-driven-development,verification-before-completion).github/*artifacts with the updated generator contract1.4.5release surfaces: manifests, lockfiles, changelog, release note, and philosophy entrypackages/vscode-hivewhere a partialhive-coremodule mock poisoned later testsRelease Notes
The GitHub Release body should come from
docs/releases/v1.4.5.md.Validation
PATH="$HOME/.bun/bin:$PATH" node --test release-artifacts.test.mjsPATH="$HOME/.bun/bin:$PATH" bun test src/providers/sidebarProvider.test.ts src/tools/merge.test.tsPATH="$HOME/.bun/bin:$PATH" bun testinpackages/vscode-hivePATH="$HOME/.bun/bin:$PATH" bun run release:checkNotes
NPM_KEY,VSCE_PAT) in GitHub Actions.npm whoami/vsce verify-pat, so the CI rehearsal and tag-triggered workflow are the meaningful release-time gates here.