Repository navigation
Checks and workflows for a weekly update routine - #18
Merged
Merged
Conversation
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>
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
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.
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:updatescompares what the repo pins with what is current, and names the lines to change.auto,optional,manualorunknown.raw.githubusercontent.com, the hosts a cloud routine can reach.npm run check:graphqlvalidates every query the templates send against Shopify's real schema, for the pinned version or one passed with--version.master, on Node 24.package.jsonchanges onmaster, and tags what it published.masterpublishes nothing.What the checks say today
check:updates: one finding,auto: Shopify API2026-07→2026-10, across 8 lines. Everything else is current.check:graphql: all 6 queries are valid against both2026-07and2026-10. Four deprecated fields are in use and still work:Product.featuredImageProduct.imagesShopPlan.displayNameShop.billingAddressTest plan
npm run test:e2e: 58/58 (42 existing, 16 new).🤖 Generated with Claude Code