Remove hardcoded version from theme duplicate API call#6737
Merged
Conversation
Contributor
Coverage report
Show new covered files 🐣
Show files with reduced coverage 🔻
Test suite run success3718 tests passing in 1438 suites. Report generated by 🧪jest coverage report action from fa8364d |
EvilGenius13
approved these changes
Jan 2, 2026
graygilmore
approved these changes
Jan 5, 2026
Contributor
|
This PR seems inactive. If it's still relevant, please add a comment saying so. Otherwise, take no action. |
Now that the public theme duplicate mutation is in in latest (rather than release candidate) we no longer need to specify `2025-10` as the version This commit removes the hardcoded version value from the theme duplicate API call
dejmedus
force-pushed
the
jb-remove-hardcoded-version
branch
from
605f82f to
fa8364d
Compare
graygilmore
approved these changes
Feb 5, 2026
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
3 participants
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 are these changes introduced?
To create the
theme duplicateCLI command we needed to add a new public mutation to the admin graphql API. The mutation was added to the2025-10version of the API and since that version was not yet supported we needed to point to it specifically in order to use it as part of the commandNow that
2025-10is the latest API version we no longer need to hardcode itWHAT is this pull request doing?
This PR removes the hardcoded
version: 2025-10from the theme duplicate API callHow to test your changes?
gh pr checkout 6737(somethings up with snapit 🤔 )pnpm shopify theme duplicatestill works as expectedMeasuring impact
How do we know this change was effective? Please choose one:
Checklist