Skip to content

Conversation

@dylankelly
Copy link
Contributor

@dylankelly dylankelly commented Jan 7, 2026

Add backporting and patch release workflows

What I did

  • Created backport.yml workflow to automatically backport PRs using labels (e.g., backport release/2.46)
  • Created patch-release.yml workflow for manually triggering patch releases from release branches
  • Updated CONTRIBUTING.md with documentation for:
    • Backporting process using PR labels
    • Patch release workflow for publishing fixes without merging to main
    • Updated release workflow diagram showing patch releases
  • Updated release-please-config.json to support patch releases on release branches

How to test

  • Backporting:
    1. Merge a PR to main or develop
    2. Add label backport release/X.Y to the merged PR
    3. Verify backport workflow creates a new PR targeting the release branch
  • Patch releases:
    1. Merge a backported PR to a release branch
    2. Go to Actions → "Patch Release" → Run workflow
    3. Enter the release branch name
    4. Verify release-please creates a release PR with patch version bump
    5. Merge and verify packages publish with new patch version

Checklist

For all PR's

  • I've added relevant changes to the project Readme if needed
  • I've updated the documentation site as needed
  • I have added tests to cover my changes (not applicable - workflow configuration changes)

For new UI components only

  • I have added a storybook story covering all variants
  • I have checked a11y tab in storybook passes
  • I have added cypress component tests (if the component is interactive)
  • Any events are emitted on the event bus using emitRplEvent

@dylankelly dylankelly merged commit 904f5c6 into main Jan 7, 2026
1 check passed
@dylankelly dylankelly deleted the feature/release-backport branch January 7, 2026 23:30
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.

3 participants