Documentation failed to build

[epage]

• https://docs.rs/crate/conventional/0.5.0
• https://docs.rs/crate/conventional/0.5.0/builds/201165

[INFO] [stderr]  Documenting conventional v0.5.0 (/opt/rustwide/workdir)
[INFO] [stderr] error: Missing code example in this documentation
[INFO] [stderr]   --> src/commit.rs:12:1
[INFO] [stderr]    |
[INFO] [stderr] 12 | /// A conventional commit.
[INFO] [stderr]    | ^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stderr]    |
[INFO] [stderr] note: lint level defined here
[INFO] [stderr]   --> src/lib.rs:79:5
[INFO] [stderr]    |
[INFO] [stderr] 79 |     rustdoc,
[INFO] [stderr]    |     ^^^^^^^
[INFO] [stderr]    = note: `#[deny(missing_doc_code_examples)]` implied by `#[deny(rustdoc)]`
[INFO] [stderr] 

[epage]

My recommendation is that lib.rs should not turn warnings into errors but the CI should with a pinned rustc.

• Faster iteration for developers since they don't have to worry about an idea they are experimenting with to be perfect.
• You only fail what you test
• Warnings can evolve over time, breaking your CI unexpectedly