Skip to content

ci: shared-actions v2.4.0 — no npm cache on self-hosted, CI-only PRs skip the bump gate - #19

Merged
robgilbreath merged 1 commit into
masterfrom
ci/shared-actions-v2.4.0
Sep 3, 2026
Merged

robgilbreath merged 1 commit into
masterfrom
ci/shared-actions-v2.4.0

Conversation

@robgilbreath

Copy link
Copy Markdown

Moves validate-codebase and verify-version-bump to shared-actions v2.4.0 (dfb52a3).

  • pncit/shared-actions#32validate-codebase no longer passes cache: npm on self-hosted runners. On the fleet ~/.npm persists between jobs, so the cache was a restore miss plus a ~1 GB post-job upload of the shared ~/.npm on every lockfile-changing job (every Dependabot PR), and an interrupted upload left cache-save processes spinning at 100 % CPU on the runner host. Where this repo's npm-publish.yml runs its own setup-node on self-hosted, that step drops the same flag.
  • pncit/shared-actions#33verify-version-bump exempts PRs that touch only .github/** from the bump gate. Nothing such a PR changes ships, so there is nothing to publish; the publish side still compares to HEAD^ and skips. This PR is the first to use it: no version bump, no release.

Public repos: both vendored .github/actions/* copies resynced byte-for-byte (banner comment only). Tracked on pncit/.github#26.

…skip the bump gate

validate-codebase (shared-actions#32): `cache: npm` on the self-hosted
fleet was a restore miss plus a ~1 GB post-job upload of the shared
~/.npm on every lockfile-changing job, and an interrupted upload left a
cache-save process spinning at 100 % CPU. v2.3.0 caches on GitHub-hosted
runners only; the publish job's own setup-node loses the same flag here.

verify-version-bump (shared-actions#33): PRs that touch only `.github/**`
no longer need a package.json bump — nothing they change ships, so there
is nothing to publish. This PR is the first such: no bump, no release.
@robgilbreath
robgilbreath merged commit da6f0ce into master Sep 3, 2026
1 check passed
@robgilbreath
robgilbreath deleted the ci/shared-actions-v2.4.0 branch September 3, 2026 04:10
robgilbreath added a commit that referenced this pull request Sep 3, 2026
npm publish over an existing version is a hard E403, so every merge to
master that didn't bump package.json (Dependabot's, and CI-only PRs now
that verify-version-bump exempts them) ended in a red publish run —
run 33714086138 after #19. Look the version up first, as
datto-rmm-api-client and timezest already do; the package is
access: restricted, so the lookup uses the read-only NPM_TOKEN while
the publish itself stays on OIDC trusted publishing.
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