chore: fix release publishing and complete repo hygiene#90
Merged
Conversation
Fix the failing release workflow: add repository, license, author, homepage and bugs metadata to all six public packages (npm provenance verifies repository.url against the publishing repo), and gate npm publishing off in changesets/action so an empty changeset state can no longer fall through to publishing 0.0.0 scaffolds. Re-enabling publish for the first real release is tracked in #89. Complete the remaining repo hygiene scope from #10: CODEOWNERS, security policy, code of conduct, pull request template and issue forms with a discussions contact link. Refs #1, #10.
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.
M0 closeout: fixes the red release workflow and completes the hygiene scope that #10 left partial.
Release workflow fix
Two root causes from the failed runs on
main:repositorymetadata — npm provenance verifiesrepository.urlin each publishedpackage.jsonagainst the publishing repository and rejected every package with E422. All six public packages now carryrepository(with per-packagedirectory),license,author,homepageandbugs.changesets/actionfalls through tochangeset publish, which attempted to push empty0.0.0scaffolds to npm (provenance rejection was the only thing that stopped them). Thepublishinput is removed: the workflow now only manages version PRs. Re-enabling publish for the first real release is tracked in Re-enable npm publish in the release workflow for the first public release #89 with a full checklist.Repo hygiene (completes #10 scope)
.github/CODEOWNERSSECURITY.md— private disclosure via GitHub Security AdvisoriesCODE_OF_CONDUCT.md— Contributor Covenant 2.1.github/PULL_REQUEST_TEMPLATE.md— issue link, checks, changeset checklistbug_report.yml,feature_request.yml) +config.ymlrouting questions to Discussionstype:buglabelVerification
build/lint/typecheck/testgreen,format:checkcleanRefs #1, #10.