Repository navigation
Document verified public npm v0.2.0 release and fix registry indexing timeout - #7
Merged
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.
The public npmjs.org registry independently returned version @firexcore/agent-orbs@0.2.0 and a tarball URL: https://github.com/FireXCore/agent-orbs/actions/runs/41674994651 . Previous publish command succeeded (
+ @firexcore/agent-orbs@0.2.0) but the 15-second metadata check failed during npm indexing. This PR extends publish CI verification to 6-minute polling with direct public registry metadata checks, updates README to make public npmjs the primary install path, removes outdated 'not published on npmjs.org' claims, and documents temporary provenance disablement. No package behavior changes.