Skip to content

Conversation

@starovoid
Copy link
Collaborator

@starovoid starovoid commented Mar 21, 2025

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

Note

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.1 soon after the completion of 0.8.0.

Thank you all for participating!

@starovoid starovoid changed the title Release 0.8.0 feat!: Release 0.8.0 Mar 21, 2025
@starovoid starovoid self-assigned this Mar 21, 2025
@starovoid starovoid added this to the 0.8 milestone Mar 21, 2025
@starovoid starovoid marked this pull request as ready for review March 26, 2025 18:15
@starovoid starovoid requested a review from ABorgna March 26, 2025 18:16
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>
@ABorgna
Copy link
Member

ABorgna commented Apr 5, 2025

Merged the changelog updates from #735, and moved the 0.8.0 release notes to the new markdown file

@ABorgna ABorgna added this pull request to the merge queue Apr 5, 2025
Merged via the queue into master with commit 5f5791c Apr 5, 2025
10 checks passed
@ABorgna ABorgna deleted the release-0.8.0 branch April 5, 2025 13:57
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.

4 participants