build(deps): bump the github-actions group with 3 updates

[dependabot]

Bumps the github-actions group with 3 updates: github/codeql-action, actions/setup-go and dessant/lock-threads.

Updates github/codeql-action from 2.22.7 to 2.22.8

Changelog

Sourced from github/codeql-action's changelog.

CodeQL Action Changelog

See the releases page for the relevant changes to the CodeQL CLI and language packs.

[UNRELEASED]

No user facing changes.

2.22.8 - 23 Nov 2023

• Update default CodeQL bundle version to 2.15.3. #2001

2.22.7 - 16 Nov 2023

• Add a deprecation warning for customers using CodeQL version 2.11.5 and earlier. These versions of CodeQL were discontinued on 8 November 2023 alongside GitHub Enterprise Server 3.7, and will be unsupported by CodeQL Action v2.23.0 and later. #1993
  • If you are using one of these versions, please update to CodeQL CLI version 2.11.6 or later. For instance, if you have specified a custom version of the CLI using the 'tools' input to the 'init' Action, you can remove this input to use the default version.
  • Alternatively, if you want to continue using a version of the CodeQL CLI between 2.10.5 and 2.11.5, you can replace github/codeql-action/*@v2 by github/codeql-action/*@v2.22.7 in your code scanning workflow to ensure you continue using this version of the CodeQL Action.

2.22.6 - 14 Nov 2023

• Customers running Python analysis on macOS using version 2.14.6 or earlier of the CodeQL CLI should upgrade to CodeQL CLI version 2.15.0 or later. If you do not wish to upgrade the CodeQL CLI, ensure that you are using Python version 3.11 or earlier, as CodeQL version 2.14.6 and earlier do not support Python 3.12. You can achieve this by adding a setup-python step to your code scanning workflow before the step that invokes github/codeql-action/init.
• Update default CodeQL bundle version to 2.15.2. #1978

2.22.5 - 27 Oct 2023

No user facing changes.

2.22.4 - 20 Oct 2023

• Update default CodeQL bundle version to 2.15.1. #1953
• Users will begin to see warnings on Node.js 16 deprecation in their Actions logs on code scanning runs starting October 23, 2023.
  • All code scanning workflows should continue to succeed regardless of the warning.
  • The team at GitHub maintaining the CodeQL Action is aware of the deprecation timeline and actively working on creating another version of the CodeQL Action, v3, that will bump us to Node 20.
  • For more information, and to communicate with the maintaining team, please use this issue.

2.22.3 - 13 Oct 2023

• Provide an authentication token when downloading the CodeQL Bundle from the API of a GitHub Enterprise Server instance. #1945

2.22.2 - 12 Oct 2023

• Update default CodeQL bundle version to 2.15.0. #1938
• Improve the log output when an error occurs in an invocation of the CodeQL CLI. #1927

2.22.1 - 09 Oct 2023

• Add a workaround for Python 3.12, which is not supported in CodeQL CLI version 2.14.6 or earlier. If you are running an analysis on Windows and using Python 3.12 or later, the CodeQL Action will switch to running Python 3.11. In this case, if Python 3.11 is not found, then the workflow will fail. #1928

2.22.0 - 06 Oct 2023

... (truncated)

Commits

• 407ffaf Merge pull request #2007 from github/update-v2.22.8-192ad9bd5
• 4af462f Update changelog for v2.22.8
• 192ad9b Merge pull request #2001 from github/update-bundle/codeql-bundle-v2.15.3
• 77c1abb Merge branch 'main' into update-bundle/codeql-bundle-v2.15.3
• 9f150ba Bump the actions group with 1 update (#2004)
• e75de4c Bump typescript from 5.2.2 to 5.3.2 (#2002)
• 80150c2 Bump the npm group with 12 updates (#2003)
• 4d999a4 Add changelog note
• 83267d5 Update default bundle to codeql-bundle-v2.15.3
• 4b6aa0b Merge pull request #1997 from github/mergeback/v2.22.7-to-main-66b90a5d
• Additional commits viewable in compare view

Updates actions/setup-go from 4.1.0 to 5.0.0

Release notes

Sourced from actions/setup-go's releases.

v5.0.0

What's Changed

In scope of this release, we change Nodejs runtime from node16 to node20 (actions/setup-go#421). Moreover, we update some dependencies to the latest versions (actions/setup-go#445).

Besides, this release contains such changes as:

• Fix hosted tool cache usage on windows by @​galargh in actions/setup-go#411
• Improve documentation regarding dependencies caching by @​artemgavrilov in actions/setup-go#417

New Contributors

• @​galargh made their first contribution in actions/setup-go#411
• @​artemgavrilov made their first contribution in actions/setup-go#417
• @​chenrui333 made their first contribution in actions/setup-go#421

Full Changelog: actions/setup-go@v4...v5.0.0

Commits

• 0c52d54 Update dependencies for node20 (#445)
• bfd2fb3 Merge pull request #421 from chenrui333/node20-runtime
• 3d65fa5 feat: bump to use actions/checkout@v4
• 8a505c9 feat: bump to use node20 runtime
• 883490d Merge pull request #417 from artemgavrilov/main
• d45ebba Rephrase sentence
• 317c661 Replace wildcards term with globs.
• f90673a Merge pull request #1 from artemgavrilov/caching-docs-improvement
• 8018234 Improve documentation regarding dependencies cachin
• d085b4f Merge pull request #411 from galargh/fix/windows-hostedtoolcache
• Additional commits viewable in compare view

Updates dessant/lock-threads from 5.0.0 to 5.0.1

Release notes

Sourced from dessant/lock-threads's releases.

v5.0.1

Learn more about this release from the changelog.

Changelog

Sourced from dessant/lock-threads's changelog.

Changelog

All notable changes to this project will be documented in this file. See commit-and-tag-version for commit guidelines.

5.0.1 (2023-11-22)

Bug Fixes

• support filtering threads by labels with spaces (0a63678), closes #40

5.0.0 (2023-11-14)

⚠ BREAKING CHANGES

• Discussions are also processed by default, set the process-only input parameter to preserve the old behavior

    steps:
      - uses: dessant/lock-threads@v5
        with:
          process-only: 'issues, prs'

• the action now requires Node.js 20

Features

• lock discussions (0a0976f), closes #25

Bug Fixes

• update dependencies (5a25b54)

4.0.1 (2023-06-12)

Bug Fixes

• retry and throttle GitHub API requests (1618e91), closes #35

4.0.0 (2022-12-04)

⚠ BREAKING CHANGES

• the action now requires Node.js 16

... (truncated)

Commits

• 1bf7ec2 chore(release): 5.0.1
• adf4aa5 chore: update package
• 0a63678 fix: support filtering threads by labels with spaces
• See full diff in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore <dependency name> major version will close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself)
• @dependabot ignore <dependency name> minor version will close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself)
• @dependabot ignore <dependency name> will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself)
• @dependabot unignore <dependency name> will remove all of the ignore conditions of the specified dependency
• @dependabot unignore <dependency name> <ignore condition> will remove the ignore condition of the specified dependency and ignore conditions

RELEASE NOTES: none

[codecov]

Codecov Report

Merging #6835 (e92277c) into master (c2398ce) will increase coverage by 0.06%.
The diff coverage is n/a.

Additional details and impacted files

@@            Coverage Diff             @@
##           master    #6835      +/-   ##
==========================================
+ Coverage   83.58%   83.65%   +0.06%     
==========================================
  Files         285      285              
  Lines       30754    30754              
==========================================
+ Hits        25706    25726      +20     
+ Misses       3991     3973      -18     
+ Partials     1057     1055       -2     

see 22 files with indirect coverage changes

[dfawley]

Updates actions/setup-go from 4.1.0 to 5.0.0

@pnacht is it expected for the bot to send PRs that update major versions, which presumably contain breaking changes? Does it do anything to vet that things will keep working before sending the PR, or is that on us to verify it before merging, or merge it and just hope for the best?

I'd probably rather stay on vN-1 unless there's a known security problem with it, than upgrade to vN regularly and need to pay the cost of vetting the new version.

[pnacht]

Hey @dfawley. Yes, dependabot does update to new major versions by default.

I've often found that breaking changes are usually easy to identify in projects such as gRPC-Go that have a lot of CI/CD testing: if there were a breaking change, the PR's checks would fail.

That being said, I can configure dependabot to ignore new major versions if you prefer.

---

In this particular case, actions/setup-go only released a new major version because they bumped the Action's runtime from node16 to node20, something most actions/* have done over the last few months.

[dfawley]

I've often found that breaking changes are usually easy to identify in projects such as gRPC-Go that have a lot of CI/CD testing: if there were a breaking change, the PR's checks would fail.

I don't care if it's fairly easy. If we're doing this, I want it to be literally 100% painless, because I don't think the security gains here are all that real

That being said, I can configure dependabot to ignore new major versions if you prefer.

Yes, please do, thanks!

In this particular case, actions/setup-go only released a new major version because they bumped the Action's runtime from node16 to node20

SG, I guess we can take this without worrying, then.