mirror of
https://github.com/yamadashy/repomix.git
synced 2026-09-19 06:00:49 +08:00
4ee4b38b7c
The scoped `npm_config_min_release_age: 0` from the previous commit does not resolve the conflict: npm's git-dep preparation spawns a child `npm install` that re-reads repomix's .npmrc (min-release-age=7) and adds its own --before, which cannot coexist — and 0 still counts as "provided". CI confirmed the website server jobs still fail with it. decision(ci-min-release-age): keep the npm@11.4.0 downgrade (the verified-green fix, matching Dockerfile) and restore the zizmor adhoc-packages exemption learned(min-release-age): npm_config_min_release_age=0 does not fix the git-dep --before conflict — the value counts as provided and the prep child re-reads .npmrc; only an npm that predates the flag avoids it Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
25 lines
895 B
YAML
25 lines
895 B
YAML
rules:
|
|
artipacked:
|
|
ignore:
|
|
# git-auto-commit-action requires persist-credentials for pushing
|
|
- schema-update.yml
|
|
secrets-outside-env:
|
|
ignore:
|
|
# These workflows use repository-level secrets without dedicated environments,
|
|
# which is acceptable for this project's threat model
|
|
- ci.yml
|
|
- claude-code-review.yml
|
|
- claude-issue-similar.yml
|
|
- claude-issue-triage.yml
|
|
- claude.yml
|
|
adhoc-packages:
|
|
ignore:
|
|
# Installing repomix at a user-specified version is this action's core function,
|
|
# so it cannot go through a lockfile
|
|
- action.yml
|
|
# Intentional: update npm itself to latest before publishing
|
|
- npm-publish.yml
|
|
# Intentional: downgrade npm to 11.4.0 so it can prepare the github:repomix
|
|
# git dependency without the min-release-age/--before conflict in npm 12
|
|
- ci-website.yml
|