Skip to content

chore: release 0.94.0 - #4589

Draft
gray-bot wants to merge 2 commits into
developfrom
release-please--branches--develop--components--daffodil
Draft

chore: release 0.94.0#4589
gray-bot wants to merge 2 commits into
developfrom
release-please--branches--develop--components--daffodil

Conversation

@gray-bot

@gray-bot gray-bot commented Jul 14, 2026

Copy link
Copy Markdown
Contributor

🤖 I have created a release beep boop

0.94.0 (2026-07-31)

⚠ BREAKING CHANGES

  • customer-order: @daffodil/customer-order/driver/magento/2-4-5 -> @daffodil/customer-order/driver/magento/2.4.5; @daffodil/customer-order/driver/magento/2-4-5/testing -> @daffodil/customer-order/driver/magento/2.4.5/testing; @daffodil/customer-order/driver/magento/2-4-6 -> @daffodil/customer-order/driver/magento/2.4.6; @daffodil/customer-order/driver/magento/2-4-6/testing -> @daffodil/customer-order/driver/magento/2.4.6/testing this aligns with our current conventions
  • order: @daffodil/order/driver/magento/2-4-0 -> @daffodil/order/driver/magento/2.4.0; @daffodil/order/driver/magento/2-4-1 -> @daffodil/order/driver/magento/2.4.1; @daffodil/order/driver/magento/2-4-1/testing -> @daffodil/order/driver/magento/2.4.1/testing
  • design: DaffCalloutComponent no longer resets the margins of paragraphs nested inside child components within [daffCalloutBody]. Previously the first and last <p> under the body received margin-top: 0 and margin-bottom: 0 at any depth. The reset now applies only to paragraphs that are direct children of [daffCalloutBody]. If you relied on the old behavior to flatten spacing in nested content, apply those margins in your own styles.
  • design: @daffodil/design/menu now exposes the DaffMenuActivatorDirective daffMenuActivator input as a signal rather than a plain property. Template bindings ([daffMenuActivator]="...") continue to work unchanged. Programmatic reads must invoke the signal: activator.daffMenuActivatoractivator.daffMenuActivator(). daffMenuActivator is now read-only and can no longer be assigned imperatively (activator.daffMenuActivator = menu is no longer supported).
  • design: DaffToastComponent.toast is now a required signal input. Read its value by calling it as a function (toast()) instead of accessing the property directly, and provide it via [toast] binding as it is now required.
  • design: @daffodil/design/text-snippet now exposes the DaffTextSnippetComponent inputs as signals rather than plain properties, and renames the toggle output to toggled. Template bindings ([condensed]="...", [html]="...") continue to work unchanged.
  • design: @daffodil/design/switch now exposes the DaffSwitchComponent inputs as signals rather than plain properties. Template bindings ([checked]="...", [labelPosition]="...", [id]="...", [disabled]="...") continue to work unchanged.
  • design: @daffodil/design/tabs now exposes its inputs as signals rather than plain properties. Template bindings ([initiallySelected]="...", [linkMode]="...", aria-label="...", [id]="...", etc.) continue to work unchanged.
  • design: @daffodil/design/tag now exposes the DaffTagComponent dismissible input as a signal rather than a plain property. Template bindings ([dismissible]="...") continue to work unchanged. Programmatic reads must invoke the signal: tag.dismissibletag.dismissible(). dismissible is now read-only and can no longer be assigned imperatively (tag.dismissible = true is no longer supported).
  • design: DaffDisableableDirective now exposes disabled as a signal (model) rather than a plain property. Template bindings ([disabled]="...") continue to work unchanged. Programmatic reads must invoke the signal: directive.disableddirective.disabled(). Imperative writes must use set: directive.disabled = truedirective.disabled.set(true).
  • design: @daffodil/design/progress-bar now exposes the DaffProgressBarComponent inputs percentage, aria-label, and indeterminate as signals rather than plain properties. Template bindings ([percentage]="...", [indeterminate]="...", etc.) continue to work unchanged. Programmatic reads must invoke the signal: progressBar.percentageprogressBar.percentage(), progressBar.ariaLabelprogressBar.ariaLabel(). These inputs are now read-only and can no longer be assigned imperatively (progressBar.percentage = 50 is no longer supported).
  • design: @daffodil/design/paginator now exposes the DaffPaginatorComponent inputs numberOfPages, currentPage, linkMode, url, and queryParam as signals rather than plain properties. Template bindings ([numberOfPages]="...", etc.) continue to work unchanged. Programmatic reads must invoke the signal: paginator.currentPagepaginator.currentPage(), paginator.numberOfPagespaginator.numberOfPages(), etc. These inputs are now read-only and can no longer be assigned imperatively.
  • design: @daffodil/design/notification now exposes the DaffNotificationComponent dismissible input as a signal rather than a plain property. Template bindings ([dismissible]="...") continue to work unchanged. Programmatic reads must invoke the signal: notification.dismissiblenotification.dismissible(). dismissible is now read-only and can no longer be assigned imperatively (notification.dismissible = true is no longer supported).
  • design: @daffodil/design/list now exposes the DaffListItemComponent active input as a signal rather than a plain property. Template bindings ([active]="...") continue to work unchanged. Programmatic reads must invoke the signal: listItem.activelistItem.active(). active is now read-only and can no longer be assigned imperatively (listItem.active = true is no longer supported).
  • design: @daffodil/design/image now exposes the DaffImageComponent inputs src, alt, width, and height as signals rather than plain properties, and renames the load output to loaded. Input template bindings ([src], [alt], etc.) continue to work unchanged. Programmatic reads must invoke the signal: image.srcimage.src(), image.widthimage.width(), etc. Inputs are now read-only and can no longer be assigned imperatively (image.src = '/image/test.jpg' is no longer supported).
  • design: @daffodil/design/form-field now exposes all DaffFormFieldComponent inputs (appearance and id) as signals rather than plain properties. Template bindings continue to work, but any programmatic access must go through the signal API:

Features

  • customer-order: rename magento driver packages to dot versions (#4624) (22288b6)
  • design: add configurable menu position and scrollable overflow (#4541) (cf4f135)
  • design: convert @daffodil/design/media-gallery to use signals (#4599) (0ef5ba2)
  • design: convert @daffodil/design/accordion to use signals (#4586) (9923025)
  • design: convert @daffodil/design/card to use signals (#4587) (b0b3f7c)
  • design: convert @daffodil/design/form-field to use signals (#4591) (f993bf9)
  • design: convert @daffodil/design/form to use signals (#4588) (ac4cb20)
  • design: convert @daffodil/design/image to use signals (#4597) (8ae04ce)
  • design: convert @daffodil/design/list to use signals (#4598) (56e3240)
  • design: convert @daffodil/design/menu to use signals (#4611) (49d0680)
  • design: convert @daffodil/design/notification to use signals (#4601) (2605219)
  • design: convert @daffodil/design/paginator to use signals (#4602) (c789c0b)
  • design: convert @daffodil/design/progress-bar to use signals (#4603) (c09aeb1)
  • design: convert @daffodil/design/spinner to use signals (#4604) (7ccfba9)
  • design: convert @daffodil/design/switch to use signals (#4608) (889ea85)
  • design: convert @daffodil/design/tabs to use signals (#4607) (dfcb254)
  • design: convert @daffodil/design/tag to use signals (#4606) (f449db4)
  • design: convert @daffodil/design/text-snippet to use signals (#4609) (0680453)
  • design: convert @daffodil/design/toast to use signals (#4610) (955d46d)
  • design: convert DaffDisableableDirective to use signals (#4605) (abdddbd)
  • Eslint for Magento driver exports in package.json (#4447) (b5b14b7)
  • order: rename version packages to dot separator (#4623) (fa1a17c)

Bug Fixes

  • design-examples: bind hero text alignment to selected option value (#4600) (fa428b0)
  • design: break dependency cycle in DaffRovingTabIndexDirective (#4594) (840e653)
  • design: isolate menu open state to activator (#4550) (5560c90)
  • design: let the card body fill the card (#4615) (49eceaa)
  • design: resolve card image border radius specificity (#4613) (98bdd4f)
  • design: scope callout body paragraph margins to direct children (#4617) (fedce39)
  • navigation: ensure fragment fields on leaf nodes in magento (#4621) (732c082)

This PR was generated with Release Please. See documentation.

@gray-bot
gray-bot force-pushed the release-please--branches--develop--components--daffodil branch 2 times, most recently from 4e7ca93 to f8c9d3e Compare July 14, 2026 12:42
@gray-bot gray-bot changed the title chore: release 0.93.2 chore: release 0.94.0 Jul 14, 2026
@gray-bot
gray-bot force-pushed the release-please--branches--develop--components--daffodil branch 8 times, most recently from c212c65 to 6fb2028 Compare July 21, 2026 13:45
@gray-bot
gray-bot force-pushed the release-please--branches--develop--components--daffodil branch 14 times, most recently from 34f4e23 to d54f140 Compare July 27, 2026 20:51
@gray-bot
gray-bot force-pushed the release-please--branches--develop--components--daffodil branch 3 times, most recently from f4c0d60 to 2a95beb Compare July 30, 2026 22:43
@gray-bot
gray-bot force-pushed the release-please--branches--develop--components--daffodil branch from e71fc32 to f7316b4 Compare July 31, 2026 14:37
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant