Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[deps]: Update gh minor #184

Open
wants to merge 1 commit into
base: main
Choose a base branch
from
Open

[deps]: Update gh minor #184

wants to merge 1 commit into from

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Nov 11, 2024

This PR contains the following updates:

Package Type Update Change
actions/cache action minor v4.1.2 -> v4.2.0
actions/create-github-app-token action patch v1.11.0 -> v1.11.1
actions/upload-artifact action minor v4.4.3 -> v4.5.0
checkmarx/ast-github-action action patch 2.0.36 -> 2.0.40
crowdin/github-action action minor v2.3.0 -> v2.5.0
github/codeql-action action minor v3.27.0 -> v3.28.0
ruby/setup-ruby action minor v1.197.0 -> v1.204.0

Release Notes

actions/cache (actions/cache)

v4.2.0

Compare Source

⚠️ Important Changes

The cache backend service has been rewritten from the ground up for improved performance and reliability. actions/cache now integrates with the new cache service (v2) APIs.

The new service will gradually roll out as of February 1st, 2025. The legacy service will also be sunset on the same date. Changes in these release are fully backward compatible.

We are deprecating some versions of this action. We recommend upgrading to version v4 or v3 as soon as possible before February 1st, 2025. (Upgrade instructions below).

If you are using pinned SHAs, please use the SHAs of versions v4.2.0 or v3.4.0

If you do not upgrade, all workflow runs using any of the deprecated actions/cache will fail.

Upgrading to the recommended versions will not break your workflows.

Read more about the change & access the migration guide: reference to the announcement.

Minor changes

Minor and patch version updates for these dependencies:

Full Changelog: actions/cache@v4...v4.2.0

actions/create-github-app-token (actions/create-github-app-token)

v1.11.1

Compare Source

actions/upload-artifact (actions/upload-artifact)

v4.5.0

Compare Source

checkmarx/ast-github-action (checkmarx/ast-github-action)

v2.0.40

Compare Source

What's Changed
Other Changes

Full Changelog: Checkmarx/ast-github-action@2.0.39...2.0.40

v2.0.39

Compare Source

What's Changed

Other Changes

Full Changelog: Checkmarx/ast-github-action@2.0.38...2.0.39

v2.0.38

Compare Source

What's Changed

Other Changes

New Contributors

Full Changelog: Checkmarx/ast-github-action@2.0.37...2.0.38

v2.0.37

Compare Source

What's Changed

Other Changes

Full Changelog: Checkmarx/ast-github-action@2.0.36...2.0.37

crowdin/github-action (crowdin/github-action)

v2.5.0

Compare Source

What's Changed

Full Changelog: crowdin/github-action@v2.4.0...v2.5.0

v2.4.0

Compare Source

What's Changed

Full Changelog: crowdin/github-action@v2.3.0...v2.4.0

github/codeql-action (github/codeql-action)

v3.28.0

Compare Source

v3.27.9

Compare Source

CodeQL Action Changelog

See the releases page 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.

3.27.9 - 12 Dec 2024

No user facing changes.

See the full CHANGELOG.md for more information.

v3.27.8

Compare Source

v3.27.7

Compare Source

CodeQL Action Changelog

See the releases page 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.

3.27.7 - 10 Dec 2024
  • We are rolling out a change in December 2024 that will extract the CodeQL bundle directly to the toolcache to improve performance. #​2631
  • Update default CodeQL bundle version to 2.20.0. #​2636

See the full CHANGELOG.md for more information.

v3.27.6

Compare Source

v3.27.5

Compare Source

v3.27.4

Compare Source

CodeQL Action Changelog

See the releases page 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.

3.27.4 - 14 Nov 2024

No user facing changes.

See the full CHANGELOG.md for more information.

v3.27.3

Compare Source

CodeQL Action Changelog

See the releases page 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.

3.27.3 - 12 Nov 2024

No user facing changes.

See the full CHANGELOG.md for more information.

v3.27.2

Compare Source

CodeQL Action Changelog

See the releases page 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.

3.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

See the full CHANGELOG.md for more information.

v3.27.1

Compare Source

CodeQL Action Changelog

See the releases page 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.

3.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
  • Update default CodeQL bundle version to 2.19.3. #​2576

See the full CHANGELOG.md for more information.

ruby/setup-ruby (ruby/setup-ruby)

v1.204.0

Compare Source

What's Changed

Full Changelog: ruby/setup-ruby@v1.203.0...v1.204.0

v1.203.0

Compare Source

Full Changelog: ruby/setup-ruby@v1.202.0...v1.203.0

v1.202.0

Compare Source

What's Changed

Full Changelog: ruby/setup-ruby@v1.201.0...v1.202.0

v1.201.0

Compare Source

What's Changed

Full Changelog: ruby/setup-ruby@v1.200.0...v1.201.0

v1.200.0

Compare Source

What's Changed

Full Changelog: ruby/setup-ruby@v1.199.0...v1.200.0

v1.199.0

Compare Source

What's Changed

Full Changelog: ruby/setup-ruby@v1.198.0...v1.199.0

v1.198.0

Compare Source

What's Changed

Full Changelog: ruby/setup-ruby@v1.197.0...v1.198.0


Configuration

📅 Schedule: Branch creation - "every 2nd week starting on the 2 week of the year before 4am on Monday" (UTC), 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 if that's undesired.


  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

@renovate renovate bot requested review from a team as code owners November 11, 2024 00:10
@bitwarden-bot bitwarden-bot changed the title [deps]: Update gh minor [PM-14690] [deps]: Update gh minor Nov 11, 2024
@bitwarden-bot
Copy link

Internal tracking:

@renovate renovate bot changed the title [PM-14690] [deps]: Update gh minor [deps]: Update gh minor Nov 11, 2024
vgrassia
vgrassia previously approved these changes Nov 11, 2024
@renovate renovate bot force-pushed the renovate/gh-minor branch 2 times, most recently from c7f5cd4 to 8d2a9bf Compare November 12, 2024 21:12
Copy link
Contributor

Logo
Checkmarx One – Scan Summary & Detailsea09d78e-3e04-460c-a9e2-262f82d8beac

New Issues

Severity Issue Source File / Package Checkmarx Insight
MEDIUM Unpinned Actions Full Length Commit SHA /crowdin-pull.yml: 26 Pinning an action to a full length commit SHA is currently the only way to use an action as an immutable release. Pinning to a particular SHA helps...
MEDIUM Unpinned Actions Full Length Commit SHA /build.yml: 67 Pinning an action to a full length commit SHA is currently the only way to use an action as an immutable release. Pinning to a particular SHA helps...

@KatherineInCode
Copy link
Contributor

🤔 @vvolkgang @vgrassia it looks like the tests are failing because renovate doesn't have appropriate permissions. Is there a way we can run tests as one of us to get around that? Or give renovate those permissions?

@renovate renovate bot force-pushed the renovate/gh-minor branch 3 times, most recently from 48d79c8 to d9efa4b Compare November 20, 2024 17:04
@renovate renovate bot force-pushed the renovate/gh-minor branch from d9efa4b to b0e4709 Compare November 25, 2024 09:24
@renovate renovate bot force-pushed the renovate/gh-minor branch 4 times, most recently from 5dabc22 to 1d922c1 Compare December 7, 2024 01:37
@renovate renovate bot force-pushed the renovate/gh-minor branch 6 times, most recently from dd2ba54 to d48cb78 Compare December 17, 2024 12:09
@renovate renovate bot force-pushed the renovate/gh-minor branch from d48cb78 to 85b3511 Compare December 17, 2024 23:32
@renovate renovate bot force-pushed the renovate/gh-minor branch from 85b3511 to f0cae44 Compare December 20, 2024 21:17
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants