Skip to content

Update @spree/sdk and @spree/next to 0.2.0#20

Merged
damianlegawiec merged 1 commit intomainfrom
update-spree-sdk-0.2.0
Feb 14, 2026
Merged

Update @spree/sdk and @spree/next to 0.2.0#20
damianlegawiec merged 1 commit intomainfrom
update-spree-sdk-0.2.0

Conversation

@damianlegawiec
Copy link
Member

@damianlegawiec damianlegawiec commented Feb 14, 2026

Summary

  • Bump @spree/sdk from ^0.1.4 to ^0.2.0
  • Bump @spree/next from ^0.1.1 to ^0.2.0
  • Rename env var SPREE_API_KEYSPREE_PUBLISHABLE_KEY in .env.example, .env.local.example, and README.md

SDK v0.2.0 restructures the client to support dual API namespaces (client.store.* and client.admin.*). The @spree/next package handles the namespace internally, so no source code changes are needed in the starter.

Test plan

  • All 58 tests pass (npm run test)
  • Manual smoke test with local Spree instance

🤖 Generated with Claude Code

Summary by CodeRabbit

Chores

  • Updated environment variable naming from SPREE_API_KEY to SPREE_PUBLISHABLE_KEY across configuration files and documentation.
  • Upgraded @spree/next and @spree/sdk package dependencies to version 0.2.0.

Bump SDK packages to v0.2.0 which introduces dual API namespaces
(client.store.* and client.admin.*). Rename env var SPREE_API_KEY
to SPREE_PUBLISHABLE_KEY to match the new SDK config.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
@coderabbitai
Copy link

coderabbitai bot commented Feb 14, 2026

Walkthrough

Configuration files and documentation are updated to replace the environment variable SPREE_API_KEY with SPREE_PUBLISHABLE_KEY. Additionally, Spree SDK dependencies (@spree/next and @spree/sdk) are bumped from version ^0.1.x to ^0.2.0 in package.json.

Changes

Cohort / File(s) Summary
Environment & Documentation Configuration
.env.example, .env.local.example, README.md
Updated environment variable references from SPREE_API_KEY to SPREE_PUBLISHABLE_KEY across example configurations and deployment documentation.
Dependency Version Updates
package.json
Bumped @spree/next and @spree/sdk from ^0.1.x to ^0.2.0.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

Possibly related PRs

Poem

🐰 A publishable key hops into view,
Where secrets once lived, now transparency shines through!
Dependencies leap from point-one to the next,
Our Spree grows stronger—what happens next? ✨

🚥 Pre-merge checks | ✅ 4
✅ Passed checks (4 passed)
Check name Status Explanation
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Title check ✅ Passed The title accurately reflects the main change in the PR: bumping @spree/sdk and @spree/next to 0.2.0 in package.json, which is the primary technical change.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Merge Conflict Detection ✅ Passed ✅ No merge conflicts detected when merging into main

✏️ Tip: You can configure your own custom pre-merge checks in the settings.

✨ Finishing touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Post copyable unit tests in a comment
  • Commit unit tests in branch update-spree-sdk-0.2.0

No actionable comments were generated in the recent review. 🎉

🧹 Recent nitpick comments
.env.example (1)

3-3: Nit: placeholder value inconsistency across env examples.

This file uses your_publishable_api_key while .env.local.example uses your_publishable_api_key_here. Consider aligning them for consistency.


Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands and usage tips.

@damianlegawiec damianlegawiec merged commit c1b7cd4 into main Feb 14, 2026
4 checks passed
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