Prompt customers to upgrade from v1 to v2 #1045
Merged
Conversation
This file contains 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
aeisenberg
reviewed
Apr 26, 2022
henrymercer
force-pushed
the
henrymercer/prompt-v1-to-v2-upgrades
branch
from
77bca35 to
0256599
Compare
adityasharad
approved these changes
Apr 28, 2022
This was referenced May 10, 2022
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.
This PR will add a warning on jobs that (a) use a v1 CodeQL Action and (b) run on a GitHub instance that supports v2 of the CodeQL Action. This warning states that v1 will be deprecated on 7th December 2022 and prompts these customers to upgrade to v2.
Example run with old version of the Action in an upgradeable environment: https://github.com/github/codeql-action/actions/runs/2239513990
Merge / deployment checklist