[Breaking] Remove deprecated storefront_access_token positional parameter #1414
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
…torefront client This removes the deprecation introduced in PR #1302 (v14.1.0) in preparation for the v15.0.0 major release. Users must now use named parameters (private_token: or public_token:) instead of passing the token as a positional argument. Updated Storefront client to raise ArgumentError when no token is provided, updated tests to use named parameters, and added breaking change documentation with migration examples. 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude <noreply@anthropic.com>
3d67213 to
2fb80f2
Compare
sle-c
approved these changes
Oct 20, 2025
lizkenyon
added a commit
that referenced
this pull request
Oct 21, 2025
…t-token [Breaking] Remove deprecated storefront_access_token positional parameter
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 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.
Description
Remove deprecated storefront_access_token positional parameter from Storefront client
This removes the deprecation introduced in PR #1302 (v14.1.0) in preparation for the v15.0.0 major release. Users must now use named parameters (private_token: or public_token:) instead of passing the token as a positional argument.
Updated Storefront client to raise ArgumentError when no token is provided, updated tests to use named parameters, and added breaking change documentation with migration examples.
Fixes #
Please, include a summary of what the PR is for:
How has this been tested?
Please, describe the tests that you ran to verify your changes.
Checklist: