Skip to content

Prepare v0.4.0 release#798

Merged
dhardy merged 1 commit intomasterfrom
push-qnzqylypkrkn
Feb 2, 2026
Merged

Prepare v0.4.0 release#798
dhardy merged 1 commit intomasterfrom
push-qnzqylypkrkn

Conversation

@dhardy
Copy link
Member

@dhardy dhardy commented Feb 1, 2026

I believe this is ready for release (see #722)?

@newpavlov
Copy link
Member

#794 should be merged first.

@newpavlov
Copy link
Member

newpavlov commented Feb 2, 2026

Note that in the custom backend we still use __getrandom_v03_custom. I think it's worth to keep it as-is since the symbol is unchanged and it will be more convenient for cases when both v0.3 and v0.4 are present in a project's dependency tree. In v0.5 (or v1.0) we are likely to remove the custom backend completely in favor of #796.

@dhardy dhardy force-pushed the push-qnzqylypkrkn branch from fc4a0e6 to 9cefeda Compare February 2, 2026 08:03
@dhardy dhardy merged commit 35fd5af into master Feb 2, 2026
77 checks passed
@dhardy dhardy deleted the push-qnzqylypkrkn branch February 2, 2026 08:16
@dhardy
Copy link
Member Author

dhardy commented Feb 2, 2026

Published. @newpavlov will you make the GH release?

@newpavlov
Copy link
Member

newpavlov commented Feb 2, 2026

Since we switched to Trusted Publishing you just need to push new version tag and with the current configuration the workflow needs your approval, so it's probably better for you to push the tag.

UPD: Ah, I see. The environment settings have changed and the list of reviewers now includes me and Joe. Either way, you already pushed the tag.

@newpavlov
Copy link
Member

newpavlov commented Feb 2, 2026

@dhardy
Maybe we should change the environment setting to prevent self-reviews since we now have several eligible reviewers? Though, since the setting can be changed, it's still basically a honor system. Additionally, it would complicate setting correct release date in the changelog if reviewers are not responsive enough...

@dhardy
Copy link
Member Author

dhardy commented Feb 2, 2026

I was referring to GitHub releases which aren't automated... or used at all in this case. Never mind.

You can change the requirements to prevent self-review if you like, but yes it is essentially an honour system. The more interesting part would be if we can require a release version to be published to either master or a backports branch, but I'm not sure exactly how the checks work. We could try that.

@dhardy
Copy link
Member Author

dhardy commented Feb 2, 2026

(I assumed that since this PR was approved that it was fine to also push the tag.)

@newpavlov
Copy link
Member

newpavlov commented Feb 2, 2026

I was referring to GitHub releases which aren't automated... or used at all in this case.

As I wrote in one of issues, personally I don't think we should bother with GH releases, regardless whether they are created manually or using a workflow.

@dhardy
Copy link
Member Author

dhardy commented Feb 2, 2026

The only use I see for them is that people can choose to "watch releases" on GitHub which I do for a few things, though I don't find it massively useful.

tarcieri added a commit to RustCrypto/traits that referenced this pull request Feb 2, 2026
tarcieri added a commit to RustCrypto/traits that referenced this pull request Feb 2, 2026
tarcieri added a commit to RustCrypto/traits that referenced this pull request Feb 2, 2026
tarcieri added a commit to RustCrypto/traits that referenced this pull request Feb 2, 2026
@tarcieri
Copy link
Contributor

tarcieri commented Feb 2, 2026

It's nice to have a page with the release notes for just one particular release, but I can always link to the changelog

tarcieri added a commit to RustCrypto/crypto-bigint that referenced this pull request Feb 2, 2026
tarcieri added a commit to RustCrypto/signatures that referenced this pull request Feb 2, 2026
tarcieri added a commit to RustCrypto/crypto-bigint that referenced this pull request Feb 2, 2026
tarcieri added a commit to RustCrypto/signatures that referenced this pull request Feb 2, 2026
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