README: what adding a plugin actually takes - #28
Merged
Conversation
The old two-line note covered the first step and stopped, which is roughly where this repo's second plugin ran into trouble. Publishing opencode-git-stats turned up three things the instructions did not mention, each of which cost a release attempt: - npm trusted publishing cannot be set up before the package exists; the record fails to attach and the exchange says "package not found". The first version has to go out by hand. - that manual publish needs --ignore-scripts, because npm aborts with EUNSUPPORTED PROTOCOL on the `workspace:*` specifiers inside @OpenTui's own published metadata — which is also why the build has to be explicit rather than left to prepack. - the trust record binds to the package, not the repo, so each plugin needs its own, and it has to name the `npm` environment the publish job declares or the OIDC claims do not match. Also records that `bump=` ignores a prerelease suffix and so skips the version a beta already claimed, and that neither workflow going green means anything reached npm.
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.
The old two-line note covered step one and stopped, which is roughly where this
repo's second plugin ran into trouble.
Publishing
opencode-git-statsturned up three things the instructions did notmention, each of which cost a release attempt:
fails to attach and the exchange reports "package not found", so the first version
has to go out by hand.
--ignore-scripts, because npm aborts withEUNSUPPORTEDPROTOCOLon theworkspace:*specifiers inside@opentui's ownpublished metadata — which is also why the build has to be explicit rather than left
to
prepack.own, and it must name the
npmenvironment the publish job declares or the OIDCclaims will not match.
Also records two things worth knowing before the next release:
bump=computes offthe newest tag ignoring any prerelease suffix, so it skips the version a beta already
claimed; and neither workflow going green means anything actually reached npm.