-
Notifications
You must be signed in to change notification settings - Fork 430
feat!: Release 0.8.0
#753
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
feat!: Release 0.8.0
#753
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
05afdda to
31cc29c
Compare
notxvilka
approved these changes
Apr 2, 2025
ABorgna
approved these changes
Apr 2, 2025
github-merge-queue bot
pushed a commit
that referenced
this pull request
Apr 5, 2025
…ion (#735) Setups [`release-plz`](https://release-plz.dev/) to run on each push to `master`. This has two different flows: ### Release PR (disabled until after the `0.8.0` release) When a PR is merged, it analyses all the commits since the last release and creates a draft PR with the automatically generated changelog. Commits are grouped into categories using conventional commit tags (see #734). I ported the existing `RELEASES.rst` to markdown, so updates can be done from there. It also runs [`cargo-semver-checks`](https://crates.io/crates/cargo-semver-checks) to decide if the next release should be a semver-breaking bump, and updates the package version. Any merged PR marked as breaking (#734) will also cause a breaking version bump. ### Package publication When a change is merged that bumps the package version `release-plz` will create a new github release with the appropriate changelog and a list of contributors, and push the new version to crates.io. (I haven't yet added the crates token, will do once we verify this action is correctly configured, before the new release gets merged). drive-by: cherry-pick new clippy lint fixes from #753 --------- Co-authored-by: starovoid <prototyperailgun@gmail.com>
Member
|
Merged the changelog updates from #735, and moved the 0.8.0 release notes to the new markdown file |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
A sufficient number of proposed changes have accumulated to combine them and publish a new major release numbered
0.8.0.BREAKING CHANGE:
This will require the user to provide extra type parameter in some APIs (Read more in #747).
List of changes
no_stdSupport #747The main innovation of the current release, the long-awaited feature that has become very relevant due to the transition of dependent projects to support
no_std.VisitMap::unvisitas proposed in #610 #611Measures fromf32&f64#737MatrixGraphmethods with recoverable errors #720GraphandStableGraph#718Note
There are still a large number of PRs that we want to adopt in the near future, so we should expect at least a release of
0.8.1soon after the completion of0.8.0.Thank you all for participating!