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

chore: create a changelog, with last pull request information #54

Merged
merged 2 commits into from
Jul 5, 2024

Conversation

Vrixyz
Copy link
Contributor

@Vrixyz Vrixyz commented Jun 24, 2024

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!

@Vrixyz
Copy link
Contributor Author

Vrixyz commented Jul 3, 2024

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.

CHANGELOG.md Outdated Show resolved Hide resolved
Co-authored-by: Sébastien Crozet <[email protected]>
@Vrixyz Vrixyz merged commit 8ac39a3 into dimforge:master Jul 5, 2024
23 checks passed
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