Visitar URL original
fix(deps): update all (major) by renovate[bot] · Pull Request #19 · moul/logman · GitHub
Skip to content

fix(deps): update all (major) - #19

Open
renovate[bot] wants to merge 1 commit into
mainfrom
renovate/major-all
Open

renovate[bot] wants to merge 1 commit into
mainfrom
renovate/major-all

Conversation

@renovate

@renovate renovate Bot commented Mar 7, 2022 •

Copy link
Copy Markdown

ℹ️ Note

This PR body was truncated due to platform limits.

This PR contains the following updates:

Package Type Update Change Age Confidence
actions/cache action major v2.1.7 → v6.1.0 age confidence
actions/checkout action major v2.4.0 → v7.0.1 age confidence
actions/setup-go action major v2 → v7 age confidence
alex (source) dependencies major 10.0.0 → 11.0.1 age confidence
codecov/codecov-action action major v2.1.0 → v7.1.1 age confidence
ghcr.io/codfish/semantic-release-action docker major v1 → v5 age confidence
github/codeql-action action major v1 → v4 age confidence
golangci/golangci-lint-action action major v2.5.2 → v9.3.0 age confidence

Release Notes

actions/cache (actions/cache)

v6.1.0

Compare Source

What's Changed

Full Changelog: actions/cache@v6...v6.1.0

v6.0.0

Compare Source

What's Changed

Full Changelog: actions/cache@v5...v6.0.0

v5.1.0

Compare Source

What's Changed

Full Changelog: actions/cache@v5...v5.1.0

v5.0.5

Compare Source

What's Changed

Full Changelog: actions/cache@v5...v5.0.5

v5.0.4

Compare Source

What's Changed
New Contributors

Full Changelog: actions/cache@v5...v5.0.4

v5.0.3

Compare Source

What's Changed

Full Changelog: actions/cache@v5...v5.0.3

v5.0.2: v.5.0.2

Compare Source

v5.0.2
What's Changed

When creating cache entries, 429s returned from the cache service will not be retried.

v5.0.1

Compare Source

[!IMPORTANT]
actions/cache@v5 runs on the Node.js 24 runtime and requires a minimum Actions Runner version of 2.327.1.

If you are using self-hosted runners, ensure they are updated before upgrading.


v5.0.1
What's Changed
v5.0.0
What's Changed

Full Changelog: actions/cache@v5...v5.0.1

v5.0.0

Compare Source

[!IMPORTANT]
actions/cache@v5 runs on the Node.js 24 runtime and requires a minimum Actions Runner version of 2.327.1.

If you are using self-hosted runners, ensure they are updated before upgrading.


What's Changed

Full Changelog: actions/cache@v4.3.0...v5.0.0

v4.3.0

Compare Source

What's Changed
New Contributors

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

v4.2.4

Compare Source

What's Changed
New Contributors

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

v4.2.3

Compare Source

What's Changed
New Contributors

Full Changelog: actions/cache@v4.2.2...v4.2.3

v4.2.2

Compare Source

What's Changed

[!IMPORTANT]
As a reminder, there were important backend changes to release v4.2.0, see those release notes and the announcement for more details.

Full Changelog: actions/cache@v4.2.1...v4.2.2

v4.2.1

Compare Source

What's Changed

[!IMPORTANT]
As a reminder, there were important backend changes to release v4.2.0, see those release notes and the announcement for more details.

New Contributors

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

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.1.2...v4.2.0

v4.1.2

Compare Source

What's Changed
New Contributors

Full Changelog: actions/cache@v4.1.1...v4.1.2

v4.1.1

Compare Source

What's Changed

Full Changelog: actions/cache@v4.1.0...v4.1.1

v4.1.0

Compare Source

What's Changed
New Contributors

Full Changelog: actions/cache@v4.0.2...v4.1.0

v4.0.2

Compare Source

What's Changed

Full Changelog: actions/cache@v4.0.1...v4.0.2

v4.0.1

Compare Source

What's Changed
New Contributors

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

v4.0.0

Compare Source

What's Changed

New Contributors

Full Changelog: actions/cache@v3...v4.0.0

v3.5.0

Compare Source

  • Bump actions/cache to v4.1.0

Full Changelog: actions/cache@v3...v3.5.0

v3.4.3

Compare Source

What's Changed

Full Changelog: actions/cache@v3.4.2...v3.4.3

v3.4.2

Compare Source

What's Changed

[!IMPORTANT]
As a reminder, there were important backend changes to release v3.4.0, see those release notes and the announcement for more details.

Full Changelog: actions/cache@v3.4.0...v3.4.2

v3.4.1

Compare Source

[!WARNING]
This version was incorrectly released using a SHA pointing to a newer version for immutable actions only. Please use v3.4.2 (or v3) instead.

v3.4.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@v3.3.3...v3.4.0

v3.3.3

Compare Source

What's Changed
New Contributors

Full Changelog: actions/cache@v3...v3.3.3

v3.3.2

Compare Source

What's Changed
New Contributors

Full Changelog: actions/cache@v3...v3.3.2

v3.3.1

Compare Source

What's Changed

Full Changelog: actions/cache@v3...v3.3.1

v3.3.0

Compare Source

What's Changed
New Contributors

Full Changelog: actions/cache@v3...v3.3.0

v3.2.6

Compare Source

What's Changed

Full Changelog: actions/cache@v3...v3.2.6

v3.2.5

Compare Source

What's Changed
New Contributors

Full Changelog: actions/cache@v3...v3.2.5

v3.2.4

Compare Source

What's Changed
New Contributors

Full Changelog: actions/cache@v3...v3.2.4

v3.2.3

Compare Source

What's Changed
New Contributors

Full Changelog: actions/cache@v3...v3.2.3

v3.2.2

Compare Source

What's Changed
New Contributors

Full Changelog: actions/cache@v3.2.1...v3.2.2

v3.2.1

Compare Source

What's Changed

Full Changelog: actions/cache@v3.2.0...v3.2.1

v3.2.0

Compare Source

What's Changed
New Contributors

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

v3.0.11

Compare Source

What's Changed
New Contributors

Full Changelog: actions/cache@v3...v3.0.11

v3.0.10

Compare Source

  • Fix a bug with sorting inputs.
  • Update definition for restore-keys in README.md

v3.0.9

Compare Source

  • Enhanced the warning message for cache unavailability in case of GHES.

v3.0.8

Compare Source

What's Changed
  • Fix zstd not working for windows on gnu tar in issues.
  • Allow users to provide a custom timeout as input for aborting cache segment download using the environment variable SEGMENT_DOWNLOAD_TIMEOUT_MIN. Default is 60 minutes.

v3.0.7

Compare Source

What's Changed
  • Fix for the download stuck problem has been added in actions/cache for users who were intermittently facing the issue. As part of this fix, new timeout has been introduced in the download step to stop the download if it doesn't complete within an hour and run the rest of the workflow without erroring out.

v3.0.6

Compare Source

What's Changed
  • Add example for clojure lein project dependencies by @​shivamarora1 in PR #​835
  • Update toolkit's cache npm module to latest. Bump cache version to v3.0.6 by @​pdotl in PR #​887
  • Fix issue #​809 where cache save/restore was failing for Amazon Linux 2 runners due to older tar version
  • Fix issue #​833 where cache save was not working for caching github workspace directory
New Contributors

Full Changelog: actions/cache@v3...v3.0.6

v3.0.5

Compare Source

Removed error handling by consuming actions/cache 3.0 toolkit, Now cache server error handling will be done by toolkit.

v3.0.4

Compare Source

In this release, we have fixed the tar creation error while trying to create it with path as ~/ home folder on ubuntu-latest.

v3.0.3

Compare Source

Fixed avoiding empty cache save when no files are available for caching. (#​624)

v3.0.2

Compare Source

This release adds the support for dynamic cache size cap on GHES.

v3.0.1

Compare Source

  • Added support for caching from GHES 3.5.
  • Fixed download issue for files > 2GB during restore.

v3.0.0

Compare Source

  • This change adds a minimum runner version(node12 -> node16), which can break users using an out-of-date/fork of the runner. This would be most commonly affecting users on GHES 3.3 or before, as those runners do not support node16 actions and they can use actions from github.com via github connect or manually copying the repo to their GHES instance.

  • Few dependencies and cache action usage examples have also been updated.

v2.1.8: Updating actions/core to version 1.10.0

Compare Source

The ::save-state and ::set-output are deprecated. The newer version of actions/core >1.10.0 uses the new syntax for save and set output. After this change, customers using actions/cache@​v2 won't see deprecation warning message.

actions/checkout (actions/checkout)

v7.0.1

Compare Source

v7.0.0

Compare Source

v6.1.0

Compare Source

v6.0.3

Compare Source

v6.0.2

Compare Source

v6.0.1

Compare Source

v6.0.0

Compare Source

v5.1.0

Compare Source

[`v5

❗ Important

✂ PR body was truncated to here.


Configuration

📅 Schedule: (UTC)

  • Branch creation
    • At any time (no schedule defined)
  • 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 a review from moul as a code owner March 7, 2022 13:55
@codecov

codecov Bot commented Mar 7, 2022 •

Copy link
Copy Markdown

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 60.60%. Comparing base (b9f08c0) to head (7a2351b).
Report is 2 commits behind head on main.

❗ Current head 7a2351b differs from pull request most recent head 284514d

Please upload reports for the commit 284514d to get more accurate results.

Additional details and impacted files
@@           Coverage Diff           @@
##             main      #19   +/-   ##
=======================================
  Coverage   60.60%   60.60%           
=======================================
  Files           1        1           
  Lines         132      132           
=======================================
  Hits           80       80           
  Misses         37       37           
  Partials       15       15           
Flag Coverage Δ
unittests 60.60% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

@trafico-bot trafico-bot Bot added the 🔍 Ready for Review Pull Request is not reviewed yet label Mar 7, 2022
@renovate
renovate Bot force-pushed the renovate/major-all branch from fa95d0d to fc4672d Compare March 26, 2022 13:17
@renovate
renovate Bot force-pushed the renovate/major-all branch from fc4672d to 11d213b Compare April 24, 2022 19:18
@renovate
renovate Bot force-pushed the renovate/major-all branch from 11d213b to 6ad3dc1 Compare May 16, 2022 01:53
@renovate
renovate Bot force-pushed the renovate/major-all branch from 6ad3dc1 to 423641c Compare June 18, 2022 18:02
@renovate
renovate Bot force-pushed the renovate/major-all branch from 423641c to 9027c24 Compare September 25, 2022 18:06
@renovate
renovate Bot force-pushed the renovate/major-all branch from 9027c24 to 7a2351b Compare November 20, 2022 17:39
@renovate
renovate Bot force-pushed the renovate/major-all branch from 7a2351b to 9d5dd0b Compare March 16, 2023 07:52
@renovate
renovate Bot force-pushed the renovate/major-all branch from 9d5dd0b to fe8c65b Compare March 24, 2023 18:55
@socket-security

socket-security Bot commented Mar 24, 2023 •

Copy link
Copy Markdown

Warning

Review the following alerts detected in dependencies.

According to your organization's Security Policy, it is recommended to resolve "Warn" alerts. Learn more about Socket for GitHub.

Action Severity Alert  (click "▶" to expand/collapse)
Warn High
Obfuscated code: npm @pnpm/network.ca-file is 90.0% likely obfuscated

Confidence: 0.90

Location: Package overview

From: ? → npm/alex@11.0.1 → npm/@pnpm/network.ca-file@1.0.2

ℹ Read more on: This package | This alert | What is obfuscated code?

Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev.

Suggestion: Packages should not obfuscate their code. Consider not using packages with obfuscated code.

Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/@pnpm/network.ca-file@1.0.2. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.

View full report

@renovate
renovate Bot force-pushed the renovate/major-all branch from fe8c65b to 1c56bf2 Compare April 17, 2023 13:12
@renovate
renovate Bot force-pushed the renovate/major-all branch 2 times, most recently from b80c65e to 30b33e7 Compare June 2, 2023 12:32
@renovate
renovate Bot force-pushed the renovate/major-all branch from 30b33e7 to 6156501 Compare June 9, 2023 17:25
@socket-security

socket-security Bot commented Jun 9, 2023 •

Copy link
Copy Markdown

Review the following changes in direct dependencies. Learn more about Socket for GitHub.

Diff Package Supply Chain
Security
Vulnerability Quality Maintenance License
Updatednpm/​alex@​10.0.0 ⏵ 11.0.196 +110010080100

View full report

@renovate
renovate Bot force-pushed the renovate/major-all branch from 6156501 to 29b9af0 Compare June 12, 2023 10:53
@renovate
renovate Bot force-pushed the renovate/major-all branch 2 times, most recently from 6e513a4 to e2714f5 Compare August 18, 2023 17:11
@renovate
renovate Bot force-pushed the renovate/major-all branch from e2714f5 to acf9a14 Compare August 24, 2023 17:24
@renovate
renovate Bot force-pushed the renovate/major-all branch 2 times, most recently from 0c1d89b to 0889d1f Compare September 8, 2023 16:20
@renovate
renovate Bot force-pushed the renovate/major-all branch from 0889d1f to 56a1e77 Compare September 22, 2023 18:10
@renovate
renovate Bot force-pushed the renovate/major-all branch from 56a1e77 to efdf076 Compare October 17, 2023 17:08
@renovate
renovate Bot force-pushed the renovate/major-all branch from efdf076 to 5d5f78a Compare November 9, 2023 22:08
@renovate
renovate Bot force-pushed the renovate/major-all branch from 5d5f78a to c8ed01d Compare December 6, 2023 16:42
@renovate
renovate Bot force-pushed the renovate/major-all branch from c8ed01d to a6b7ee0 Compare December 13, 2023 17:20
@renovate
renovate Bot force-pushed the renovate/major-all branch from a6b7ee0 to 577e3e0 Compare January 11, 2024 17:25
@renovate
renovate Bot force-pushed the renovate/major-all branch 4 times, most recently from 4f3e942 to 7606159 Compare May 1, 2024 15:33
@renovate
renovate Bot force-pushed the renovate/major-all branch 5 times, most recently from b15aea7 to eba939a Compare May 8, 2024 23:02
@renovate
renovate Bot force-pushed the renovate/major-all branch 3 times, most recently from 9e11393 to f9fb0f1 Compare May 20, 2024 20:31
@renovate
renovate Bot force-pushed the renovate/major-all branch 2 times, most recently from cfda03e to 284514d Compare June 13, 2024 08:09
@renovate
renovate Bot force-pushed the renovate/major-all branch from 284514d to 4f83ef7 Compare July 29, 2024 22:36
@renovate
renovate Bot force-pushed the renovate/major-all branch 2 times, most recently from 292730d to 51f938a Compare October 1, 2024 15:28
@renovate
renovate Bot force-pushed the renovate/major-all branch 4 times, most recently from 567670f to e230d10 Compare October 8, 2024 18:53
@renovate
renovate Bot force-pushed the renovate/major-all branch 2 times, most recently from 6ada278 to 39df8c4 Compare October 23, 2024 15:24
@renovate
renovate Bot force-pushed the renovate/major-all branch 4 times, most recently from 861c4e1 to 5155482 Compare November 19, 2024 22:22
@socket-security

socket-security Bot commented Jul 18, 2026 •

Copy link
Copy Markdown

Review the following changes in direct dependencies. Learn more about Socket for GitHub.

Diff Package Supply Chain
Security
Vulnerability Quality Maintenance License
Updatednpm/​alex@​10.0.0 ⏵ 11.0.196 +110010080100

View full report

@socket-security

socket-security Bot commented Jul 18, 2026 •

Copy link
Copy Markdown

Warning

Review the following alerts detected in dependencies.

According to your organization's Security Policy, it is recommended to resolve "Warn" alerts. Learn more about Socket for GitHub.

Action Severity Alert  (click "▶" to expand/collapse)
Warn High
Obfuscated code: npm @pnpm/network.ca-file is 90.0% likely obfuscated

Confidence: 0.90

Location: Package overview

From: tool/lint/package.json → npm/alex@11.0.1 → npm/@pnpm/network.ca-file@1.0.2

ℹ Read more on: This package | This alert | What is obfuscated code?

Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev.

Suggestion: Packages should not obfuscate their code. Consider not using packages with obfuscated code.

Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/@pnpm/network.ca-file@1.0.2. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.

View full report

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

dependencies 🔍 Ready for Review Pull Request is not reviewed yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants