Skip to content

ci: open one release PR for all plugins, like faustjs - #851

Merged
josephfusco merged 1 commit into
mainfrom
ci/single-release-pr
Oct 26, 2026
Merged

josephfusco merged 1 commit into
mainfrom
ci/single-release-pr

Conversation

@josephfusco

Copy link
Copy Markdown
Member

release-please opens a separate release PR for each plugin (#825, #826, #827, #848 right now). faustjs leaves separate-pull-requests at its default (false), so it gets one release PR with every package listed in it. This does the same.

  • Removes "separate-pull-requests": true from release-please-config.json. release-please then keeps a single chore: release main PR on release-please--branches--main. Each plugin still gets its own version bump, CHANGELOG entry, tag, and GitHub Release, and the PR body has a section per plugin.
  • CONTRIBUTING.md now describes the single PR.

The workflow already handles a PR that bumps several plugins. sync-release-files syncs every plugin whose manifest version changed (#828), and release-plugin runs once per path in paths_released.

After merging

The next push to main opens the combined PR. The per-plugin PRs (#825, #826, #827, #848) stay open with autorelease: pending and need closing by hand. Their changes are in the combined PR.

Use of AI Tools

AI assistance: Yes
Tool(s): Claude Code
Model(s): Claude Opus 5.5
Used for: Assisting with matching the release-please setup to faustjs.

@josephfusco
josephfusco requested review from a team and colinmurphy as code owners October 26, 2026 21:09
@josephfusco
josephfusco merged commit 96f6b19 into main Oct 26, 2026
2 checks passed
@josephfusco
josephfusco deleted the ci/single-release-pr branch October 26, 2026 21:09
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