Runtime inventory
Root and nested Action metadata, every pre, main, and post entrypoint, and runner constraints mapped before edits.
For maintainers of commercial JavaScript Actions
Ship the Node 24 release before the escape hatch disappears.
A tested migration PR—not a one-line action.yml edit. I update the runtime, dependencies, checked-in bundle, CI coverage, and release notes as one fixed-scope delivery.
No GitHub login. No repository upload. The free check reads public metadata directly from GitHub in your browser.
2 business daysfor qualified simple Actions
$950 fixedone Action, agreed scope
PR + evidencetests, notes, release checklist
Free public-repository check
See what your Action declares today.
This quick check finds JavaScript Action metadata anywhere in a public repository and flags legacy runtime declarations. It is evidence for triage, not a compatibility guarantee.
Definition of done
The release work around the runtime change.
Every engagement starts with a repository audit and a written scope. A qualified simple Action includes these six deliverables.
Dependency migration
Runtime-sensitive packages reviewed and upgraded where required, with lockfile changes kept inside the agreed scope.
Rebuilt distribution
Checked-in bundles regenerated from source—not hand-edited—so Marketplace users receive the tested code.
Node 24 test proof
Existing tests run under Node 24, Action behavior exercised, and relevant hosted-runner operating systems covered.
Release-ready PR
A reviewable pull request with focused commits, exact verification results, compatibility notes, and no invented green checks.
Cutover checklist
Major-tag movement, Marketplace release notes, user upgrade guidance, rollback steps, and maintainer-owned publication.
Good fit
A maintained JavaScript Action with a bounded release.
- Public or access-granted private repository
- One Action or a small, related set of entrypoints
- Source and build process are present
- Existing tests or reproducible behavior to verify
- A maintainer is available to review and publish
Separate quote
Broader platform work needs broader scope.
- Application-wide Node upgrades or framework rewrites
- ARM32 replacement or self-hosted runner fleet upgrades
- Missing source for a committed distribution bundle
- Security certification, penetration testing, or uptime guarantees
- Unrelated backlog fixes bundled into the migration
Founding fixed scope
One qualified Action. One release-ready PR.
The public audit is free. If the repository fits the standard scope, the migration is fixed-price. If it does not, you receive the boundary before any payment is requested.
Read GitHub’s Node 20 deprecation notice →$950fixed
- Repository and runtime audit
- Metadata, dependency, and bundle changes
- Node 24 and relevant runner tests
- Release notes and cutover checklist
- One review round for in-scope findings
Target: 2 business days after written scope, repository access, deposit, and a reproducible baseline. Publication remains with the maintainer.
Request the free auditStraight answers
Before repository access changes hands.
Isn’t this just changing node20 to node24?
That edit declares the new runtime; it does not prove dependencies, bundled code, all entrypoints, or supported runners behave correctly. The service is scoped around reproducible release evidence.
Do you need admin access?
No. For a private repository, least-privilege read/write access sufficient to create a branch or fork is normally enough. You retain review, merge, tag, Marketplace, secrets, and publication control.
Can you guarantee compatibility?
No honest migration can guarantee every downstream environment. I report the exact matrix and behavior tested, document known exclusions, and do not label untested conditions as passing.
What about old self-hosted runners?
Node 24 requires a sufficiently current Actions runner and drops some older operating-system and ARM32 support. Fleet remediation is separate from the standard Action migration.
Who publishes the release?
You do. The deliverable is a release-ready PR and checklist. Tags, major-version movement, Marketplace updates, secrets, and production publication stay under maintainer control.
The default already changed
Start with the repository, not a sales call.
Send one public repo. You’ll get a concise fit/no-fit audit and a written boundary before any paid work.
Send the repository