Skip to content

feat: multi-branch release PRs #64

@decofe

Description

@decofe

Support creating separate release PRs per branch, so patch releases on older versions can coexist with the main release train.

Example: foundry ships v1.6.0 from master, but also patches v1.5.x from a release/v1.5 branch. The action should create independent release PRs:

  • changelog-release/master → v1.6.0
  • changelog-release/release-v1.5 → v1.5.2

The action already accepts a branch input — this could be extended to derive the branch name from the trigger branch, e.g. changelog-release/${{ github.ref_name }}.

Changelog entries on each branch would be independent.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions