Skip to content

fix(release): harden next workflow and resumable releases - #1

Open
omermorad wants to merge 4 commits into
nextfrom
fix/action-release-reliability
Open

omermorad wants to merge 4 commits into
nextfrom
fix/action-release-reliability

Conversation

@omermorad

Copy link
Copy Markdown
Contributor

Summary

  • Use next, Conventional Commit PR titles, reviewed squash-only merges, Node 22+ development, GitHub Node 24 Action runtime, and MIT.
  • Require sufficient changeset coverage, paginate changed files, and fail clearly for missing governance engines.
  • Retry incomplete releases without skipping missing releases or assets, tag the triggering commit explicitly, and propagate authorization failures.
  • Regenerate version branches with a force-with-lease guard and commit only version-owned paths.
  • Backport malformed-YAML version sync through a checked-in pnpm patch; rebuild the bundled Action without publishing a dependency.
  • Documentation uses the existing v0.1.0-dev.14 tag, not a SHA or nonexistent stable tag.

Validation

Typecheck, 22 tests (including real local Git integration), build, and reproducible bundle verification pass.

Approval boundary

No versions or tags were created or moved, and nothing was published. Existing tagged Action versions do not contain these fixes. Ask Omer before any release.

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.

1 participant