chore: release packages#2771
Open
github-actions[bot] wants to merge 1 commit into
Open
Conversation
✅ Deploy Preview for fondue-components ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
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.
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 main, this PR will be updated.
Releases
@frontify/fondue-components@30.8.0
Minor Changes
#2769
a75f700Thanks @mnoleto! - feat(Card.Action): forward arbitrarydata-*attributesCard.Actionnow spreads unknown props (notablydata-*attributes, e.g. ananalytics or onboarding-tour selector) onto the rendered element, so consumers
no longer need an extra wrapper to carry them.
#2769
a75f700Thanks @mnoleto! - feat(Card.BannerImage): add apaddingpropCard.BannerImagenow acceptspadding="none" | "small" | "medium" | "large"(none by default; small 12px, medium 24px, large 32px). Padding is applied
inside the banner and pairs best with
fit="contain", giving previews such aslogos or icons breathing room without dropping out of the component. Backward
compatible — existing images default to
none.#2769
a75f700Thanks @mnoleto! - feat(Card.Banner): add atonepropCard.Bannernow acceptstone="dim" | "inverted".invertedrenders the darkdrop-target state (near-black background, white icon), while
dimpins thebackground and opts out of the implicit hover/active background shift that
otherwise applies when a
Card.BannerIconis nested. Leavingtoneunsetpreserves the previous behavior, so existing consumers are unaffected.
#2769
a75f700Thanks @mnoleto! - feat(Card.Root): forwardclassNameCard.Rootnow forwards aclassNameonto its root element, merged after theinternal styles. This enables layout hooks such as Tailwind's
group(e.g. todrive
group-hover:styles on descendants) without an extra wrapper element.Patch Changes