Repository navigation
Fix the npm pack directory; document moving v0.1.0 through the tag ruleset - #84
Merged
Merged
Conversation
release.md said the repository has no tag ruleset. It has the family's, and a plain git push --force of v0.1.0 is refused with GH013 (measured 2026-11-13). The move goes through package-tools' reset-release-tags.py, which lifts the ruleset for the one update and restores it.
npm pack --pack-destination does not create its destination, so the first 0.9.0 publish (run 43451014327) failed in the build job with ENOENT. Reproduced locally (exit 254) and fixed; ToolingTest now requires the mkdir before the pack and was seen failing without it.
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.
Summary
Two fixes found while moving
v0.1.0and publishing@laranail/emojis-picker0.9.0.npm pack.--pack-destinationdoes not create its destination, so the first 0.9.0 publish (run 43451014327) failed in the build job with ENOENT. I introduced this in Picker style menu, UI fixes, API keys and CORS, security hardening, showcase #82. Reproduced locally (exit 254) and fixed.ToolingTestnow requires themkdirbefore the pack, and was seen failing without it.docs/release.md: moving the tag goes through the tag ruleset. The doc said the repository has no tag ruleset. It has the family's, andgit push --force origin v0.1.0is refused with GH013. A move usesreset-release-tags.py --move, which lifts the ruleset for the one update and restores it. That is howv0.1.0moved to495224dtoday.After merge
Re-dispatch the publish. The dispatch uses the workflow on
main, so this needs no tag move:gh workflow run npm-publish.yml -f tag=v0.1.0 -f version=0.9.0 -f registry=github