Skip to content

Pin actions, add Dependabot version updates, refresh dependencies - #33

Merged
okcodes merged 5 commits into
mainfrom
security-hardening
Oct 22, 2026
Merged

okcodes merged 5 commits into
mainfrom
security-hardening

Conversation

@okcodes

@okcodes okcodes commented Oct 22, 2026

Copy link
Copy Markdown
Collaborator

What

  • Actions pinned to commit SHAs (Swatinem/rust-cache, dtolnay/rust-toolchain, pnpm/setup); GitHub-owned ones stay on tags. release.yml runs these beside the signing secrets, and a tag can be moved by its owner. rust-toolchain picks its toolchain from the ref, so it now says toolchain: stable explicitly.
  • dependabot.yml: weekly, grouped, for Cargo, /website (pnpm) and GitHub Actions, with a 7-day cooldown on routine bumps. Security updates are unaffected and ignore it.
  • Dependencies refreshed: cargo update (344 tests, clippy 1.99 pass) and pnpm update (check + pnpm audit clean).
  • README links https://vump.codehacks.io.

Worth knowing

The open time advisory is cleared (0.3.47) but time is in the lockfile only: no target compiles it. Its newer crates declare Rust 1.88 against this crate's 1.85, so cargo update alone had left it; I forced it with --precise. Nothing changes at runtime. If you would rather keep the lockfile MSRV-clean, drop that commit and dismiss the alert as not reachable.

Still yours: enable secret scanning and push protection in Settings → Code security.

🤖 Generated with Claude Code

okcodes and others added 5 commits October 21, 2026 22:49
A tag like @v2 is a pointer its owner can move, and release.yml runs these
actions beside the signing secrets. A commit SHA cannot be moved. The
version stays in a trailing comment so a reader and Dependabot can both see
what it is.

dtolnay/rust-toolchain chooses its toolchain from the ref it is called at, so
pinning the ref would have silently dropped the choice; it is now stated with
toolchain: stable. GitHub-owned actions stay on tags.

Co-Authored-By: Claude Sonnet 5.5 <[email protected]>
Security updates were already on and need no file. This adds weekly updates
for the three ecosystems — Cargo, the site's pnpm dependencies, and GitHub
Actions — grouped so a week is one pull request each rather than a stream.

A seven-day cooldown applies to routine bumps only: a release published
today may be one a maintainer's account was used to push a minute ago, and
waiting lets a compromised version be yanked before it arrives. Security
updates ignore the cooldown.

Co-Authored-By: Claude Sonnet 5.5 <[email protected]>
cargo update, including time 0.3.47 for the open advisory. time is in the
lockfile but no target compiles it, so nothing changes at runtime; its newer
crates declare Rust 1.88 against this crate's 1.85, which is why it stayed put
until forced.

Co-Authored-By: Claude Sonnet 5.5 <[email protected]>
pnpm update, then check and audit: typecheck, lint, format and the prerendered
build pass and pnpm audit reports nothing. @types/node stays on 24 rather than
jumping to 26.

Co-Authored-By: Claude Sonnet 5.5 <[email protected]>
@okcodes
okcodes merged commit 7e9be6b into main Oct 22, 2026
10 checks passed
@okcodes
okcodes deleted the security-hardening branch October 22, 2026 05:20
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.

1 participant