Skip to content

Publish web_atoms 0.1.1. #609

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

Merged
merged 1 commit into from
Apr 27, 2025
Merged

Publish web_atoms 0.1.1. #609

merged 1 commit into from
Apr 27, 2025

Conversation

jdm
Copy link
Member

@jdm jdm commented Apr 26, 2025

This includes the changes from #608.

Signed-off-by: Josh Matthews <[email protected]>
@simonwuelker
Copy link
Contributor

It's a bit silly to release a new version every time someone adds new atoms. Can't we depend on the git version instead?

@nicoburns
Copy link
Contributor

It's a bit silly to release a new version every time someone adds new atoms. Can't we depend on the git version instead?

We could, but that would require bumping markup5ever, html5ever, xml5ever, and stylo every time because there would be no notion of semver compatibility.

IMO the problem is that we're just not being quick enough on the draw with releases. Releasing is a 5 minute task (much quicker than running CI for a git version!) for those who have the permission. It should happen as a matter of course when a PR adding atoms is merged. We just have a lot of roadblocks around crate releases in the Servo project (although not all parts, this does happen for Servo crates like smallvec - the main difference seeming to be that crate has a maintainer who is 1. engaged in the process of making releases 2. empowered to make version bump commits without review).

@jdm jdm added this pull request to the merge queue Apr 27, 2025
Merged via the queue into main with commit 559f96a Apr 27, 2025
6 checks passed
@jdm
Copy link
Member Author

jdm commented Apr 27, 2025

Published.

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

Successfully merging this pull request may close these issues.

3 participants