Skip to content

chore: prep CHANGELOG for v0.9.4 release - #1042

Merged
bradygaster merged 1 commit into
mainfrom
squad/release-0.9.4-changelog
Apr 25, 2026
Merged

chore: prep CHANGELOG for v0.9.4 release#1042
bradygaster merged 1 commit into
mainfrom
squad/release-0.9.4-changelog

Conversation

@bradygaster

Copy link
Copy Markdown
Owner

This PR converts the [Unreleased] section in CHANGELOG.md to [0.9.4] with today's date (2026-04-25).

Why This Matters

PR #1023 bumped the version to 0.9.4 across all package.json files, but the CHANGELOG wasn't updated. The release automation workflow (squad-release.yml) requires a CHANGELOG entry matching the version before it will proceed.

What Happens Next

Once this PR is merged to main, the squad-release.yml workflow will:

  1. Validate the ## [0.9.4] CHANGELOG entry
  2. Create a git tag v0.9.4
  3. Create a GitHub Release
  4. Trigger squad-npm-publish.yml to publish to npm @latest

Ready for Brady to review and merge.

Closes the gap from PR #1023 where version was bumped but CHANGELOG wasn't updated.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
@bradygaster
bradygaster merged commit e7ddc01 into main Apr 25, 2026
12 checks passed
bradygaster added a commit that referenced this pull request Apr 25, 2026
Adds battle-tested knowledge from the v0.9.4 release session:
- GITHUB_TOKEN event propagation limitation and manual workaround
- Root package.json must match sub-package versions
- CHANGELOG.md version entry validation gate
- Lockfile integrity check workspace package handling
- Prebuild version bump local dev fix

PRs #1042, #1043, #1044 cited as source evidence.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
@bradygaster
bradygaster deleted the squad/release-0.9.4-changelog branch August 8, 2026 08:43
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants