Ship API licenses and verify released artifacts (0.8.7) - #20
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
The API deployment metadata declared MIT, but adopters could not find a repository license. Supply that MIT text and preserve BSD-3-Clause terms for the copied Core schemas and test fixtures with a separate full license and scope notice.
Include the texts in source releases, the container and the existing deployment bundle. Source CI checks exact license bytes; container publication additionally checks the files and OCI license label. Publish software 0.8.7 with unchanged runtime and Core 0.7 behavior.
Validation: 126 local tests passed; six PostgreSQL tests await the real PostgreSQL CI service. The source archive license check passed. Container verification runs in release CI.