chore(ci): bump gradle/actions from 6 to 6.2.0 - #336
Conversation
Bumps [gradle/actions](https://github.com/gradle/actions) from 6 to 6.2.0. - [Release notes](https://github.com/gradle/actions/releases) - [Commits](gradle/actions@v6...v6.2.0) --- updated-dependencies: - dependency-name: gradle/actions dependency-version: 6.2.0 dependency-type: direct:production update-type: version-update:semver-minor ... Signed-off-by: dependabot[bot] <support@github.com>
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: ASSERTIVE Plan: Pro Plus Run ID: 📒 Files selected for processing (1)
📝 WalkthroughWalkthroughThe Android bundle workflow updates ChangesAndroid workflow
Estimated code review effort: 1 (Trivial) | ~2 minutes Suggested reviewers: 🚥 Pre-merge checks | ✅ 9✅ Passed checks (9 passed)
✨ Finishing Touches🧪 Generate unit tests (beta)
Comment |
|
OK, I won't notify you again about this release, but will get in touch when a new version is available. If you'd rather skip all updates until the next major or minor version, let me know by commenting If you change your mind, just re-open this PR and I'll resolve any conflicts on it. |
Roll the three currently-open Dependabot PRs into a single change so they land and close together instead of as three separate merges, matching this repo's standing "master Dependabot consolidation" practice. Cargo (production-dependencies group, #338): - wide 1.5.0 -> 1.6.0 (SIMD; used by the frontend software blitter) - clap_complete 4.6.7 -> 4.6.8 (CLI shell-completion generation) Cargo.lock is taken verbatim from Dependabot's #338 so the diff is exactly the four version+checksum lines and nothing else. A local `cargo update -p clap_complete --precise 4.6.8` additionally re-resolved four transitive `windows-sys` references off 0.61.2 (down to 0.52.0/0.48.0) -- a valid but non-minimal churn cargo does opportunistically against a newer registry index; Dependabot's own lockfile does NOT do this (clap 4.6.8 does not require it), and agy's review flagged the drift, so the minimal lockfile is used instead. `cargo metadata --locked` accepts it, so it is consistent with the manifest with zero re-resolution. GitHub Actions: - taiki-e/install-action v2 -> v2.85.5 (#337) -- both call sites in .github/workflows/security.yml (the cargo-audit and cargo-deny jobs, which install the prebuilt binaries rather than compiling them under the 1.96 pin). - gradle/actions/setup-gradle v6 -> v6.2.0 (#336) -- the Android foss+play bundle job in .github/workflows/android.yml. Both move from a floating `@vN` major tag to the exact patch Dependabot pins; Dependabot's github-actions ecosystem then tracks them forward. (agy suggested SHA-pinning; declined -- the repo deliberately keeps `@vN` tags for every action except the compiler-installing dtolnay/rust-toolchain, a documented maintenance-policy choice.) Verification: - Cargo.lock diff == Dependabot #338 (wide + clap_complete only, no windows-sys or other transitive churn); `cargo metadata --locked` clean. - `cargo check --workspace` compiles the full graph on the new lockfile. - `cargo build -p rustynes-core --target thumbv7em-none-eabihf --no-default-features` -- the standalone no_std build a full workspace build masks (the lz4_flex-0.14 lesson) -- stays green. - Both edited workflows parse as valid YAML. Supersedes #336, #337, #338 (closed in favour of this consolidated PR). Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
…340) Roll the three currently-open Dependabot PRs into a single change so they land and close together instead of as three separate merges, matching this repo's standing "master Dependabot consolidation" practice. Cargo (production-dependencies group, #338): - wide 1.5.0 -> 1.6.0 (SIMD; used by the frontend software blitter) - clap_complete 4.6.7 -> 4.6.8 (CLI shell-completion generation) Cargo.lock is taken verbatim from Dependabot's #338 so the diff is exactly the four version+checksum lines and nothing else. A local `cargo update -p clap_complete --precise 4.6.8` additionally re-resolved four transitive `windows-sys` references off 0.61.2 (down to 0.52.0/0.48.0) -- a valid but non-minimal churn cargo does opportunistically against a newer registry index; Dependabot's own lockfile does NOT do this (clap 4.6.8 does not require it), and agy's review flagged the drift, so the minimal lockfile is used instead. `cargo metadata --locked` accepts it, so it is consistent with the manifest with zero re-resolution. GitHub Actions: - taiki-e/install-action v2 -> v2.85.5 (#337) -- both call sites in .github/workflows/security.yml (the cargo-audit and cargo-deny jobs, which install the prebuilt binaries rather than compiling them under the 1.96 pin). - gradle/actions/setup-gradle v6 -> v6.2.0 (#336) -- the Android foss+play bundle job in .github/workflows/android.yml. Both move from a floating `@vN` major tag to the exact patch Dependabot pins; Dependabot's github-actions ecosystem then tracks them forward. (agy suggested SHA-pinning; declined -- the repo deliberately keeps `@vN` tags for every action except the compiler-installing dtolnay/rust-toolchain, a documented maintenance-policy choice.) Verification: - Cargo.lock diff == Dependabot #338 (wide + clap_complete only, no windows-sys or other transitive churn); `cargo metadata --locked` clean. - `cargo check --workspace` compiles the full graph on the new lockfile. - `cargo build -p rustynes-core --target thumbv7em-none-eabihf --no-default-features` -- the standalone no_std build a full workspace build masks (the lz4_flex-0.14 lesson) -- stays green. - Both edited workflows parse as valid YAML. Supersedes #336, #337, #338 (closed in favour of this consolidated PR). Co-authored-by: Claude Opus 4.8 <noreply@anthropic.com>
Bumps gradle/actions from 6 to 6.2.0.
Release notes
Sourced from gradle/actions's releases.
... (truncated)
Commits
b6eebf3[bot] Update dist directory9901393Remove unnecessary dependency overrides (#981)20ce680Update RELEASING.md5e2ebd0[bot] Update dist directory9e2c1ccResolve npm security vulnerabilities via dependency overrides (#980)657f690[bot] Update dist directory9d6bacdUpdate@actions/cacheand@actions/artifact, stop ignoring them in Dependabot...79f6b19[bot] Update dist directory6781648Bump the npm-dependencies group in /sources with 5 updates (#977)a3b40d2[bot] Update dist directoryDependabot 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 rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@dependabot ignore this major versionwill close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this minor versionwill close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this dependencywill close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)Summary by CodeRabbit