Skip to content
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.

Sign up for GitHub

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

Jump to bottom

baseline: Avoid warning at major version boundaries #5419

Merged
merged 1 commit into from
Nov 9, 2022
Merged

baseline: Avoid warning at major version boundaries #5419

merged 1 commit into from
Nov 9, 2022

Commits on Nov 9, 2022

  1. baseline: Avoid warning at major version boundaries 

    There is nothing which requires the first release to use version 1.0.
Especially with the desire to rename things at major boundaries, it is
not unexpected that the first release of an artifact may be version 2.0
or 3.0. And in this case, a warning about missing baseline is noise.

Signed-off-by: BJ Hargrave <[email protected]>
    @bjhargrave
    bjhargrave committed Nov 9, 2022
    Configuration menu
    Copy the full SHA
    38b3552 View commit details
    Browse the repository at this point in the history