chore(deps): update all non-major dependencies - #261
Merged
Conversation
![renovate-approve[bot]](https://avatars.githubusercontent.com/in/7394?s=60&v=4){kind=small}
![renovate-approve-2[bot]](https://avatars.githubusercontent.com/in/62175?s=60&v=4){kind=small}
Contributor
Trivy image scan report
|
Contributor
Trivy image scan report
|
Contributor
Trivy image scan report
|
Contributor
✅MegaLinter analysis: Success
Notices📣 MegaLinter 9.5.0 is out! Discover the new features and security recommendations in the release announcement. (Skip this info by defining See detailed reports in MegaLinter artifacts Your project could benefit from a custom flavor, which would allow you to run only the linters you need, and thus improve runtime performances. (Skip this info by defining
|
Contributor
|
🎉 This PR is included in version 1.11.46 🎉 The release is available on GitHub release Your semantic-release bot 📦🚀 |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
v5.6.0→v5.7.0v4.5.2→v4.6.0v4.37.3→v4.37.4v6.2.0→v6.3.01.28.0→1.29.0Release Notes
actions/setup-java (actions/setup-java)
v5.7.0Compare Source
docker/login-action (docker/login-action)
v4.6.0Compare Source
github/codeql-action (github/codeql-action)
v4.37.4Compare Source
gradle/actions (gradle/actions)
v6.3.0Compare Source
Highlights
Enhanced Caching: Windows fixes and a cache-protocol bump
This release updates
gradle-actions-cachingto v1.0.0 (up from v0.7.0), which fixes two significant caching defects, both most visible on Windows:Cache entries failed to store at all on Windows.. Every entry failed
with
Path Validation Error: Path(s) specified in the action for caching do(es) not exist, even though the Gradle User Home was fully intact. Nothing was stored, soevery downstream job ran against an empty Gradle User Home. The cause was a nested,
unpatched copy of
@actions/globcombined with a silently swallowedrequire()inthe bundle, which left Windows path separators unnormalized.
Cache cleanup deleted instrumented jars that were in use. A bug in key
hashing for paths shorter than 64 characters made cleanup judge freshly created
caches/jars-9entries as unused and remove them, so theinstrumented-jarsentrywas never saved and every job re-instrumented its classpaths.
Also included: cache entry names are now consistent between the save and restore
reports — restore previously fell back to showing the raw glob pattern (e.g.
/home/runner/.gradle/caches/modules-*/files-*/*/*/*/*/) instead ofdependencies.Basic caching warns instead of failing silently
The basic (open-source) caching provider now emits a warning and reports
(Entry not saved: save failed)in the Job Summary when a cache save fails, ratherthan reporting success (#1028).
Dependency submission works with Isolated Projects
dependency-submissionnow disables Isolated Projects via a promoted property, sodependency graph generation works on builds that enable it (#1025). Thanks to @reinsch82 for the contribution.
Updated defaults
wrapper-validationWhat's Changed
New Contributors
Full Changelog: gradle/actions@v6.2.0...v6.3.0
zizmorcore/zizmor (zizmor)
v1.29.0Compare Source
New Features 🌈🔗
zizmor now has experimental support for auditing pre-commit inputs, meaning both pre-commit configuration and hook definitions (#2209)
New audit: insecure-url-scheme detects usages of insecure (i.e. plaintext) protocols when making network requests. The initial version of this audit is limited to pre-commit inputs only (#2228)
zizmor now supports GitHub's "self-repository" reference syntax for local actions, e.g.
uses: $/foo/barinstead of a manual checkout anduses: ./foo/bar(#2248)Changes⚠️ 🔗
uses:clauses, whereas unpinned-images is now responsible fordocker://-styleuses:clauses (in addition to already checking other image references) (#2222)Removals 🌅🔗
--collect=workflows-onlyand--collect=actions-onlyhave been fully removed. Use--collect=workflowsand--collect=actionsfor the replacement behavior (#2242)Bug Fixes 🐛🔗
Fixed a bug where zizmor would reject a valid workflow definition for containing a literal jobs..outputs. value for being a non-string (#2220)
Fixed a bug where the github-app audit would incorrectly flag some usages as needing a repositories: key, despite requesting organization-level-only permissions (#2227)
Fixed a class of bugs where zizmor would discover the user's configuration in unintuitive ways. When auditing from a Git repository, zizmor now uses the repository root to discover configuration consistently (#2234)
Configuration
📅 Schedule: (UTC)
* 0-3 * * 1)🚦 Automerge: Enabled.
♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.
👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.
This PR was generated by Mend Renovate. View the repository job log.