Skip to content

1.1.0, and docs.rs improvements#8

Merged
babolivier merged 1 commit into
mainfrom
babolivier/1.1
Apr 23, 2026
Merged

1.1.0, and docs.rs improvements#8
babolivier merged 1 commit into
mainfrom
babolivier/1.1

Conversation

@babolivier
Copy link
Copy Markdown
Member

No description provided.

@babolivier babolivier requested a review from a team as a code owner April 23, 2026 11:07
@babolivier babolivier merged commit 5ca498b into main Apr 23, 2026
2 checks passed
@jtracey
Copy link
Copy Markdown
Contributor

jtracey commented Apr 24, 2026

Saw the bustage, sorry for not noticing this should have been a major version bump. Not sure what we should do now, since it's already shipped, but someone who marks the dependency as 1 could have two different expected APIs.

@babolivier
Copy link
Copy Markdown
Member Author

babolivier commented Apr 24, 2026

It's also my mistake for not realising the change broke API stability.

someone who marks the dependency as 1 could have two different expected APIs

Unless they've pinned 1.0.0 (with =1.0.0), I'd expect Cargo should always pick 1.1.0, so there's some stability there. The crate's only been out for a little amount of time so hopefully nobody besides us has actually started to consume it, so I think we should just make sure we keep >=1.1.0 stable (we could yank the release from crates.io, but I'm not convinced it's worth the pain considering the circumstances).

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.

2 participants