Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I expect this to fail, due to some things being deliberately wrong in
CITATION.cff
andCHANGELOG.md
that should be updated when the answers are figured out. Meanwhile, these are some things I thought should change as I was releasing Lace0.5.0
:BSL-1.1
(which is not a valid SPDX identifier) toBUSL-1.1
. The SPDX entry forBUSL-1.1
is here; I think it's the correct one for our Business Source License, despite the fact that within our license the acronym BSL is used. But @BaxterEaves , I would appreciate it if you verified that theBUSL-1.1
identifier looks like the correct one; otherwise, we can uselicense-file
to specify our includedLICENSE
insteadCargo.toml
files withlicense-file = LICENSE
to instead uselicense = BUSL-1.1
. I considered this to be a MINOR semver changes because they should be the same license, just expressed in different ways. Semver did not appear to be clear on this issue.Cargo.toml
files withlicense = SSPL-1.0
to instead belicense = BUSL-1.1
. This list essentially is all the dependency crates oflace
. I considered all of these changes to be MAJOR changes, since the license is changing.CITATION.CFF
filemaster
--only on PRs