Repository navigation
chore(release): prepare CHANGELOG for v0.13.0 - #1885
Conversation
🛫 PR Readiness Check
PR Scope: 🔧 Infrastructure
|
| Status | Check | Details |
|---|---|---|
| ✅ | Single commit | 1 commit — clean history |
| ✅ | Not in draft | Ready for review |
| ✅ | Branch up to date | Up to date with dev |
| ❌ | Copilot review | No Copilot review yet — it may still be processing |
| ✅ | Changeset present | CHANGELOG.md edit found |
| ✅ | Scope clean | No .squad/ or docs/proposals/ files |
| ✅ | No merge conflicts | No merge conflicts |
| ❌ | Copilot threads resolved | 1 unresolved Copilot thread(s) — fix and resolve before merging |
| ✅ | CI passing | All checks passing |
Files Changed (1 file, +26 −0)
| File | +/− |
|---|---|
CHANGELOG.md |
+26 −0 |
Total: +26 −0
This check runs automatically on every push. Fix any ❌ items and push again.
See CONTRIBUTING.md and PR Requirements for details.
🟢 Impact Analysis — PR #1885Risk tier: 🟢 LOW 📊 Summary
🎯 Risk Factors
📦 Modules Affectedroot (1 file)
This report is generated automatically for every PR. See #733 for details. |
There was a problem hiding this comment.
🟡 Changes recommended
The new v0.13.0 notes appear to duplicate an item already listed under v0.12.0, which risks publishing inaccurate/confusing release notes.
Once you've addressed the issues Copilot identified, you can request another Copilot review.
Pull request overview
Promotes the CHANGELOG.md [Unreleased] section into a new v0.13.0 release entry dated 2026-08-25, to satisfy the release workflow gate that requires a ## [0.13.0] header before promoting dev → preview → main.
Changes:
- Added a new
## [0.13.0] - 2026-08-25section with release notes grouped under Added/Changed/Fixed. - Left
[Unreleased]in place as the top placeholder for future entries.
File summaries
| File | Description |
|---|---|
| CHANGELOG.md | Adds the 0.13.0 release section needed for the promote/release pipeline gate. |
Review details
- Files reviewed: 1/1 changed files
- Comments generated: 1
- Review effort level: Lite
💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.
| - (sdk) `resolveSquadState()` now passes `rootDir: paths.teamDir` to `FSStorageProvider`, so the path-traversal guard actually validates state writes; also fixes `resolveSquadPaths()` treating `config.teamRoot: "."` as remote mode, which pointed `teamDir` one level above `.squad/`; fixes #1555. | ||
| - (sdk) `parseAzureDevOpsRemote()` now decodes percent-encoded characters in org/project/repo segments for all three URL formats (`dev.azure.com`, SSH, legacy `visualstudio.com`); fixes #1526. | ||
| - (sdk) Add `"max"` to `SquadReasoningEffort` and `VALID_REASONING_EFFORTS` to match Copilot SDK 1.0.9. |
Promote [Unreleased] entries to [0.13.0] from 15 pending changesets. Required by squad-promote.yml validate gate before dev -> main promote. Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
445a02b to
038b9a7
Compare
What
Promotes
[Unreleased]to[0.13.0] - 2026-08-25inCHANGELOG.md, compiled from 15 pending changesets.Why this is required
squad-promote.ymlvalidatesgrep -q "## [$VERSION]" CHANGELOG.mdbefore mergingpreview → main. Without this entry the promote workflow fails andv0.13.0cannot ship.Merge order
devdevworkflow_dispatch,dry_run: false) →dev → preview → mainsquad-release.ymlauto-fires → tagv0.13.0+ GitHub Release createdsquad-npm-publish.ymlfires onrelease: published→@bradygaster/squad-cli@0.13.0on npmnpm view @bradygaster/squad-cli@0.13.0 versionVersion determination
0.12.0v0.12.0package.jsonondev0.13.0(bumped in #1705)0.13.0(highest bump:minor, fromsquad-health+scribe-archival-integrity)No version file changes are needed —
devis already at0.13.0.No automation changes
This PR touches only
CHANGELOG.md. The existing release path (squad-promote.yml→squad-release.yml→squad-npm-publish.yml) is used unchanged.