Skip to content

Conversation

@ThierryBerger
Copy link
Contributor

No description provided.

@ekalosak
Copy link

ekalosak commented Jul 3, 2024

Nice! If it were my change, I'd add a '### 0.12.0' or something to indicate when which changes were made.

That said, usually I see these things with more of like, "here's what bugs were fixed and what changes were made and what features were added", rather than the versions for dependencies. The latter can be recovered from the git history of the cargo.toml relatively easily, and then maintaining the update list becomes a redundant chore - worst kind of chore!

@ThierryBerger
Copy link
Contributor Author

You're probably right about the detailed upgrade list, it can probably be tuned down to just rapier.

I feel like "important" dependency updates deserve a line still.

About the version, yes, the plan is to adopt same logic as other dimforge/ repositories (rapier...) ; where changes are under "unreleased" while not published, then their version is filled in.

Co-authored-by: Sébastien Crozet <sebastien@crozet.re>
@ThierryBerger ThierryBerger merged commit 8ac39a3 into dimforge:master Jul 5, 2024
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