Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
chore(deps): update workflows (#2849)
This PR contains the following updates: | Package | Type | Update | Change | |---|---|---|---| | [github/codeql-action](https://redirect.github.com/github/codeql-action) | action | patch | `v2.27.0` -> `v2.27.3` | | [github/codeql-action](https://redirect.github.com/github/codeql-action) | action | patch | `v3.27.0` -> `v3.27.3` | | [pypa/gh-action-pypi-publish](https://redirect.github.com/pypa/gh-action-pypi-publish) | action | minor | `v1.11.0` -> `v1.12.2` | --- ### Release Notes <details> <summary>github/codeql-action (github/codeql-action)</summary> ### [`v2.27.3`](https://redirect.github.com/github/codeql-action/releases/tag/v2.27.3) [Compare Source](https://redirect.github.com/github/codeql-action/compare/v2.27.2...v2.27.3) ##### CodeQL Action Changelog See the [releases page](https://redirect.github.com/github/codeql-action/releases) for the relevant changes to the CodeQL CLI and language packs. Note that the only difference between `v2` and `v3` of the CodeQL Action is the node version they support, with `v3` running on node 20 while we continue to release `v2` to support running on node 16. For example `3.22.11` was the first `v3` release and is functionally identical to `2.22.11`. This approach ensures an easy way to track exactly which features are included in different versions, indicated by the minor and patch version numbers. ##### 2.27.3 - 12 Nov 2024 No user facing changes. See the full [CHANGELOG.md](https://redirect.github.com/github/codeql-action/blob/v2.27.3/CHANGELOG.md) for more information. ### [`v2.27.2`](https://redirect.github.com/github/codeql-action/releases/tag/v2.27.2) [Compare Source](https://redirect.github.com/github/codeql-action/compare/v2.27.1...v2.27.2) ### CodeQL Action Changelog See the [releases page](https://redirect.github.com/github/codeql-action/releases) for the relevant changes to the CodeQL CLI and language packs. Note that the only difference between `v2` and `v3` of the CodeQL Action is the node version they support, with `v3` running on node 20 while we continue to release `v2` to support running on node 16. For example `3.22.11` was the first `v3` release and is functionally identical to `2.22.11`. This approach ensures an easy way to track exactly which features are included in different versions, indicated by the minor and patch version numbers. #### 2.27.2 - 12 Nov 2024 - Fixed an issue where setting up the CodeQL tools would sometimes fail with the message "Invalid value 'undefined' for header 'authorization'". [#​2590](https://redirect.github.com/github/codeql-action/pull/2590) See the full [CHANGELOG.md](https://redirect.github.com/github/codeql-action/blob/v2.27.2/CHANGELOG.md) for more information. ### [`v2.27.1`](https://redirect.github.com/github/codeql-action/releases/tag/v2.27.1) [Compare Source](https://redirect.github.com/github/codeql-action/compare/v2.27.0...v2.27.1) ##### CodeQL Action Changelog See the [releases page](https://redirect.github.com/github/codeql-action/releases) for the relevant changes to the CodeQL CLI and language packs. Note that the only difference between `v2` and `v3` of the CodeQL Action is the node version they support, with `v3` running on node 20 while we continue to release `v2` to support running on node 16. For example `3.22.11` was the first `v3` release and is functionally identical to `2.22.11`. This approach ensures an easy way to track exactly which features are included in different versions, indicated by the minor and patch version numbers. ##### 2.27.1 - 08 Nov 2024 - The CodeQL Action now downloads bundles compressed using Zstandard on GitHub Enterprise Server when using Linux or macOS runners. This speeds up the installation of the CodeQL tools. This feature is already available to GitHub.com users. [#​2573](https://redirect.github.com/github/codeql-action/pull/2573) - Update default CodeQL bundle version to 2.19.3. [#​2576](https://redirect.github.com/github/codeql-action/pull/2576) See the full [CHANGELOG.md](https://redirect.github.com/github/codeql-action/blob/v2.27.1/CHANGELOG.md) for more information. </details> <details> <summary>pypa/gh-action-pypi-publish (pypa/gh-action-pypi-publish)</summary> ### [`v1.12.2`](https://redirect.github.com/pypa/gh-action-pypi-publish/releases/tag/v1.12.2) [Compare Source](https://redirect.github.com/pypa/gh-action-pypi-publish/compare/v1.12.1...v1.12.2) #### 🐛 What's Fixed The fix for signing legacy zip sdists turned out to be incomplete, so [@​woodruffw](https://redirect.github.com/woodruffw)[💰](https://redirect.github.com/sponsors/woodruffw) promptly produced another follow-up that updated `pypi-attestations` from v0.0.13 to v0.0.15 in [#​297](https://redirect.github.com/pypa/gh-action-pypi-publish/issues/297). This is the only change since the previous release. **🪞 Full Diff**: pypa/gh-action-pypi-publish@v1.12.1...v1.12.2 **🧔♂️ Release Manager:** [@​webknjaz](https://redirect.github.com/sponsors/webknjaz) [🇺🇦](https://stand-with-ukraine.pp.ua) ### [`v1.12.1`](https://redirect.github.com/pypa/gh-action-pypi-publish/releases/tag/v1.12.1) [Compare Source](https://redirect.github.com/pypa/gh-action-pypi-publish/compare/v1.12.0...v1.12.1) #### 🐛 What's Fixed Version v1.12.0 hit several rare corner cases we never considered fully supported, and this release fixes a few of those. In [#​294](https://redirect.github.com/pypa/gh-action-pypi-publish/issues/294), [@​webknjaz](https://redirect.github.com/webknjaz)[💰](https://redirect.github.com/sponsors/webknjaz) improved the self-hosted runner experience by pre-installing Python if it's not there, and with [#​293](https://redirect.github.com/pypa/gh-action-pypi-publish/issues/293) the ability to use the action on GitHub Enterprise instances has been restored. The latter should've also fixed the ability to invoke [`pypi-publish`][pypi-publish] from nested in-repo composite actions — another exotic use-case that was never tested in our CI. [@​woodruffw](https://redirect.github.com/woodruffw)[💰](https://redirect.github.com/sponsors/woodruffw) also managed to squeeze in a last-minute fix for detecting legacy `.zip` sdists while producing attestations via [#​295](https://redirect.github.com/pypa/gh-action-pypi-publish/issues/295). **🪞 Full Diff**: pypa/gh-action-pypi-publish@v1.12.0...v1.12.1 **🧔♂️ Release Manager:** [@​webknjaz](https://redirect.github.com/sponsors/webknjaz) [🇺🇦](https://stand-with-ukraine.pp.ua) **🙏 Huge Thanks** to all the bug reporters for posting the logs, helping inspect the problems and verify the regression fixes! [`pypi-publish`]: https://redirect.github.com/marketplace/actions/pypi-publish ### [`v1.12.0`](https://redirect.github.com/pypa/gh-action-pypi-publish/releases/tag/v1.12.0) [Compare Source](https://redirect.github.com/pypa/gh-action-pypi-publish/compare/v1.11.0...v1.12.0) #### ⚡️ Why Should You Update? This is a minor version bump, but it does not add any new user-facing interfaces. Still, I felt like it should not be a patch-release: this update brings *significant changes* to the action invocation and internal release process. Previously, each invocation of [`pypi-publish`][pypi-publish] required building a container image in the invoking CI job. This was inefficient and added about 30 seconds to the publishing jobs at their startup just to build the container. I wanted to improve this for over three years ([#​58](https://redirect.github.com/pypa/gh-action-pypi-publish/issues/58)) and a little over half a year ago [@​br3ndonland](https://redirect.github.com/br3ndonland)[💰](https://redirect.github.com/sponsors/br3ndonland) stepped up and offered a very comprehensive solution to the limitation I was hoping to overcome: [#​230](https://redirect.github.com/pypa/gh-action-pypi-publish/issues/230). Going forward, I'm going to pre-build per-version containers prior to cutting each release. And the action invocations will just pull the image from GitHub Container registry. > \[!CAUTION] > Known quirks: > > - This seems to not work on self-hosted runners without a `python` executable: [#​289](https://redirect.github.com/pypa/gh-action-pypi-publish/issues/289). The workaround could be installing it prior to running the action. > - \~Pinning to commit hashes does not work: [#​290](https://redirect.github.com/pypa/gh-action-pypi-publish/issues/290). Workaround: postpone updating until it's fixed or switch to Git tags for now. Subscribe to that issue to follow the progress.~ *UPD:* This was an issue during the first 12 hours post release and it has been addressed upstream by publishing a commit SHA-tagged image for the release on Nov 12, 2024 at 10:27 UTC+1. > - Calling `pypi-publish` from another nested repo-local composite action might be breaking file paths: [#​291](https://redirect.github.com/pypa/gh-action-pypi-publish/issues/291). Workaround: postpone updating until it's fixed. Subscribe to that issue to follow the progress. > - Running within GitHub Enterprise fails on the action repo clone: [#​292](https://redirect.github.com/pypa/gh-action-pypi-publish/issues/292). Workaround: postpone updating until it's fixed. Subscribe to that issue to follow the progress. **🪞 Full Diff**: pypa/gh-action-pypi-publish@v1.11.0...v1.12.0 **🧔♂️ Release Manager:** [@​webknjaz 🇺🇦](https://redirect.github.com/sponsors/webknjaz) [`pypi-publish`]: https://redirect.github.com/marketplace/actions/pypi-publish </details> --- ### Configuration 📅 **Schedule**: Branch creation - "before 6am on wednesday" in timezone Australia/Sydney, Automerge - At any time (no schedule defined). 🚦 **Automerge**: Disabled by config. Please merge this manually once you are satisfied. ♻ **Rebasing**: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox. 👻 **Immortal**: This PR will be recreated if closed unmerged. Get [config help](https://redirect.github.com/renovatebot/renovate/discussions) if that's undesired. --- - [ ] <!-- rebase-check -->If you want to rebase/retry this PR, check this box --- This PR was generated by [Mend Renovate](https://mend.io/renovate/). View the [repository job log](https://developer.mend.io/github/google/osv.dev). <!--renovate-debug:eyJjcmVhdGVkSW5WZXIiOiIzOS45LjUiLCJ1cGRhdGVkSW5WZXIiOiIzOS45LjUiLCJ0YXJnZXRCcmFuY2giOiJtYXN0ZXIiLCJsYWJlbHMiOlsiZGVwZW5kZW5jaWVzIl19-->
- Loading branch information
1 parent
7825e34
commit 8dfe109