Skip to content

Instantly share code, notes, and snippets.

View screeny05's full-sized avatar

Sebastian Langer screeny05

View GitHub Profile
@screeny05
screeny05 / CHANGELOG.md
Created August 26, 2026 20:56
Core 0.44.0 + 0.45.0, UI 2.16.0 + 2.17.0 + 2.18.0 + 2.19.0

Release notes

Orchestr 0.44.0

Minor Changes

  • OpenTelemetry tracing. A storefront that sets OTEL_EXPORTER_OTLP_ENDPOINT at build time exports traces of its server-side work through the standard OTEL_* configuration; without it nothing is installed. Queries, links and component resolvers each become spans nested under the Nitro request span, and an upstream API call made while a resolver runs nests under that resolver — so a trace attributes upstream time to the work that caused it.

    What spans carry. Attributes are counts and names a backend can group by: how many entities a resolver asked for, a token name, the app a handler comes from. Entity-id lists, link payloads and handler metadata stay in the local dev tree that feeds devtools, because a span over a backend's payload ceiling is dropped whole — which would lose the slowest requests first.

@screeny05
screeny05 / CHANGELOG.md
Created August 24, 2026 08:24
Core 0.43.1, UI 2.15.0, Cockpit

Release notes

Orchestr 0.43.1

Patch Changes

  • Query, link and entity-component caches now key on the market, and query and link caches also key on the pagination limit. Two markets that share a language and a currency no longer read each other's cached results, and a request for 24 items no longer receives the slice a different page size cached.

    The key format changed, so existing cache entries become unreachable on upgrade and expire on their own TTL. Expect one cold period after the deploy.

@screeny05
screeny05 / CHANGELOG.md
Created August 21, 2026 14:52
Core 0.42.0 + 0.43.0, UI 2.13.0 + 2.14.0, Canonical Types 0.30.0

Release notes

Core 0.42.0

Minor Changes

  • Add the consent-aware analytics system. useAnalytics() returns { track, register, unregister }; track(Token, payload) emits a typed event whose token carries its own payload schema. @laioutr-core/core-types/analytics provides the token factories and the platform's own web/* events, @laioutr-core/canonical-types/analytics the ecommerce/* commerce vocabulary.

    Breaking: the specialized tracking composables are removed.

@screeny05
screeny05 / CHANGELOG.md
Created August 13, 2026 15:55
Core 0.41.0, UI 2.11.0, UI 2.12.0

Release notes

Core 0.41.0

Minor Changes

  • Markets can be set to draft, and a project can name its default market.

    A draft market still serves its own host so it can be checked before launch, but it is excluded from hreflang alternates, og:locale:alternate, x-default, and market switchers, and its pages

@screeny05
screeny05 / CHANGELOG.md
Last active August 6, 2026 09:42
Core 0.40, Canonical Types 0.27.0, UI 2.10.3, Shopware 0.14.0

Release notes

Core 0.39.0

Minor Changes

  • Internal: Add a laioutr:// resource locator for addressing a single field inside a project's configuration tree.

Core 0.40.0

@screeny05
screeny05 / CHANGELOG.md
Created August 3, 2026 14:15
Frontend-Core 0.38.3 & UI 2.10.0 & GTM 1.2.0

Release notes

Core 0.38.3

Patch Changes

  • Stop the reflect endpoint from serving a previous deployment's section and block catalog. Its cached reflection is now keyed by build id, so a redeploy is a cache miss instead of inheriting whatever the last build left behind, and two frontends sharing one Redis no longer overwrite each other's entry. Cached entries expire
@screeny05
screeny05 / CHANGELOG.md
Created August 1, 2026 08:38
Frontend-Core 0.38.2

Release notes

Core 0.38.1

Patch Changes

  • Add aiDisclosure to Media, recording whether an asset was fully AI-generated ('generated') or altered by generative AI ('modified'). Available on images, videos and audio; a video's poster and an audio's cover carry their own value independently of the parent.
@screeny05
screeny05 / CHANGELOG.md
Created July 30, 2026 12:42
Frontend-Core 0.38.0

Release notes

Core 0.38.0

Minor Changes

  • Fill hreflang alternates, og:locale:alternate, x-default and the locale switcher with each locale's own route params instead of the current locale's.

    On a page whose slug is translated per locale, the alternate URLs and the locale-switch target previously reused the current locale's params — pointing at URLs that do not exist in the target locale. Where the page type's pageIndex registration implements locate and reports a complete per-locale map, each locale now gets its own slug, and locales the page does not exist in are omitted from the alternates rather than guessed at.

@screeny05
screeny05 / CHANGELOG.md
Created July 14, 2026 02:44
Frontend-Core 0.35.0

Release notes

Core 0.34.0

Minor Changes

  • Add a configurable trailing-slash policy via RcProject.config.trailingSlash (default false). Routes, canonical/hreflang links, switch-locale/market URLs, and the useMarketPath helper are generated in the configured shape, and a Nitro server middleware issues a 301 normalizing the opposite shape. The policy is also applied to Nuxt's <NuxtLink> default so client-side navigation hrefs match, and the active value is readable at runtime via runtimeConfig.public.laioutr.trailingSlash. Domain path prefixes are normalized, so single- and multi-segment prefixes (/fr, /en/us) — including ones written with a stray trailing slash — compose correctly. Fixes homepage alternate/canonical links carrying a trailing slash on path-prefixed domains (/fr/ → /fr). The root path / is unaffected.

On path-prefixed domains the homepage now resolves correctly instead of falling through to the 404 page (the core/404 catch-all is no longer market-prefixed, so

@screeny05
screeny05 / CHANGELOG.md
Created July 13, 2026 15:51
Frontend-Core 0.34.0

Release notes

Core 0.34.0

Minor Changes

  • Add a configurable trailing-slash policy via RcProject.config.trailingSlash (default false). Routes, canonical/hreflang links, switch-locale/market URLs, and the useMarketPath helper are generated in the configured shape, and a Nitro server middleware issues a 301 normalizing the opposite shape. The policy is also applied to Nuxt's <NuxtLink> default so client-side navigation hrefs match, and the active value is readable at runtime via runtimeConfig.public.laioutr.trailingSlash. Domain path prefixes are normalized, so single- and multi-segment prefixes (/fr, /en/us) — including ones written with a stray trailing slash — compose correctly. Fixes homepage alternate/canonical links carrying a trailing slash on path-prefixed domains (/fr/ → /fr). The root path / is unaffected.

On path-prefixed domains the homepage now resolves correctly instead of falling through to the 404 page (the core/404 catch-all is no longer market-prefixed, so