[Breaking] Remove ApiVersion::LATEST constant #434
Merged
Conversation
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
…tion Prevent semantic versioning violations where library updates automatically change API versions, potentially breaking production apps without developer awareness or control Breaking change: apiVersion parameter now required in Context::initialize() Migration: Developers must explicitly specify API version (e.g., '2025-10') Aligns with Ruby library PR #1411 and broader Shopify library strategy See BREAKING_CHANGES_FOR_V6.md for complete migration guide 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude <noreply@anthropic.com>
lizkenyon
force-pushed
the
remove-latest-api-constant
branch
from
cb51a1f to
a30842c
Compare
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.
WHAT is this pull request doing?
Remove ApiVersion::LATEST constant and require explicit version selection
Prevent semantic versioning violations where library updates automatically change API versions, potentially breaking production apps without developer awareness or control
Breaking change: apiVersion parameter now required in Context::initialize() Migration: Developers must explicitly specify API version (e.g., '2025-10') Aligns with Ruby library PR #1411 and broader Shopify library strategy See BREAKING_CHANGES_FOR_V6.md for complete migration guide
Type of change
Checklist