chore: Release 0.1.0 to GitHub Packages - #2
Merged
Merged
Conversation
Published on a tag, with the tag and the manifest checked against each other so a version cannot name a package it is not. On its own version line rather than the core it is used by: this is a library, and what a consumer needs to know is whether its own interface changed.
The release notes were generated from commit titles. A written entry says what the package is, and the release fails before publishing if the version it is cutting has no entry.
The publish, changelog and release steps were written here first. They now live in the shared actions, where the next package library takes them without copying.
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.
First release of the component library, to GitHub Packages. The agent takes it by version from here on rather than by path, so its checks build against the same components a release publishes.
0.1.0 rather than the core's version: nothing about the components is tied to a core release.