Repository navigation
docs: maintain a catalog of published Plompy releases - #19
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
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.
Add a publication catalog for all 16 GitHub releases, keeping CHANGELOG.md as the source of release changes. The website can generate a dated page per published version without presenting development-only changes as released.
Includes a public metadata refresh command, maintainer instructions and links to the release history. No runtime, version or release artifacts change.
Validation: 2 catalog tests passed; reviewed public GitHub dates, latest designation and asset links. Website generation and link validation passed against this canonical source.