Skip to content

chore(release): release packages#2013

Merged
filiphsps merged 1 commit into
masterfrom
changeset-release/master
Jun 16, 2026
Merged

chore(release): release packages#2013
filiphsps merged 1 commit into
masterfrom
changeset-release/master

Conversation

@github-actions

@github-actions github-actions Bot commented May 28, 2026

Copy link
Copy Markdown
Contributor

This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to master, this PR will be updated.

Releases

@nordcom/cart-core@0.2.0

Minor Changes

  • #2018 f4500a5 Thanks @filiphsps! - Add a clear cart mutation and clear() action so emptying the cart issues one bulk line removal instead of one removeLine per line.

  • #1945 d5133c3 Thanks @filiphsps! - Initial publish: framework-agnostic cart kernel, types, capabilities, adapter contract, middleware (logger, tracing, idempotency, retry, analytics), event bus, money helpers, contract tests, and mock adapter.

Patch Changes

  • f78ea78 Thanks @filiphsps! - Refresh the shared dev/build toolchain (vite, vitest, concurrently) and the React/Next dev pins to their latest releases as part of a monorepo-wide dependency upgrade. Internal-only — published runtime dependencies and peer ranges are unchanged.

  • #1960 72bdabe Thanks @filiphsps! - Backfill JSDoc on public/internal symbols.

@nordcom/cart-next@0.2.0

Minor Changes

  • #1945 d5133c3 Thanks @filiphsps! - Initial publish: Next.js 16 HttpOnly cookie storage, react.cache() reader/ensurer (no 'use cache'), typed + FormData server-action factories with injectable message localizer + auth bridge, and nextEventBridge for kernel-side fire-and-forget effects.

Patch Changes

  • f78ea78 Thanks @filiphsps! - Refresh the shared dev/build toolchain (vite, vitest, concurrently) and the React/Next dev pins to their latest releases as part of a monorepo-wide dependency upgrade. Internal-only — published runtime dependencies and peer ranges are unchanged.

  • 518289c Thanks @filiphsps! - Fix uncaught CartProviderError escaping the Server Action boundary. resolveContext() was called before the try/catch in run(), so any context-resolution failure (missing request headers, DB error) bubbled as a raw unhandled exception instead of returning { ok: false, reason: 'provider-error' }. Moved resolveContext inside the try block so all failure modes are handled uniformly.

  • #1992 4ca9f4d Thanks @filiphsps! - Add missing @example blocks on Tier-1 functions per review.

  • #1990 ffdaa4d Thanks @filiphsps! - Backfill JSDoc on public/internal symbols.

  • Updated dependencies [f78ea78, f4500a5, d5133c3, 72bdabe]:

    • @nordcom/cart-core@0.2.0

@nordcom/cart-react@0.2.0

Minor Changes

  • #2018 f4500a5 Thanks @filiphsps! - Add a clear cart mutation and clear() action so emptying the cart issues one bulk line removal instead of one removeLine per line.

  • #1945 d5133c3 Thanks @filiphsps! - Initial publish: React 19 provider with slice contexts, predictive mutation queue with cascade-cancel and cross-tab sync, capability-typed actions, line + cart predictors, <CartForm> zero-JS primitive, and ./devtools panel.

Patch Changes

  • f78ea78 Thanks @filiphsps! - Refresh the shared dev/build toolchain (vite, vitest, concurrently) and the React/Next dev pins to their latest releases as part of a monorepo-wide dependency upgrade. Internal-only — published runtime dependencies and peer ranges are unchanged.

  • f690eb9 Thanks @filiphsps! - Fix cartReady permanently stuck at false. seededRef was read inside a useMemo factory but not included in the dependency array — after setInitial dispatch state.pending stayed the same array reference, so the memo never recomputed and cartReady never became true. Replaced the ref with useState so React tracks the transition and recomputes the status slice correctly on mount.

  • #1969 47ae0b0 Thanks @filiphsps! - Address jsdoc review followups: missing @example on Props types, capability-mixin example typings, American English.

  • #1967 f0047c2 Thanks @filiphsps! - Backfill JSDoc on public/internal symbols.

  • Updated dependencies [f78ea78, f4500a5, d5133c3, 72bdabe]:

    • @nordcom/cart-core@0.2.0

@nordcom/cart-shopify@0.2.0

Minor Changes

  • #1945 d5133c3 Thanks @filiphsps! - Initial publish: Shopify cart adapter using an injected ShopifyTransport, gql.tada mutations + normalizer, all-capabilities-on by default, updateBuyerCountry custom mutation, and mockShopifyTransport testing utility.

Patch Changes

  • f78ea78 Thanks @filiphsps! - Refresh the shared dev/build toolchain (vite, vitest, concurrently) and the React/Next dev pins to their latest releases as part of a monorepo-wide dependency upgrade. Internal-only — published runtime dependencies and peer ranges are unchanged.

  • #1970 16d77ff Thanks @filiphsps! - Add missing @example to mockShopifyTransport per Tier-1 spec.

  • #1965 3a5af48 Thanks @filiphsps! - Backfill JSDoc on public/internal symbols.

  • Updated dependencies [f78ea78, f4500a5, d5133c3, 72bdabe]:

    • @nordcom/cart-core@0.2.0

next-build-notifier@0.2.0

Minor Changes

  • #2034 d500a1b Thanks @filiphsps! - Add next-build-notifier: a headless "new build available" indicator for Next.js. Generic build detection (any host) with first-class Vercel support, exposed as a config wrapper (withBuildNotifier), a route-handler factory (createVersionRoute), and a headless client API (BuildNotifierProvider / useBuildNotification / <BuildNotifier>).

react-payment-brand-icons@0.2.1

Patch Changes

  • f78ea78 Thanks @filiphsps! - Refresh the shared dev/build toolchain (vite, vitest, concurrently) and the React/Next dev pins to their latest releases as part of a monorepo-wide dependency upgrade. Internal-only — published runtime dependencies and peer ranges are unchanged.

  • #2028 d6b2cf0 Thanks @filiphsps! - Wipe the generated icons/ output directory before re-emitting. A removed or renamed SVG — or a stale module from an earlier generator that emitted a different file extension — could otherwise linger and be picked up by the extensionless icon imports (vite resolves .js ahead of .tsx, so an orphan JSX-bearing .js broke the build locally).

@tagtree/core@0.0.3

Patch Changes

  • f78ea78 Thanks @filiphsps! - Refresh the shared dev/build toolchain (vite, vitest, concurrently) and the React/Next dev pins to their latest releases as part of a monorepo-wide dependency upgrade. Internal-only — published runtime dependencies and peer ranges are unchanged.

  • #1958 cab9aa7 Thanks @filiphsps! - Backfill JSDoc on public/internal symbols.

@tagtree/next@0.0.3

Patch Changes

  • f78ea78 Thanks @filiphsps! - Refresh the shared dev/build toolchain (vite, vitest, concurrently) and the React/Next dev pins to their latest releases as part of a monorepo-wide dependency upgrade. Internal-only — published runtime dependencies and peer ranges are unchanged.

  • #1956 a815f10 Thanks @filiphsps! - Backfill JSDoc on public/internal symbols.

  • Updated dependencies [f78ea78, cab9aa7]:

    • @tagtree/core@0.0.3

@tagtree/shopify@0.0.3

Patch Changes

  • f78ea78 Thanks @filiphsps! - Refresh the shared dev/build toolchain (vite, vitest, concurrently) and the React/Next dev pins to their latest releases as part of a monorepo-wide dependency upgrade. Internal-only — published runtime dependencies and peer ranges are unchanged.

  • #1959 ba1011b Thanks @filiphsps! - Address jsdoc review followups on parseShopifyWebhook.

  • #1955 5f183c9 Thanks @filiphsps! - Backfill JSDoc on public/internal symbols.

  • Updated dependencies [f78ea78, cab9aa7]:

    • @tagtree/core@0.0.3

@codecov

codecov Bot commented Jun 13, 2026

Copy link
Copy Markdown

Bundle Report

Bundle size has no change ✅

@github-actions

Copy link
Copy Markdown
Contributor Author

Coverage Report

Status Category Percentage Covered / Total
🔵 Lines 84.18% (🎯 65%) 9276 / 11019
🔵 Statements 82.97% (🎯 60%) 10125 / 12202
🔵 Functions 83.2% (🎯 75%) 2463 / 2960
🔵 Branches 71.37% (🎯 50%) 5824 / 8160
File CoverageNo changed files found.
Generated in workflow #13110 for commit 30672c0 by the Vitest Coverage Report Action

@codecov

codecov Bot commented Jun 15, 2026

Copy link
Copy Markdown

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 83.94%. Comparing base (775f2ec) to head (30672c0).
⚠️ Report is 29 commits behind head on master.
✅ All tests successful. No failed tests found.

Additional details and impacted files
@@           Coverage Diff           @@
##           master    #2013   +/-   ##
=======================================
  Coverage   83.94%   83.94%           
=======================================
  Files         603      603           
  Lines       13651    13651           
  Branches     3986     3986           
=======================================
  Hits        11459    11459           
  Misses       2192     2192           
Components Coverage Δ
App: Storefront 82.87% <ø> (ø)
App: Admin 88.66% <ø> (ø)
App: Landing ∅ <ø> (∅)
Pkg: @nordcom/commerce-db 89.16% <ø> (ø)
Pkg: @nordcom/commerce-errors 100.00% <ø> (ø)
Pkg: @nordcom/commerce-marketing-common ∅ <ø> (∅)
Pkg: @nordcom/commerce-shopify-graphql 100.00% <ø> (ø)
Pkg: @nordcom/commerce-shopify-html 94.93% <ø> (ø)
Layer: Apps 84.28% <ø> (ø)
Layer: Packages 79.72% <ø> (ø)
Flag Coverage Δ
unit 83.94% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

Releases:
  @nordcom/cart-core@0.2.0
  @nordcom/cart-next@0.2.0
  @nordcom/cart-react@0.2.0
  @nordcom/cart-shopify@0.2.0
  @tagtree/core@0.0.3
  @tagtree/next@0.0.3
  @tagtree/shopify@0.0.3
  react-payment-brand-icons@0.2.1
  next-build-notifier@0.2.0
@github-actions github-actions Bot force-pushed the changeset-release/master branch from 30672c0 to 890ddf0 Compare June 16, 2026 04:48
@filiphsps filiphsps merged commit bdf6d58 into master Jun 16, 2026
2 of 4 checks passed
@filiphsps filiphsps deleted the changeset-release/master branch June 16, 2026 04:58
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