Repository navigation
ci(release): tag and release a package that moved on its own - #112
Merged
Merged
Conversation
The release is tagged and released after core's version. When the linked group lets one package move alone (angular 1.11.1 next to core 1.11.0), v<core> already exists and the workflow made neither a tag nor a GitHub Release for that package. scripts/own-release-packages.js lists such packages: version not core's, and no v<version> tag that covers it. Each gets @dynamic-field-kit/<pkg>@<version> and a Release (not latest) from its own CHANGELOG section. A dry run prints the list.
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.
When one package moves alone (angular 1.11.1 next to core 1.11.0), v already exists, so
release.yml made neither a tag nor a GitHub Release for it: both were made by hand on 14/10.
scripts/own-release-packages.js (with tests) lists the packages whose version is not core's and
has no v tag. Publish tags each @dynamic-field-kit/@; the Release step
makes a Release for it from its own CHANGELOG, not marked latest. Both skip what exists, so a
rerun or resume is safe; a dry run prints the list. Checked: YAML parses, the new loops run
against stubbed git and gh (existing tag/Release skipped, new one made, empty list no-op).