Fix action pins to resolve tags exactly as specified #10567
Merged
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.
When resolving action versions dynamically, the system was replacing user-specified tags (e.g., "v4") with more precise versions from the cache (e.g., "v4.6.2") if they pointed to the same SHA. This caused version comments to flip unexpectedly between compilations.
Changes
GetActionPinWithData()that checked cache for "more precise" versions and substituted themTestGetActionPinWithData_ExactVersionResolutionverifying exact tag resolution with dynamic resolverBehavior
Fallback to hardcoded pins (when no resolver available) remains unchanged - exact match preferred, semver-compatible fallback if needed.
Original prompt
💬 We'd love your input! Share your thoughts on Copilot coding agent in our 2 minute survey.