| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
There was a problem hiding this comment.
Copilot reviewed 7 out of 13 changed files in this pull request and generated no comments.
Files not reviewed (6).github/workflows/__multi-language-autodetect.yml:91
languages: ${{ runner.os == 'Linux' && 'cpp,csharp,go,java,javascript,python,ruby' || '' }}
Tip: Copilot only keeps its highest confidence comments to reduce noise and keep you focused. Learn more
Sorry, something went wrong.
|
@mbg, there are three workflows that are failing now that I'm deprecating 2.14.6. It looks like you created these workflows and hard-coded 2.14.6. Is there another, non-deprecated version we can use? Is it the case that now that 2.14.6 is deprecated, we can remove the workaround? |
Sorry, something went wrong.
|
I think intention with pinning that version was that we would fix/improve the tracer not long after, and so would no longer need the workaround then. However, that never happened, so the workaround is still needed to this day (AFAIK). That means we can either:
|
Sorry, something went wrong.
|
OK. Thanks. I'll pin it to 2.20.0. |
Sorry, something went wrong.
|
Actually, if I pin to default and the workaround is implemented, then we will see a test failure more quickly and will be reminded to change or remove the tests. I changed to that. |
Sorry, something went wrong.
| include: | ||
| - os: ubuntu-latest | ||
| version: stable-v2.14.6 | ||
| version: default |
There was a problem hiding this comment.
Why does this not update as stable-v2.19.4 like files below ? Diff in files .github/workflows/__go-tracing-autobuilder.yml and beyond do not mention default as version. Not sure if this is just setup differently for different workflows.
Sorry, something went wrong.
There was a problem hiding this comment.
maybe your comment here is linked to my Q -- but I am not sure I fully understand the reasoning though. Do we follow some guide/playbook for these upgrades?
Sorry, something went wrong.
There was a problem hiding this comment.
Yes. These tests are for a particular workaround in the CLI and action for indirect tracing of go code. I'm actually not sure what this is. It's something that @mbg implemented. It's testing that if we're using a version of go that supports statically linked binaries, we can still build a database even though the CodeQL go tracer does not support statically linked binaries. If we ever do implement this in the go tracer, then these tests will start to fail.
I moved from a fixed version to default so that we won't need to update these tests again in the future.
We only need to test a single version since this is a mechanism that is in the action, and independent of the codeql version.
Look at the "Deprecating a CodeQL version" section of CONTRIBUTING.md for more information around how this deprecation works.
Sorry, something went wrong.
There was a problem hiding this comment.
Versions for the other workflows are handled by the sync.py script.
Sorry, something went wrong.
| include: | ||
| - os: ubuntu-latest | ||
| version: stable-v2.14.6 | ||
| version: default |
There was a problem hiding this comment.
same comment as above
Sorry, something went wrong.
| include: | ||
| - os: ubuntu-latest | ||
| version: stable-v2.14.6 | ||
| version: default |
There was a problem hiding this comment.
same comment as above
Sorry, something went wrong.
| | `v2.22.1` | `2.14.6` | Enterprise Server 3.11 | Supports CodeQL Action v3, but did not ship with CodeQL Action v3. For more information, see "[Code scanning: deprecation of CodeQL Action v2](https://github.blog/changelog/2024-01-12-code-scanning-deprecation-of-codeql-action-v2/#users-of-github-enterprise-server-311)." | | ||
|
|
||
| CodeQL Action v2 will stop receiving updates when GHES 3.11 is deprecated. | ||
| CodeQL Action v2 has stopped receiving updates now that GHES 3.11 is deprecated. |
There was a problem hiding this comment.
Does this need to be part of changelog update?
Sorry, something went wrong.
There was a problem hiding this comment.
I jumped the gun on this change by just a little since v2 is not yet officially deprecated. This is something @angelapwen will be working on shortly. GHES 3.11 is getting deprecated on December 19.
I made the change since I thought it would be confusing to remove the line about GFHES 3.11 and keep the line about v2 unchanged.
The last update to the v2 branch should only go in the v2 branch, so I won't put it the changelog on the main branch.
Sorry, something went wrong.
There was a problem hiding this comment.
Looks fine to me, but we want to make sure that we don't merge before Dec 19, right?
Sorry, something went wrong.
|
I will make a release on December 19. It's probably fine to merge this PR before then. |
Sorry, something went wrong.
There was a problem hiding this comment.
:merge-it:
Sorry, something went wrong.
| Back | FazBrowse Home | New Git URL |
Merge / deployment checklist