Skip to content

fix: use separate release PRs per component#28

Merged
peter-svensson merged 1 commit intomainfrom
fix/separate-release-prs
Mar 9, 2026
Merged

fix: use separate release PRs per component#28
peter-svensson merged 1 commit intomainfrom
fix/separate-release-prs

Conversation

@peter-svensson
Copy link
Copy Markdown
Member

Summary

  • Add separate-pull-requests: true to release-please config
  • Each component (root Go module, tck, specverify, typescript) gets its own release PR instead of one combined PR

Test plan

Each Go module and the TypeScript package get their own release PR,
allowing independent review and merge of each component's release.
@peter-svensson peter-svensson enabled auto-merge (squash) March 9, 2026 19:51
@peter-svensson peter-svensson disabled auto-merge March 9, 2026 19:52
@peter-svensson peter-svensson merged commit 0c0f594 into main Mar 9, 2026
5 checks passed
@peter-svensson peter-svensson deleted the fix/separate-release-prs branch March 9, 2026 19:52
@codecov
Copy link
Copy Markdown

codecov Bot commented Mar 9, 2026

Codecov Report

✅ All modified and coverable lines are covered by tests.

📢 Thoughts on this report? Let us know!

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