feat(ci): onboard vitest-runner onto the CLDMV v4 release flow - #2
Closed
Shinrai wants to merge 1 commit into
Closed
feat(ci): onboard vitest-runner onto the CLDMV v4 release flow#2Shinrai wants to merge 1 commit into
Shinrai wants to merge 1 commit into
Conversation
Replace the standalone ci.yml with thin callers of the CLDMV/.github @v4 reusable workflows and install the full v4 release-flow + core-cicd + security entry callers. Workflows added/replaced (.github/workflows/): ci.yml (replaces standalone), feature-pr.yml, hotfix-redirector.yml, next-release.yml, next-reset.yml, hotfixes-release.yml, pr-title-normalizer.yml, publish.yml, codeql.yml, scorecard.yml, master-commit-audit.yml, update-major-version-tags.yml, v4-bootstrap.yml Per-repo customizations: package_name=@cldmv/vitest-runner; type_check_command=npm run types:check; max_node_major=24 (keeps Node 24 LTS in the matrix, matching old CI). package.json: add build:ci = lint && format:check && types:build, so the lint + format gates the old standalone CI ran are preserved (workflow-ci@v4 does not run lint/format itself) and publish/CI regenerate types from source.
Contributor
Author
|
Closing in favor of #1. Both PRs carry the same head ( |
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
1 participant
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.
Onboards vitest-runner onto the CLDMV v4 flow. This scaffold PR targets
masterbecause the repo isn't on the staging flow yet; after merge,next/hotfixesfast-forward to master (they're strict ancestors — no history lost) and the flow activates.ci.ymlwith theworkflow-ci.yml@v4caller + adds the full v4 suite (release-flow,publish,codeql,scorecard,master-commit-audit,update-major-version-tags,v4-bootstrap).build:ci=lint && format:check && types:buildso the reusable CI keeps the lint + format gates the old standalone CI had (the reusable doesn't run them on its own) and regenerates the trackedtypes/.CLDMV_BOT_APP_ID→CLDMV_BOT_APP_CLIENT_ID;type_check_command → npm run types:check; Node matrix 20/22/24.Validated: YAML + actionlint clean;
npm run build:ciruns green (types regenerate byte-identical). After merge: FFnext/hotfixesto master, dispatchv4-bootstrap, confirm org bot + GPG +NPM_TOKENsecrets. The pendingfix/coverage-summary-nonnumeric-pct-guardbug fix then opens cleanly againstnext.