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.
Stop compiler from emitting deprecated artifact v3 pins in GHES mode #43298
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Stop compiler from emitting deprecated artifact v3 pins in GHES mode #43298
Changes from all commits
232cc81ab0bf61f97e3ea7c62b59930b2d4ff58f4dFile filter
Filter by extension
Conversations
Uh oh!
There was an error while loading. Please reload this page.
Jump to
Uh oh!
There was an error while loading. Please reload this page.
There are no files selected for viewing
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The test sets
compatCompiler.ghesArtifactCompat = truedirectly (a private field). Since the field now has no behavioral effect ongetActionPin, this test validates a tautology: it sets a no-op flag, then asserts the result is the same as without the flag. The test will always pass regardless of whether GHES compat is wired up correctly.Consider driving GHES compat through the public API (
compatCompiler.SetGHESCompat(true)followed by a compile step) or testing at integration level viaconfigureCompilerFlags, to ensure the public contract is actually exercised.@copilot please address this.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
After removing the v3 pin override from
getActionPin(),ghesArtifactCompatis now write-only: it is set (lines 437–441) and logged here, but no code path makes a behavioral decision based on it. This means--ghes/aw.json ghes: truesilently have no effect on compilation output beyond this log message.If GHES mode is intended to gate future non-artifact behavior, this is fine as scaffolding. But if the flag is now truly inert, consider removing the field, CLI flag, and schema entry to avoid misleading users — or add an explicit comment documenting that GHES compat is retained for future use.
@copilot please address this.
Uh oh!
There was an error while loading. Please reload this page.