chore(release): v1.5.0 #85
No reviewers
Labels
No labels
already-shipped
bug
documentation
duplicate
enhancement
good first issue
help wanted
in progress
invalid
needs-decision
proposal
question
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: crenshawdev/cadence#85
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "cadence/v1.5.0"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Cuts v1.5.0. Bumps
.claude-plugin/plugin.json1.4.1 → 1.5.0 and dates the changelog section.Milestone is 0 open / 4 closed: #64, #68, #74, #75.
One thing the tool got wrong
release-bump.mjs bumpscaffolded## [1.5.0] - 2026-07-28below the## [Unreleased]section rather than promoting its contents into it. Left alone, v1.5.0 would have shipped with empty release notes while all four entries continued to read as unreleased. Promoted by hand here; filing the tool behaviour separately so the next release doesn't hit it.Also adds the
[1.4.1]link reference at the bottom, which was omitted when that release went out.Verification
node --test cadence-core/bin/*.test.mjs→ 745 pass, 0 failnode cadence-core/bin/self-verify.mjs→ok:trueTag is cut after this merges, on
main, not from this branch.