Search for releases in GITHUB_BASE_REF if possible #2096
Conversation
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
Contributor
There was a problem hiding this comment.
Pull request overview
Fixes incorrect “previous release” selection in PR builds by using the PR base branch (when available) instead of the PR merge ref name, aligning release lookup with the intended target branch (Issue #2094).
Changes:
- Use
GITHUB_BASE_REFas the release-lookup branch when present; otherwise fall back toGITHUB_REF_NAME. - Add release note entry for Issue #2094.
Reviewed changes
Copilot reviewed 2 out of 2 changed files in this pull request and generated no comments.
| File | Description |
|---|---|
| RELEASENOTES.md | Documents the fix for Issue #2094 in the release notes. |
| Actions/RunPipeline/RunPipeline.ps1 | Adjusts previous-release lookup to prefer the PR base branch context. |
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
mazhelez
approved these changes
Jan 23, 2026
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.
❔What, Why & How
Related to issue: #2094
When AL-Go tries to download the latest release it will look in a specific branch. Currently, we use whatever is contained in GITHUB_REF_NAME as the branch but this doesn't always work for pull requests. If you use the "pull_request" trigger then GITHUB_REF_NAME will be the name of the merge branch when it should be the name of the base branch.
Suggested fix: Just use the base branch whenever possible (https://docs.github.com/en/actions/reference/workflows-and-actions/contexts). If it's not available, use the ref_name.
✅ Checklist