chore(ci): bump actions, add concurrency + cache + badges + step summaries#695
Open
ChonSong wants to merge 1 commit into
Open
chore(ci): bump actions, add concurrency + cache + badges + step summaries#695ChonSong wants to merge 1 commit into
ChonSong wants to merge 1 commit into
Conversation
…aries - checkout@v4 → @v5, setup-node@v4 → @v5, setup-qemu/buildx/login@v3, build-push@v5 → @v6 - Add concurrency groups (cancel-in-progress) to all workflows - Add pnpm store cache to CI - Add step summary to security + docker workflows - Use ::notice for non-blocking lint/typecheck skips - Add CI/Security/Docker status badges to README
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.
What changed
All workflows
cancel-in-progress: true) to prevent wasted CI on rapid pushesCI workflow
~/.pnpm-storekeyed on lockfile, cuts install time::noticeinstead of silentechoSecurity workflow
Docker workflow
README
Why
🤖 Agent Trace
Agent reasoning, searches, file writes — click to expand
Web searches 🔍
github actions checkout v5actions/setup-node v5 releasev5exists for Node 22 supportdocker/build-push-action v6 changelogactions/cache v5GitHub Actions step summary syntax$GITHUB_STEP_SUMMARYmarkdown renderinggithub actions annotation commands::notice::command syntaxFile writes & patches 📝
.github/workflows/ci.yml.github/workflows/security.ymlconcurrency, added scan-results step summary.github/workflows/docker-publish.ymlREADME.mdReasoning
@v4actions target Node 20 but GitHub runners now run Node 24. Deprecation warnings appear on every run and will break when GH drops Node 20 entirely.@v5targets Node 22+.echoskips (lint, typecheck, test) provide no feedback.::noticesurfaces them in the GitHub UI as yellow warnings on the commit.File read exploration 📄
Before writing, read the current state of all 4 workflow files + README to understand existing structure and identify each line that needed changes.