Skip to content

chore(deps): bump commerce-elastic-path to 0.5.0 in canvas-packages, loader-bundle-env and the example app - #509

Merged
field123 merged 1 commit into
masterfrom
chore/ep-bump-commerce-050-consumers
Aug 28, 2026
Merged

chore(deps): bump commerce-elastic-path to 0.5.0 in canvas-packages, loader-bundle-env and the example app#509
field123 merged 1 commit into
masterfrom
chore/ep-bump-commerce-050-consumers

Conversation

@field123

Copy link
Copy Markdown
Collaborator

@elasticpath/plasmic-ep-commerce-elastic-path 0.5.0 is published. Three consumers
pinned ^0.4.1, and a caret range on a 0.x version pins the minor — ^0.4.1 means
>=0.4.1 <0.5.0 — so none of them would have moved to 0.5.0 on their own.

  • platform/canvas-packages — code components the Studio canvas renders
  • platform/loader-bundle-env — the bundle the loader/renderer serves
  • examples/ep-commerce-app-router — reference storefront

Without this, both the canvas and the loader keep serving 0.4.1 after the
commerce-elastic-path hostless bundle is republished, so designers still see the
Sort prop that 0.5.0 removes (#502) and the pre-#481 Category ID label.

Each is a separate yarn project, so each yarn.lock is regenerated in its own
directory. All three now resolve 0.5.0 from the registry.

Worth noting: EP Fork Integrity asserts only that these two declare the dependency,
never which version, so a stale pin here passes CI silently. The version-equality check
covers plasmicpkgs-dev alone.

Follows the same shape as #468, which did this for 0.4.1.

…loader-bundle-env and the example app

These pinned `^0.4.1`, and a caret on a 0.x version pins the minor, so none of
them would have picked up 0.5.0 on their own. The canvas and the loader would
have kept serving the removed Sort prop after the hostless republish.
@field123
field123 merged commit 37a108a into master Aug 28, 2026
9 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