Repository navigation
ci(audit): put the remediation summary and semantic change check on main [skip changelog] - #161
Merged
Merged
Conversation
…ain [skip changelog] Same four CI files as #160 (audit-remediate.yml, scripts/audit-remediate.mjs and its two test files), byte for byte. Workflows run from main, so the job summary / notice output and the audited-version change check only take effect once they are on main. AGENTS.md and CHANGELOG.md stay on develop with #160 and ship with the next release. Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_012ESxuEjCeVsRAAxAb29Yjr
Contributor
Coverage Report
File CoverageNo changed files found. |
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.
Summary
Companion to #160, same relationship as #159 had to #158. Workflows run from
main, so the job-summary/notice output and the audited-version change check from #160 only take effect once they are onmain. This PR puts exactly those four CI files onmainnow instead of waiting for a release.Merge as a merge commit, never squash or rebase.
backmerge.ymlthen carries it intodevelop.What is in it
Byte for byte the same as #160 (verified with an empty
git diffagainst its head), four files:.github/workflows/audit-remediate.ymlscripts/audit-remediate.mjstests/automation/audit-remediate.node-test.mjstests/automation/audit-remediate-workflow.node-test.mjs(new)AGENTS.mdandCHANGELOG.mdedits stay on #160 and ship with the next release (hence[skip changelog], as in #133 and #159). See #160 for what changes and why: every outcome now shows on the run page (job summary plus a notice), and "did the update change anything" compares the versions of the audited packages instead of lockfile text.Verification
main-based tree with only these four files: 101 automation tests pass,npm run checkpasses (598 tests).develop, it cleanly carries the same four files, so the merge order of ci(audit): show the remediation result on the run page; judge changes by audited versions #160 and this PR does not matter.Not verified
audit-remediate.ymlshould now show its result on the run page itself.Type of change
Checklist
npm testpasses locally (598 passed, 29 skipped);node --test tests/automation/*.node-test.mjs101 passednpx tsc --noEmitpasses locallyGenerated by Claude Code