-
Notifications
You must be signed in to change notification settings - Fork 10
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
release: version packages #4173
Open
github-actions
wants to merge
1
commit into
main
Choose a base branch
from
changeset-release/main
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Conversation
This file contains 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
The latest updates on your projects. Learn more about Vercel for Git ↗︎
1 Skipped Deployment
|
github-actions
bot
force-pushed
the
changeset-release/main
branch
from
September 23, 2024 09:19
169dfd0
to
e37c9d9
Compare
github-actions
bot
force-pushed
the
changeset-release/main
branch
from
September 23, 2024 14:12
e37c9d9
to
8577582
Compare
github-actions
bot
force-pushed
the
changeset-release/main
branch
from
September 25, 2024 17:14
8577582
to
88eb37e
Compare
github-actions
bot
force-pushed
the
changeset-release/main
branch
from
September 25, 2024 18:10
88eb37e
to
d435f71
Compare
github-actions
bot
force-pushed
the
changeset-release/main
branch
from
September 27, 2024 09:58
d435f71
to
4296d85
Compare
github-actions
bot
force-pushed
the
changeset-release/main
branch
from
September 30, 2024 01:00
4296d85
to
a4da8d0
Compare
github-actions
bot
force-pushed
the
changeset-release/main
branch
from
September 30, 2024 02:14
a4da8d0
to
50e0e99
Compare
github-actions
bot
force-pushed
the
changeset-release/main
branch
from
September 30, 2024 03:20
50e0e99
to
190ce09
Compare
github-actions
bot
force-pushed
the
changeset-release/main
branch
2 times, most recently
from
October 2, 2024 07:17
1a57487
to
470dbab
Compare
github-actions
bot
force-pushed
the
changeset-release/main
branch
from
October 2, 2024 08:12
470dbab
to
e7fe556
Compare
github-actions
bot
force-pushed
the
changeset-release/main
branch
from
October 20, 2024 23:03
abd0701
to
9ba0275
Compare
github-actions
bot
force-pushed
the
changeset-release/main
branch
2 times, most recently
from
October 21, 2024 00:48
1cc650e
to
f3bbfe1
Compare
github-actions
bot
force-pushed
the
changeset-release/main
branch
2 times, most recently
from
October 21, 2024 02:23
0ccd3f0
to
ab4c982
Compare
github-actions
bot
force-pushed
the
changeset-release/main
branch
2 times, most recently
from
October 21, 2024 03:52
87c3601
to
2e0330b
Compare
github-actions
bot
force-pushed
the
changeset-release/main
branch
from
October 21, 2024 06:19
2e0330b
to
6a08443
Compare
github-actions
bot
force-pushed
the
changeset-release/main
branch
from
October 21, 2024 08:42
6a08443
to
a7184bc
Compare
github-actions
bot
force-pushed
the
changeset-release/main
branch
from
October 21, 2024 12:56
a7184bc
to
2c2d87f
Compare
github-actions
bot
force-pushed
the
changeset-release/main
branch
from
October 22, 2024 11:40
2c2d87f
to
9f9898c
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
None yet
0 participants
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
@marigold/[email protected]
Major Changes
2d9917f: Breaking changes
Dialog.Headline
has been renamed toDialog.Title
. Please update your code accordingly.<Dialog.Content>
,<Dialog.Actions>
, and<Dialog.Footer>
have been introduced for better organization and flexibility.<Dialog>
component will need to be updated to use these new subcomponents.Minor Changes
2babc0b: feat(components): Mark layout components as regions for accessibility.
Added the ability to mark layout components as regions (ARIA role). This improves accessibility by allowing assistive technologies to identify significant sections of the page, making navigation easier for users with disabilities.
956982a: feat(components): Make
<Text>
and<Headline>
accessible by allowing ARIA labelling props<Text>
and<Headline>
will no longer cause type errors when ARIA labelling is used (aria-label
,id
, ...).df04623: Adding size to dialog component
Patch Changes
caefbe4: refa(listbox): Allow sections in
<Combobox>
and<Autocomplete>
, adjust Section API in<Select>
,<Combobox>
and<Autocomplete>
.Added the possibility to use sections with
<Combobox>
and<Autocomplete>
Refactored the
<Section>
(from<Listbox>
) to fit our API, no need for the extra<Header>
anymore. Instead you can do<Select.Section header="My header">
, same for the other componentsRenamed
<Item>
to<Option>
in<Combobox>
and<Autocomplete>
to align with<Select>
Updated the docs for
<Select>
,<Combobox>
and<Autocomplete>
Updated Storybook for
<Select>
,<Combobox>
and<Autocomplete>
with section storiesRenamed the part of the
<ListBox>
accordingly (fromsectionTitle
toheader
)BREAKING CHANGE: We changed the API of the
<Section>
component that is used in<Select>
,<Combobox>
and<Autocomplete>
. It is no longer necessary to add aHeader
within the<Section>
.Use the newly added
header
prop instead. Additionally, to unify the APIs all choices of<Select>
,<Combobox>
and<Autocomplete>
are now called<Option>
instead of<Item>
.7ea3838: feat(Menu): pass
aria-label
to menu button instead of menuf18c8aa: [DST-494]: add loading states pattern
[DST-494]: added prop
mode
to the<XLoader />
to support inline and full-section loadingd5386e4: fix(components): Display
<Checkbox>
focus ring and adjust focus ring of<Table>
Focus ring was not showing for the
<Checkbox>
. It does now!5c029ec: feat(components): Expose
Selection
type for easy usage withTable
and other componentsWhen working with a
<Table>
you can now useinstead of creating the type.
b8cd92a: feat:
CheckboxGroup
can now be used as a compound componentCheckboxGroup
to be a compound component and align it with other components:<CheckboxGroup>
-><Checkbox.Group>
45fb3c4: chore(deps): update react-aria to 1.4
f6a132c: docs([DST-582]): revise
<SectionMessage>
page according to new component page structurefeat(components): add close button on
<SectionMessage>
Revised the
<SectionMessage>
documentation page to our new layout of component pages. And added a close button to allow the user to dismiss the<SectionMessage>
this is now aligned with our feedback message pattern.Updated dependencies [caefbe4]
Updated dependencies [2babc0b]
Updated dependencies [45fb3c4]
Updated dependencies [956982a]
@marigold/[email protected]
Major Changes
2d9917f: Breaking changes
Dialog.Headline
has been renamed toDialog.Title
. Please update your code accordingly.<Dialog.Content>
,<Dialog.Actions>
, and<Dialog.Footer>
have been introduced for better organization and flexibility.<Dialog>
component will need to be updated to use these new subcomponents.Minor Changes
Patch Changes
caefbe4: refa(listbox): Allow sections in
<Combobox>
and<Autocomplete>
, adjust Section API in<Select>
,<Combobox>
and<Autocomplete>
.Added the possibility to use sections with
<Combobox>
and<Autocomplete>
Refactored the
<Section>
(from<Listbox>
) to fit our API, no need for the extra<Header>
anymore. Instead you can do<Select.Section header="My header">
, same for the other componentsRenamed
<Item>
to<Option>
in<Combobox>
and<Autocomplete>
to align with<Select>
Updated the docs for
<Select>
,<Combobox>
and<Autocomplete>
Updated Storybook for
<Select>
,<Combobox>
and<Autocomplete>
with section storiesRenamed the part of the
<ListBox>
accordingly (fromsectionTitle
toheader
)BREAKING CHANGE: We changed the API of the
<Section>
component that is used in<Select>
,<Combobox>
and<Autocomplete>
. It is no longer necessary to add aHeader
within the<Section>
.Use the newly added
header
prop instead. Additionally, to unify the APIs all choices of<Select>
,<Combobox>
and<Autocomplete>
are now called<Option>
instead of<Item>
.f6a132c: docs([DST-582]): revise
<SectionMessage>
page according to new component page structurefeat(components): add close button on
<SectionMessage>
Revised the
<SectionMessage>
documentation page to our new layout of component pages. And added a close button to allow the user to dismiss the<SectionMessage>
this is now aligned with our feedback message pattern.Updated dependencies [caefbe4]
Updated dependencies [2d9917f]
Updated dependencies [7ea3838]
Updated dependencies [2babc0b]
Updated dependencies [f18c8aa]
Updated dependencies [d5386e4]
Updated dependencies [5c029ec]
Updated dependencies [b8cd92a]
Updated dependencies [45fb3c4]
Updated dependencies [f6a132c]
Updated dependencies [956982a]
Updated dependencies [df04623]
@marigold/[email protected]
Major Changes
2d9917f: Breaking changes
Dialog.Headline
has been renamed toDialog.Title
. Please update your code accordingly.<Dialog.Content>
,<Dialog.Actions>
, and<Dialog.Footer>
have been introduced for better organization and flexibility.<Dialog>
component will need to be updated to use these new subcomponents.Patch Changes
d5386e4: fix(components): Display
<Checkbox>
focus ring and adjust focus ring of<Table>
Focus ring was not showing for the
<Checkbox>
. It does now!f6a132c: docs([DST-582]): revise
<SectionMessage>
page according to new component page structurefeat(components): add close button on
<SectionMessage>
Revised the
<SectionMessage>
documentation page to our new layout of component pages. And added a close button to allow the user to dismiss the<SectionMessage>
this is now aligned with our feedback message pattern.Updated dependencies [caefbe4]
Updated dependencies [2d9917f]
Updated dependencies [7ea3838]
Updated dependencies [2babc0b]
Updated dependencies [f18c8aa]
Updated dependencies [d5386e4]
Updated dependencies [5c029ec]
Updated dependencies [b8cd92a]
Updated dependencies [45fb3c4]
Updated dependencies [f6a132c]
Updated dependencies [956982a]
Updated dependencies [df04623]
@marigold/[email protected]
Minor Changes
2babc0b: feat(components): Mark layout components as regions for accessibility.
Added the ability to mark layout components as regions (ARIA role). This improves accessibility by allowing assistive technologies to identify significant sections of the page, making navigation easier for users with disabilities.
956982a: feat(components): Make
<Text>
and<Headline>
accessible by allowing ARIA labelling props<Text>
and<Headline>
will no longer cause type errors when ARIA labelling is used (aria-label
,id
, ...).@marigold/[email protected]
Patch Changes
@marigold/[email protected]
Patch Changes
@marigold/[email protected]
Patch Changes
caefbe4: refa(listbox): Allow sections in
<Combobox>
and<Autocomplete>
, adjust Section API in<Select>
,<Combobox>
and<Autocomplete>
.Added the possibility to use sections with
<Combobox>
and<Autocomplete>
Refactored the
<Section>
(from<Listbox>
) to fit our API, no need for the extra<Header>
anymore. Instead you can do<Select.Section header="My header">
, same for the other componentsRenamed
<Item>
to<Option>
in<Combobox>
and<Autocomplete>
to align with<Select>
Updated the docs for
<Select>
,<Combobox>
and<Autocomplete>
Updated Storybook for
<Select>
,<Combobox>
and<Autocomplete>
with section storiesRenamed the part of the
<ListBox>
accordingly (fromsectionTitle
toheader
)BREAKING CHANGE: We changed the API of the
<Section>
component that is used in<Select>
,<Combobox>
and<Autocomplete>
. It is no longer necessary to add aHeader
within the<Section>
.Use the newly added
header
prop instead. Additionally, to unify the APIs all choices of<Select>
,<Combobox>
and<Autocomplete>
are now called<Option>
instead of<Item>
.45fb3c4: chore(deps): update react-aria to 1.4
Updated dependencies [2babc0b]
Updated dependencies [956982a]
@marigold/[email protected]
Patch Changes
@marigold/[email protected]
Patch Changes
165e184: style(docs): Improve whitespace of
p
Removed the top margin because this lead to some weird extra whitespace.
9ff555b: docs: add landing page to the site
Updated dependencies [caefbe4]
Updated dependencies [2d9917f]
Updated dependencies [7ea3838]
Updated dependencies [2babc0b]
Updated dependencies [f18c8aa]
Updated dependencies [d5386e4]
Updated dependencies [5c029ec]
Updated dependencies [b8cd92a]
Updated dependencies [45fb3c4]
Updated dependencies [f6a132c]
Updated dependencies [956982a]
Updated dependencies [df04623]
@marigold/[email protected]
Patch Changes
caefbe4: refa(listbox): Allow sections in
<Combobox>
and<Autocomplete>
, adjust Section API in<Select>
,<Combobox>
and<Autocomplete>
.Added the possibility to use sections with
<Combobox>
and<Autocomplete>
Refactored the
<Section>
(from<Listbox>
) to fit our API, no need for the extra<Header>
anymore. Instead you can do<Select.Section header="My header">
, same for the other componentsRenamed
<Item>
to<Option>
in<Combobox>
and<Autocomplete>
to align with<Select>
Updated the docs for
<Select>
,<Combobox>
and<Autocomplete>
Updated Storybook for
<Select>
,<Combobox>
and<Autocomplete>
with section storiesRenamed the part of the
<ListBox>
accordingly (fromsectionTitle
toheader
)BREAKING CHANGE: We changed the API of the
<Section>
component that is used in<Select>
,<Combobox>
and<Autocomplete>
. It is no longer necessary to add aHeader
within the<Section>
.Use the newly added
header
prop instead. Additionally, to unify the APIs all choices of<Select>
,<Combobox>
and<Autocomplete>
are now called<Option>
instead of<Item>
.4818227: docs([DST-570]): Added "Release" pages to our documentation
We now create for each changelog a page on our documentation, it is also possible to create release blog posts.
With these pages we improve communication, enhance user experience, and ensure all users have easy access to the latest updates in one central location.
f18c8aa: [DST-494]: add loading states pattern
[DST-494]: added prop
mode
to the<XLoader />
to support inline and full-section loadinge83566d: docs: remove examples from checkbox page and add guidline section
9ff555b: docs: add landing page to the site
380704d: docs[DST-519]: Clean up Marigold Docs/ Improve Navigation
b8cd92a: feat:
CheckboxGroup
can now be used as a compound componentCheckboxGroup
to be a compound component and align it with other components:<CheckboxGroup>
-><Checkbox.Group>
a582035: docs: Update the
MarigoldProvider
pageUpdated the MarigoldProvider page according to our new page layout and information.
fab9442: docs(Combobox): add info that section headers are not included wehen filtering
45fb3c4: chore(deps): update react-aria to 1.4
f6a132c: docs([DST-582]): revise
<SectionMessage>
page according to new component page structurefeat(components): add close button on
<SectionMessage>
Revised the
<SectionMessage>
documentation page to our new layout of component pages. And added a close button to allow the user to dismiss the<SectionMessage>
this is now aligned with our feedback message pattern.f85bb04: docs: Apply root styles to overlay portal so they are displayed correctly.
Overlay components (e.g.
<Dialog>
did not display correctly in the docs.Updated dependencies [caefbe4]
Updated dependencies [165e184]
Updated dependencies [2d9917f]
Updated dependencies [7ea3838]
Updated dependencies [2babc0b]
Updated dependencies [f18c8aa]
Updated dependencies [d5386e4]
Updated dependencies [5c029ec]
Updated dependencies [9ff555b]
Updated dependencies [b8cd92a]
Updated dependencies [45fb3c4]
Updated dependencies [f6a132c]
Updated dependencies [956982a]
Updated dependencies [df04623]