ci: disable semver checks

[agilarity]

This resolves #2470.

Changes

• Allow the CI semver workflow to be triggered manually
  • This provides the option of trying again later
• Do not trigger the CI semver on push

Notes

• The blame for the errors seem to be external to the leptos code. Something changed around 03/24/2024 that now causes even previously passing commits to fail.

[agilarity]

@benwis This is ready for review.

[obi1kenobi]

👋 Hey, I'm the cargo-semver-checks maintainer, and I'm looking into this as well. Of course feel free to merge this PR to get things unblocked while I look, I just want to get to the bottom of this one way or the other.

[agilarity]

Excellent. Thank you.

…

On Sat, Mar 30, 2024, 12:43 PM Predrag Gruevski ***@***.***> wrote: 👋 Hey, I'm the cargo-semver-checks maintainer, and I'm looking into this as well. Of course feel free to merge this PR to get things unblocked while I look, I just want to get to the bottom of this one way or the other. — Reply to this email directly, view it on GitHub <#2471 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ABWF4QMLDIUQNI7FKYUKP6DY23TRXAVCNFSM6AAAAABFPUSXKOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDAMRYGI2TEOBVG4> . You are receiving this because you authored the thread.Message ID: ***@***.***>

[obi1kenobi]

Found the problem. It's not related to cargo-semver-checks but to an interaction between axum and the nightly Rust version used here.

To fix it, either downgrade axum or upgrade to a newer nightly Rust.

Here's what's going on:

• axum is doing nightly detection in its build.rs script, and enables a cfg attribute if so: https://github.com/tokio-rs/axum/blob/dbd61783935e7f33d2f7dbb2fbe391441b8c9790/axum/build.rs#L1-L4
• That cfg is used to enable nightly features, like here: https://github.com/tokio-rs/axum/blob/axum-v0.7.5/axum/src/handler/mod.rs#L128-L133
• That nightly feature was added more recently than in the 1.77-nightly the CI here uses. This is why rustdoc fails in cargo-semver-checks — it doesn't recognize the syntax.

I was stumped because I couldn't reproduce this problem on my own machine. But turns out I'm running 1.79-nightly which is new enough to have the feature in question.

[agilarity]

I recommend merging this PR now and tackling a nightly upgrade later.