Move Taskboard and Usage Tracker to Git releases - #15
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.
What changed
publishConfig, packageallowlists, prepack hooks, and the tracked npm publish credential config.
semver sources and BB Community shorthand.
capability while preserving existing release tags and historical evidence.
Verification
npm run checkpasses.metadata verification pass at 0.3.1.
at 0.1.2.
npm publish --dry-run --ignore-scriptsworkspace checks refusepublication because each workspace is private.
unpublished.
integration, and historical receipt-artifact audit pass.
Release plan
After merge, create new immutable annotated tags
taskboard/v0.3.1andusage-tracker/v0.1.2at commitce9a73401f7bd448f347f6dc6b9d7ae81565df6e; never move existing tags.