Move validate/publish to ubuntu-latest; release 2.0.53 - #13
Merged
Merged
Conversation
…heck The org runner group rejects jobs from public repos, so `runs-on: self-hosted` has left every run since 2026-06-19 unschedulable. Switch both workflows to GitHub-hosted runners and install the .nvmrc Node ahead of verify-node-toolchain so it checks our toolchain, not the image's system Node. Refs pncit/.github#3 Co-Authored-By: Claude Code <noreply@anthropic.com>
CI-only release: every PR into master must bump the version (validate.yml gate), and this one moves the workflows to GitHub-hosted runners. Refs pncit/.github#3 Co-Authored-By: Claude Code <noreply@anthropic.com>
Was floating on @latest. Org standard is npm 12 (matches shared-actions validate-codebase, which pins 12.0.2); npm/cli#9722 was fixed in 12.0.1. Co-Authored-By: Claude Code <noreply@anthropic.com>
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.
Why
The org's self-hosted runner group has
allows_public_repositories: false(correctly — it keeps fork PRs off the fleet), so this public repo'sruns-on: self-hostedjobs can never be scheduled. Every Validate run since 2026-06-19 has been cancelled/queued; the two open Dependabot PRs (#10, #11) are among them.What changed
validate.ymlandnpm-publish.yml:runs-on: self-hosted->runs-on: ubuntu-latest.validate.yml: addactions/setup-node(node-version-file: .nvmrc) beforeverify-node-toolchain. That vendored action assertsnode/npmmajors against the org vars (NODE_MAJOR_VERSION=24/NPM_MAJOR_VERSION=11) and previously relied on the self-hosted box having Node 24 preinstalled; on the hosted image it would have checked Ubuntu's system Node. Node 24 bundles npm 11, so the check passes unchanged.validate-codebaseruns setup-node again afterwards — cache hit, harmless.ifgate is now a policy choice rather than a runner-safety requirement, matchingdatto-rmm-api-client.package.json2.0.52 -> 2.0.53: the validate gate requires a version bump on every PR (no Dependabot exemption, per Apply version-bump gate to Dependabot PRs too (release 2.0.52) #9), so this ships as a CI-only release, same as Apply version-bump gate to Dependabot PRs too (release 2.0.52) #9 did.Nothing in either workflow depended on runner-local state: publish auth is OIDC trusted publishing (
id-token: write),npm cihits registry.npmjs.org, and no cached paths or local registries are referenced.datto-rmm-api-clientruns the same steps onubuntu-latestsuccessfully.Refs pncit/.github#3
🤖 Generated with Claude Code
Also pins npm@12.0.2 in publish (was floating on @latest).