fix: stop defaulting setup-ref/setupRef to the frozen v1 tag - #117
Merged
Conversation
fengmk2
force-pushed
the
fix-setup-ref-defaults
branch
2 times, most recently
from
August 4, 2026 04:22
1664635 to
93004ee
Compare
fengmk2
added a commit
that referenced
this pull request
Aug 4, 2026
The `v1` major tag is frozen at v1.15.0: the voidzero-dev org-level tag ruleset blocks non-fast-forward tag updates, so it can no longer be moved on each release. This PR restructures the docs around exact version pinning. - New `Versioning` section: pin an exact release tag (or commit SHA), with a warning that `v1` is frozen at v1.15.0 and should not be used - All GitHub, GitLab, and Azure examples now pin `v1.16.0` - GitLab examples pin `setup-ref` to the same tag as the remote URL, so the compiled runtime matches the included template; the separate pinned-runtime section is folded into basic usage - `package.json` version now tracks the latest release (bumped to 1.16.0); it was pinned at 1.0.0 when releases only moved tags - Release steps updated: a PR bumps `package.json` and the README tags before tagging, no `v1` move Follow-up in #117 (stacked on this PR): the GitLab `setup-ref` and Azure `setupRef` template defaults still fall back to the frozen `v1`, so an unpinned include silently gets the v1.15.0 runtime.
An unpinned setup-ref (GitLab) or setupRef (Azure) downloaded the compiled runtime from the moving v1 tag, which is now frozen at v1.15.0, so unpinned includes silently ran a stale runtime. Default both to the latest release instead, and bump the defaults in each release PR (added to the release checklist).
fengmk2
force-pushed
the
fix-setup-ref-defaults
branch
from
August 4, 2026 05:33
93004ee to
c15a5de
Compare
fengmk2
marked this pull request as ready for review
August 4, 2026 05:36
Contributor
There was a problem hiding this comment.
Pull request overview
This PR updates the GitLab and Azure pipeline templates to stop defaulting setup-ref / setupRef to the frozen v1 tag (v1.15.0), ensuring unpinned template usage pulls the intended compiled runtime for the template’s published release.
Changes:
- Default
setup-ref(GitLab) andsetupRef(Azure) tov1.16.0in the shipped templates (including the GitLab env fallback). - Update README input/parameter tables and the release checklist to reflect the new default-bump requirement per release.
- Update
src/azure/template.test.tsto assert the new Azure template default.
Reviewed changes
Copilot reviewed 4 out of 4 changed files in this pull request and generated no comments.
| File | Description |
|---|---|
src/azure/template.test.ts |
Updates the test expectation so the Azure template’s setupRef default matches the published template default (v1.16.0). |
README.md |
Aligns docs and release checklist with the new template defaults and the “bump defaults per release” process. |
gitlab/setup-vp.yml |
Changes setup-ref default and bash env fallback to v1.16.0 so unpinned includes don’t fetch the frozen v1 runtime. |
azure/setup-vp.yml |
Changes setupRef parameter default to v1.16.0 so unpinned template usage pulls the correct runtime ref. |
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
Merged
fengmk2
added a commit
that referenced
this pull request
Aug 4, 2026
Bump the version to v1.16.1 in package.json, the README examples, and the setup-ref / setupRef defaults in the GitLab and Azure templates. Changes since v1.16.0: - fix: stop defaulting setup-ref/setupRef to the frozen v1 tag (#117) - docs: use exact version tags instead of the moving v1 tag (#116) After merge, tag the merge commit as v1.16.1 and push the tag. --------- Signed-off-by: MK (fengmk2) <fengmk2@gmail.com> Co-authored-by: Copilot Autofix powered by AI <175728472+Copilot@users.noreply.github.com>
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
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.
Follow-up to #116 (now merged).
An unpinned
setup-ref(GitLab) orsetupRef(Azure) downloaded the compiled runtime from the movingv1tag, which is now frozen at v1.15.0, so unpinned includes silently ran a stale v1.15.0 runtime.setup-ref/setupRef(input default and bash env fallback) tov1.16.0, the latest releasesrc/azure/template.test.tsassertionThe README examples keep the explicit
setup-refpin, which is still the recommended setup and the only correct one for v1.16.0 itself (its shipped template default is the frozenv1).