chore: support release branches in CI workflows#111
Merged
jrichter1 merged 1 commit intoJun 10, 2026
Merged
Conversation
subhashkhileri
force-pushed
the
workflow/support-release-branches
branch
2 times, most recently
from
653246a to
9dd2530
Compare
- publish-npm.yml: trigger on release-* branches, publish with branch name as npm dist-tag so `latest` stays on main - pr-build-and-check.yml: accept PRs targeting release-* branches, use dynamic base ref instead of hardcoded origin/main Assisted-by: Claude Code Co-Authored-By: Claude Code
subhashkhileri
force-pushed
the
workflow/support-release-branches
branch
from
9dd2530 to
f9dc6a9
Compare
2 tasks
jrichter1
approved these changes
Jun 10, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
release-*branches. Release branches publish with the branch name as the npm dist-tag (e.g.,release-1.10) solateststays pinned tomain.release-*branches. Replace hardcodedorigin/mainwith dynamicorigin/${{ github.base_ref }}(via env vars) so version-check and docs-check compare against the correct base branch.This is needed to support the
release-1.10branch for RHDH 1.10 E2E test utils releases (1.10.xversioning), independent ofmainwhich uses2.xversioning for RHDH 2.1+.Test plan
main)release-1.10and verify PR checks work against the release branchAssisted-by: Claude Code