chore: release 0.94.0 - #4589
Draft
gray-bot wants to merge 2 commits into
Draft
Conversation
gray-bot
force-pushed
the
release-please--branches--develop--components--daffodil
branch
2 times, most recently
from
July 14, 2026 12:42
4e7ca93 to
f8c9d3e
Compare
gray-bot
force-pushed
the
release-please--branches--develop--components--daffodil
branch
8 times, most recently
from
July 21, 2026 13:45
c212c65 to
6fb2028
Compare
gray-bot
force-pushed
the
release-please--branches--develop--components--daffodil
branch
14 times, most recently
from
July 27, 2026 20:51
34f4e23 to
d54f140
Compare
gray-bot
force-pushed
the
release-please--branches--develop--components--daffodil
branch
3 times, most recently
from
July 30, 2026 22:43
f4c0d60 to
2a95beb
Compare
gray-bot
force-pushed
the
release-please--branches--develop--components--daffodil
branch
from
July 31, 2026 14:37
e71fc32 to
f7316b4
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
🤖 I have created a release beep boop
0.94.0 (2026-07-31)
⚠ BREAKING CHANGES
@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/testingthis aligns with our current conventions@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/testingDaffCalloutComponentno longer resets the margins of paragraphs nested inside child components within[daffCalloutBody]. Previously the first and last<p>under the body receivedmargin-top: 0andmargin-bottom: 0at 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.@daffodil/design/menunow exposes theDaffMenuActivatorDirectivedaffMenuActivatorinput as a signal rather than a plain property. Template bindings ([daffMenuActivator]="...") continue to work unchanged. Programmatic reads must invoke the signal:activator.daffMenuActivator→activator.daffMenuActivator().daffMenuActivatoris now read-only and can no longer be assigned imperatively (activator.daffMenuActivator = menuis no longer supported).DaffToastComponent.toastis 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.@daffodil/design/text-snippetnow exposes theDaffTextSnippetComponentinputs as signals rather than plain properties, and renames thetoggleoutput totoggled. Template bindings ([condensed]="...",[html]="...") continue to work unchanged.@daffodil/design/switchnow exposes theDaffSwitchComponentinputs as signals rather than plain properties. Template bindings ([checked]="...",[labelPosition]="...",[id]="...",[disabled]="...") continue to work unchanged.@daffodil/design/tabsnow exposes its inputs as signals rather than plain properties. Template bindings ([initiallySelected]="...",[linkMode]="...",aria-label="...",[id]="...", etc.) continue to work unchanged.@daffodil/design/tagnow exposes theDaffTagComponentdismissibleinput as a signal rather than a plain property. Template bindings ([dismissible]="...") continue to work unchanged. Programmatic reads must invoke the signal:tag.dismissible→tag.dismissible().dismissibleis now read-only and can no longer be assigned imperatively (tag.dismissible = trueis no longer supported).DaffDisableableDirectivenow exposesdisabledas a signal (model) rather than a plain property. Template bindings ([disabled]="...") continue to work unchanged. Programmatic reads must invoke the signal:directive.disabled→directive.disabled(). Imperative writes must useset:directive.disabled = true→directive.disabled.set(true).@daffodil/design/progress-barnow exposes theDaffProgressBarComponentinputspercentage,aria-label, andindeterminateas signals rather than plain properties. Template bindings ([percentage]="...",[indeterminate]="...", etc.) continue to work unchanged. Programmatic reads must invoke the signal:progressBar.percentage→progressBar.percentage(),progressBar.ariaLabel→progressBar.ariaLabel(). These inputs are now read-only and can no longer be assigned imperatively (progressBar.percentage = 50is no longer supported).@daffodil/design/paginatornow exposes theDaffPaginatorComponentinputsnumberOfPages,currentPage,linkMode,url, andqueryParamas signals rather than plain properties. Template bindings ([numberOfPages]="...", etc.) continue to work unchanged. Programmatic reads must invoke the signal:paginator.currentPage→paginator.currentPage(),paginator.numberOfPages→paginator.numberOfPages(), etc. These inputs are now read-only and can no longer be assigned imperatively.@daffodil/design/notificationnow exposes theDaffNotificationComponentdismissibleinput as a signal rather than a plain property. Template bindings ([dismissible]="...") continue to work unchanged. Programmatic reads must invoke the signal:notification.dismissible→notification.dismissible().dismissibleis now read-only and can no longer be assigned imperatively (notification.dismissible = trueis no longer supported).@daffodil/design/listnow exposes theDaffListItemComponentactiveinput as a signal rather than a plain property. Template bindings ([active]="...") continue to work unchanged. Programmatic reads must invoke the signal:listItem.active→listItem.active().activeis now read-only and can no longer be assigned imperatively (listItem.active = trueis no longer supported).@daffodil/design/imagenow exposes theDaffImageComponentinputssrc,alt,width, andheightas signals rather than plain properties, and renames theloadoutput toloaded. Input template bindings ([src],[alt], etc.) continue to work unchanged. Programmatic reads must invoke the signal:image.src→image.src(),image.width→image.width(), etc. Inputs are now read-only and can no longer be assigned imperatively (image.src = '/image/test.jpg'is no longer supported).@daffodil/design/form-fieldnow exposes allDaffFormFieldComponentinputs (appearanceandid) as signals rather than plain properties. Template bindings continue to work, but any programmatic access must go through the signal API:Features
@daffodil/design/accordionto use signals (#4586) (9923025)@daffodil/design/cardto use signals (#4587) (b0b3f7c)@daffodil/design/form-fieldto use signals (#4591) (f993bf9)@daffodil/design/formto use signals (#4588) (ac4cb20)@daffodil/design/imageto use signals (#4597) (8ae04ce)@daffodil/design/listto use signals (#4598) (56e3240)@daffodil/design/menuto use signals (#4611) (49d0680)@daffodil/design/notificationto use signals (#4601) (2605219)@daffodil/design/paginatorto use signals (#4602) (c789c0b)@daffodil/design/progress-barto use signals (#4603) (c09aeb1)@daffodil/design/spinnerto use signals (#4604) (7ccfba9)@daffodil/design/switchto use signals (#4608) (889ea85)@daffodil/design/tabsto use signals (#4607) (dfcb254)@daffodil/design/tagto use signals (#4606) (f449db4)@daffodil/design/text-snippetto use signals (#4609) (0680453)@daffodil/design/toastto use signals (#4610) (955d46d)DaffDisableableDirectiveto use signals (#4605) (abdddbd)exportsin package.json (#4447) (b5b14b7)Bug Fixes
This PR was generated with Release Please. See documentation.