| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
Sorry, something went wrong.
|
@henrymercer, could you review this PR? I've got some failing checks and I'm honestly stumped—Copilot wasn't much help either. util › checkActionVersion reports error for CodeQL Action version 2.2.1 and GitHub version GHES 3.11 ... util › checkActionVersion reports error for CodeQL Action version 2.2.1 and GitHub version GHES 3.12 It seems to consistently fail for these two sets of versions 🤔 Edit: Nevermind |
Sorry, something went wrong.
… to reflect correct deprecation status
There was a problem hiding this comment.
This PR updates the CodeQL Action version deprecation warning from v3 to v4. The changes prepare users for the upcoming deprecation of CodeQL Action v3 by updating version checks, error messages, and minimum supported GHES version requirements.
Copilot reviewed 9 out of 9 changed files in this pull request and generated 2 comments.
| File | Description |
|---|---|
| src/util.ts | Updated checkActionVersion function to check for v4 instead of v3, changed GHES minimum version to 3.20, and updated deprecation message |
| src/util.test.ts | Added test cases for v3 and v4 version checks with various GHES versions, updated expected error message |
| lib/*.js | Generated JavaScript files reflecting the TypeScript changes (auto-generated, not reviewed per guidelines) |
| CHANGELOG.md | Documented the new v3 to v4 migration warning |
Sorry, something went wrong.
Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>
There was a problem hiding this comment.
Looks good, just a couple of minor messaging suggestions.
Sorry, something went wrong.
There was a problem hiding this comment.
![]()
Sorry, something went wrong.
| Back | FazBrowse Home | New Git URL |
Risk assessment
For internal use only. Please select the risk level of this change:
Which use cases does this change impact?
How did/will you validate this change?
If something goes wrong after this change is released, what are the mitigation and rollback strategies?
How will you know if something goes wrong after this change is released?
Merge / deployment checklist