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.

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

baseline: Avoid warning at major version boundaries #5419

Merged
merged 1 commit into from Nov 9, 2022

Conversation

bjhargrave
Copy link
Member

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.

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 <bj@hargrave.dev>
@bjhargrave bjhargrave merged commit 161b9cf into bndtools:master Nov 9, 2022
11 checks passed
@bjhargrave bjhargrave deleted the baseline-missing-warning branch Nov 9, 2022
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.

None yet

1 participant