chore: release v5.0.0 - #82
Merged
Merged
Conversation
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #82 +/- ##
=======================================
Coverage 99.71% 99.71%
=======================================
Files 44 44
Lines 1414 1414
Branches 265 265
=======================================
Hits 1410 1410
Misses 4 4
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Harness. 🚀 New features to boost your workflow:
|
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.
Phase 1 of the release process (see RELEASING.md): version bump + CHANGELOG only. Nothing is tagged or published by this PR.
Version
5.0.0was passed explicitly rather than letting release-it compute it. Two reasons:v4.1.0..maincarries a!marker orBREAKING CHANGE:footer, so conventional-commits would have computed4.2.0— but this release is breaking (see below).CHANGELOG was written by hand
The generated section had two defects, both corrected in this PR:
⚠ BREAKING CHANGESsection, for the reason above. Every prior major has one, and this release genuinely breaks custom persistence adapters.feat:/fix:commits so conventional-changelog can no longer list them. Worth using a merge commit or rebase for content PRs next time.The hand-written section documents the three breaking changes (required
WorkflowInstance.definitionVersion; the KyselyWorkflowDatabaseadditions; the required004migration), the features, and two notes — that resolution is unchanged (the stamp is provenance, not pinning) and that correct multi-hop history ordering needsuuidStrategy: "uuidv7".Verification
pnpm run build— clean (ESM + CJS)pnpm test— 604 passed, 3 skipped (integration suites skip withoutDATABASE_URL)pnpm run test:coverage— 99.44 / 97.51 / 100 / 99.66, all four thresholds passpnpm install --frozen-lockfile— succeeds, so Phase 2 won't trip on lockfile drift5.0.0;@duraflows/corepeer re-pinned to^5.0.0in pg, kysely, and nestjsAfter merge
Phase 2 (tag, publish to npm, GitHub release) runs locally from
mainand needsGITHUB_TOKENexported —.release-it.publish.jsonaborts without it.🤖 Generated with Claude Code
https://claude.ai/code/session_011PB7QQawpa1GextDxZrzmV