-
Notifications
You must be signed in to change notification settings - Fork 1.1k
chore: release libc v0.2.173 #4481
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
Conversation
|
Heya @marcoieni do you have any idea what might have gone on here? I merged this PR bumping the version from 0.2.172 to 0.2.173, and the release-plz job ran successfully but didn't do a release https://github.com/rust-lang/libc/actions/runs/15544775261/job/43763769879. The same thing happens locally and I can't figure out why. The latest version on crates.io is 0.2.172 so either I'm missing something or this should have published. The PR here is pretty similar to the last release at #4410, which did get a release https://github.com/rust-lang/libc/actions/runs/14461036350/job/40553576959. |
that's weird, release-plz should definitely emit more logs. Since the same thing happens locally, can you add more logs as explained in https://release-plz.dev/docs/troubleshooting#see-debug-logs ? If not sufficient, I would debug release-plz by adding more logs or using a debugger to understand why it quits so early without printing anything. |
I checked with both 0.3.130 and 0.3.135 locally, the output is the same. With debug:
Rerunning with trace, the last few lines:
Nothing stands out to me here, what a weird error. My GH token doesn't have permissions to publish but I don't think that would be an issue. I'll try to debug this a bit better tomorrow or try with a build from source. I was just pretty confused 😆 |
As mentioned at release-plz/release-plz#2270 (comment) I did a bad cherry pick, fixing this at #4486 🎉. |
I'm glad you find the issue! |
No description provided.