ci: publish scoped @open-gitagent/opengap only (drop blocked unscoped step)#85
Merged
Conversation
npm rejects the unscoped root name 'opengap' with E403 (too similar to 'openai' — typosquatting guard). Removed the unscoped publish step so the release workflow no longer fails. Package ships under the scoped name.
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.
Why
The unscoped root name
opengapcannot be published — npm returns403 Forbidden: "Package name too similar to existing package openai" (their typosquatting guard). The scoped@open-gitagent/opengappublishes fine.Change
Removes the unscoped publish step from
publish.yml. Releases now publish only the scoped package, so the workflow stops reporting failure. Left an inline comment documenting why.@open-gitagent/opengap@0.4.0is already live on npm.