chore(release): version packages [skip-heavy-ci] (next)

[github-actions]

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 develop, this PR will be updated.

⚠️⚠️⚠️⚠️⚠️⚠️

develop is currently in pre mode so this branch has prereleases rather than normal releases. If you want to exit prereleases, run changeset pre exit on develop.

⚠️⚠️⚠️⚠️⚠️⚠️

Releases

@pie-element/mc-populated-blank@0.3.0-next.4

Minor Changes

• 392bfcf: stop rendering the audio transcript in delivery; the toolkit renders it PIE-855

@pie-element/shared-types@0.2.0-next.0

Minor Changes

• 1d74cc2: Carry sign-language cards on CatalogCard, the shape pie-players canonicalises (PIE-879)

  An accessibility catalog card is now a single CatalogCard: catalog (the QTI
  support= token, and the only discriminant), optional language, and exactly
  one of content — the string form, SSML for spoken — or payload, the
  structured form for what a string cannot express. Adds
  SignLanguageCardPayload (a MediaAssetRef with multiple sources and MIME
  types, an optional MediaFragmentRange, and an optional signLang), the
  CatalogCardPayload union, MediaAssetRef, MediaKind, MediaSource, and an
  isSignLanguageCard narrowing guard.

  A signing card's adaptation language belongs on the card's language. That is
  the only field pie-players resolves a card on — resolution runs before anything
  knows the card is a signing card, so it can only key on the generic field — and
  the player falls back to it when the payload omits signLang. So signLang is
  optional, and redundant on every card the Learnosity importer produces, which
  emits language alone. It stays declared for the one shape where the two differ:
  a card tagged with the item's content language, so resolution reaches it by the
  default-language rung while the payload says what the clip is signed in.
  isSignLanguageCard deliberately says nothing about it — it briefly required a
  non-empty signLang, which would have rejected every imported card.

  The previous flat content: string could only hold a bare URL, which cannot
  express a signing video and left malformed payloads indistinguishable from
  text.

  This replaces the SignLanguageCatalogCard | TextCatalogCard union that was
  staged here earlier, and with it the signLanguage payload key. pie-players
  owns the card shape and canonicalises one generic payload slot interpreted by
  catalog: QTI's qti-card has a single content slot that @support already
  discriminates, and a field per accommodation makes every new structured
  alternate — braille next — a breaking widening of the card type in every
  consumer that reads cards. The divergence was not academic: pie-players
  tolerated signLanguage as an input alias on its resolution path but not its
  enumeration path, so a card authored against the old shape rendered its signing
  video and was simultaneously reported as carrying no alternate.

  SignLanguageCatalogCard survives as a narrowing of CatalogCard for the write
  side, since an open-ended catalog vocabulary means the type cannot state "a
  signing card must carry a payload".

  Breaking for consumers that referenced AccessibilityCatalogCard,
  TextCatalogCard, MediaFragment, or card.signLanguage: they are
  CatalogCard, CatalogCard, MediaFragmentRange, and card.payload. No
  element in this repo reads any of them, so nothing here changes behaviour. Data
  model only — resolution, rendering, and PNP gating live in pie-players.

@pie-element/element-theme@0.1.1-next.2

Patch Changes

• @pie-element/shared-theming@0.1.1-next.2

@pie-element/element-theme-daisyui@0.1.1-next.2

Patch Changes

• Updated dependencies [1d74cc2]
  • @pie-element/shared-types@0.2.0-next.0
  • @pie-element/shared-theming@0.1.1-next.2
  • @pie-element/element-theme@0.1.1-next.2

@pie-element/categorize@13.1.2-next.6

Patch Changes

• @pie-element/shared-controller-utils@0.1.1-next.2

@pie-element/charting@12.1.2-next.6

Patch Changes

• @pie-element/shared-controller-utils@0.1.1-next.2

@pie-element/drag-in-the-blank@10.1.2-next.6

Patch Changes

• @pie-element/shared-controller-utils@0.1.1-next.2

@pie-element/ebsr@14.2.2-next.6

Patch Changes

• @pie-element/shared-controller-utils@0.1.1-next.2
• @pie-element/multiple-choice@13.3.5-next.1

@pie-element/explicit-constructed-response@11.1.2-next.6

Patch Changes

• @pie-element/shared-controller-utils@0.1.1-next.2

@pie-element/graphing@10.1.2-next.6

Patch Changes

• @pie-element/shared-controller-utils@0.1.1-next.2

@pie-element/hotspot@11.1.2-next.6

Patch Changes

• @pie-element/shared-controller-utils@0.1.1-next.2

@pie-element/image-cloze-association@10.1.2-next.6

Patch Changes

• @pie-element/shared-controller-utils@0.1.1-next.2

@pie-element/inline-dropdown@10.1.2-next.6

Patch Changes

• @pie-element/shared-controller-utils@0.1.1-next.2

@pie-element/match@12.1.2-next.6

Patch Changes

• @pie-element/shared-controller-utils@0.1.1-next.2

@pie-element/match-list@7.1.2-next.6

Patch Changes

• @pie-element/shared-controller-utils@0.1.1-next.2

@pie-element/math-templated@7.1.1-next.16

Patch Changes

• @pie-element/shared-controller-utils@0.1.1-next.2

@pie-element/multiple-choice@13.3.5-next.1

Patch Changes

• @pie-element/shared-controller-utils@0.1.1-next.2

@pie-element/number-line@13.1.2-next.6

Patch Changes

• @pie-element/shared-controller-utils@0.1.1-next.2

@pie-element/passage@7.1.2-next.6

Patch Changes

• 2b06575: The paired-passage tabs follow the active theme and color scheme. Tab fill, tab ink and the
  selection indicator resolve through --pie-background / --pie-text instead of MUI's
  palette, so they no longer stay white with black ink over a dark passage body, and the tab
  outline and the strip's bottom rule move to --pie-border-gray, which holds the 3:1
  non-text minimum on every scheme where the previous #D9DADA measured about 1.2:1. A host
  that sets --pie-passage-header-background keeps its own strip colour unchanged; only the
  default, previously a white literal, now follows the theme.

@pie-element/placement-ordering@14.1.2-next.6

Patch Changes

• @pie-element/shared-controller-utils@0.1.1-next.2

@pie-element/select-text@13.1.2-next.6

Patch Changes

• @pie-element/shared-controller-utils@0.1.1-next.2

@pie-element/shared-controller-utils@0.1.1-next.2

Patch Changes

• Updated dependencies [1d74cc2]
  • @pie-element/shared-types@0.2.0-next.0

@pie-element/shared-test-utils@0.1.1-next.1

Patch Changes

• Updated dependencies [1d74cc2]
  • @pie-element/shared-types@0.2.0-next.0
  • @pie-element/shared-utils@0.1.1-next.2

@pie-element/shared-theming@0.1.1-next.2

Patch Changes

• Updated dependencies [1d74cc2]
  • @pie-element/shared-types@0.2.0-next.0

@pie-element/shared-theming-mui@0.1.1-next.2

Patch Changes

• Updated dependencies [1d74cc2]
  • @pie-element/shared-types@0.2.0-next.0
  • @pie-element/shared-theming@0.1.1-next.2

@pie-element/shared-utils@0.1.1-next.2

Patch Changes

• Updated dependencies [1d74cc2]
  • @pie-element/shared-types@0.2.0-next.0

@pie-element/element-a11y-demo@0.1.2-next.3

Patch Changes

• @pie-element/element-theme-daisyui@0.1.1-next.2

@pie-element/element-demo@0.1.2-next.3

Patch Changes

• @pie-element/element-theme-daisyui@0.1.1-next.2

@pie-element/learnosity-parity-demo@0.1.2-next.3

Patch Changes

• @pie-element/element-theme-daisyui@0.1.1-next.2