Skip to content

chore: release v5.0.0 - #82

Merged
camcima merged 1 commit into
mainfrom
chore/release-5.0.0
Aug 18, 2026
Merged

chore: release v5.0.0#82
camcima merged 1 commit into
mainfrom
chore/release-5.0.0

Conversation

@camcima

@camcima camcima commented Aug 18, 2026

Copy link
Copy Markdown
Owner

Phase 1 of the release process (see RELEASING.md): version bump + CHANGELOG only. Nothing is tagged or published by this PR.

Version

5.0.0 was passed explicitly rather than letting release-it compute it. Two reasons:

  1. No commit in v4.1.0..main carries a ! marker or BREAKING CHANGE: footer, so conventional-commits would have computed 4.2.0 — but this release is breaking (see below).
  2. RELEASING.md advises passing the version explicitly regardless.

CHANGELOG was written by hand

The generated section had two defects, both corrected in this PR:

  • No ⚠ BREAKING CHANGES section, for the reason above. Every prior major has one, and this release genuinely breaks custom persistence adapters.
  • The whole release collapsed to a single line, because feat: definition version stamping (workflow versioning phase 1) #81 was squash-merged. RELEASING.md warns about exactly this: squashing collapses the individual 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 Kysely WorkflowDatabase additions; the required 004 migration), the features, and two notes — that resolution is unchanged (the stamp is provenance, not pinning) and that correct multi-hop history ordering needs uuidStrategy: "uuidv7".

Verification

  • pnpm run build — clean (ESM + CJS)
  • pnpm test — 604 passed, 3 skipped (integration suites skip without DATABASE_URL)
  • pnpm run test:coverage — 99.44 / 97.51 / 100 / 99.66, all four thresholds pass
  • pnpm install --frozen-lockfile — succeeds, so Phase 2 won't trip on lockfile drift
  • All packages at 5.0.0; @duraflows/core peer re-pinned to ^5.0.0 in pg, kysely, and nestjs

After merge

Phase 2 (tag, publish to npm, GitHub release) runs locally from main and needs GITHUB_TOKEN exported — .release-it.publish.json aborts without it.

🤖 Generated with Claude Code

https://claude.ai/code/session_011PB7QQawpa1GextDxZrzmV

Copilot AI lite review requested due to automatic review settings August 18, 2026 02:48

Copilot AI left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Copilot was unable to review this pull request because the user who requested the review has reached their quota limit.

@codecov

codecov Bot commented Aug 18, 2026

Copy link
Copy Markdown

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 99.71%. Comparing base (90226ab) to head (dbcb7bd).

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           
Flag Coverage Δ
unit 99.71% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Harness.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
  • 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

@camcima
camcima merged commit d65eb23 into main Aug 18, 2026
6 checks passed
@camcima
camcima deleted the chore/release-5.0.0 branch August 18, 2026 02:50
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