Skip to content

Checks and workflows for a weekly update routine - #18

Merged
mksd0398 merged 2 commits into
masterfrom
weekly-update-check
Oct 10, 2026
Merged

mksd0398 merged 2 commits into
masterfrom
weekly-update-check

Conversation

@mksd0398

Copy link
Copy Markdown
Owner

Summary

Groundwork for a weekly routine that keeps Nitrogen current and releases the updates itself. Nothing here changes the published package, so there is no version bump.

  • npm run check:updates compares what the repo pins with what is current, and names the lines to change.
    • It covers npm dependency ranges (CLI and both templates), the Shopify API version, the Functions Node runtime, GitHub Actions versions, and new majors of the Firebase and Shopify CLIs.
    • Each finding is auto, optional, manual or unknown.
    • It reads only npm's registry and raw.githubusercontent.com, the hosts a cloud routine can reach.
  • npm run check:graphql validates every query the templates send against Shopify's real schema, for the pinned version or one passed with --version.
    • The templates' tests stub Shopify, so nothing else would notice a field a new API version removed.
    • It also lists deprecated fields.
  • A Test workflow runs the full suite and the schema check on every pull request and on master, on Node 24.
  • The publish workflow now also starts when package.json changes on master, and tags what it published.
    • A cloud routine can merge its own PR but cannot push a tag, so merging a version bump has to be a release.
    • Tag pushes and manual runs still work, and a version already on npm is still skipped.
    • Runs are serialised.
    • The tag is pushed by a separate job with its own write permission.
    • A manual run on a branch other than master publishes nothing.

What the checks say today

  • check:updates: one finding, auto: Shopify API 2026-07 → 2026-10, across 8 lines. Everything else is current.
  • check:graphql: all 6 queries are valid against both 2026-07 and 2026-10. Four deprecated fields are in use and still work:
    • Product.featuredImage
    • Product.images
    • ShopPlan.displayName
    • Shop.billingAddress

Test plan

  • npm run test:e2e: 58/58 (42 existing, 16 new).
  • Both checks run against live sources.
  • Both workflow files parse; the Test workflow runs on this PR.
  • The publish workflow's new trigger and tag job first run for real on the next version bump.

🤖 Generated with Claude Code

mksd0398 and others added 2 commits October 10, 2026 10:46
npm run check:updates compares what the repository pins with what is
current: npm dependency ranges in the CLI and both templates, the Shopify
API version, the Functions Node runtime, the GitHub Actions the workflows
use, and new majors of the Firebase and Shopify CLIs. It names the lines to
change and marks each finding auto, optional, manual or unknown. It reads
only npm's registry and raw.githubusercontent.com, which a restricted
network can still reach. The Shopify version comes from the quarterly
calendar, confirmed against Shopify's own library, because Shopify's version
table lists scheduled versions next to shipped ones.

npm run check:graphql validates every query the templates send against
Shopify's real schema for the version they pin, or for one passed with
--version. The templates' tests stub Shopify, so nothing else would notice a
field that a new API version removed. It also lists deprecated fields.

The tests work out their expectations from whatever the repository pins, so
they keep passing after a version is raised.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
A new Test workflow runs the full suite and the schema check on every pull
request and on master, on Node 24.

The publish workflow now also starts when package.json changes on master,
and tags what it published. A cloud routine can merge its own pull request
but cannot push a tag, so merging a version bump has to be a release. Tag
pushes and manual runs still work, a version already on npm is still
skipped, and runs are serialised so a merge and a tag for the same version
cannot both publish. The tag is pushed by a separate job, so the token that
can write to the repository is never present while dependencies run. A
manual run on a branch other than master publishes nothing.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@mksd0398
mksd0398 merged commit 8a90aa8 into master Oct 10, 2026
1 check passed
@mksd0398
mksd0398 deleted the weekly-update-check branch October 10, 2026 05:18
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