Skip to content
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

Changelog with breaking changes #2976

Open
eps1lon opened this issue Jun 24, 2024 · 3 comments
Open

Changelog with breaking changes #2976

eps1lon opened this issue Jun 24, 2024 · 3 comments

Comments

@eps1lon
Copy link

eps1lon commented Jun 24, 2024

Documentation

There is currently no comprehensive changelog for breaking changes e.g. what are the breaking changes in @radix-ui/[email protected]? This makes it hard to upgrade Radix UI packages.

It's also not apparent for users how package names map to the headings in https://www.radix-ui.com/primitives/docs/overview/releases.

Ideally we'd also have GitHub releases and tagged commits so that it is apparent when a change was released. You could automate all of this with Changesets

Related to #2508

Relevant Radix Component(s)

All

Examples from other doc sites

https://github.com/mui/material-ui/releases

@vladmoroz
Copy link
Collaborator

vladmoroz commented Jun 25, 2024

There is currently no comprehensive changelog for breaking changes e.g. what are the breaking changes in @radix-ui/[email protected]? This makes it hard to upgrade Radix UI packages.

Internal utilities like this one aren't documented generally—we don't advertise/recommend using them. This one specifically was bumped to major because I removed a type export for a really old React.ComponentPropsWithoutRef workaround.

It's also not apparent for users how package names map to the headings in https://www.radix-ui.com/primitives/docs/overview/releases.

As in, you'd rather see @radix-ui/react-popover instead of Popover? This makes sense

Ideally we'd also have GitHub releases and tagged commits so that it is apparent when a change was released. You could automate all of this with Changesets

Strongly agree. I don't know when we'd find time to set this up, but it's on our radar.

@eps1lon
Copy link
Author

eps1lon commented Jun 25, 2024

Internal utilities like this one aren't documented generally—we don't advertise/recommend using them. This one specifically was bumped to major because I removed a type export for a really old React.ComponentPropsWithoutRef workaround.

Good to know, thank you. Is it safe to assume that every package that's not used in the docs is internal?

@vladmoroz
Copy link
Collaborator

Good to know, thank you. Is it safe to assume that every package that's not used in the docs is internal?

Yep exactly

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants