Repository navigation
Fix the release pack step and set the code owner - #23
Merged
Merged
Conversation
npm pack doesn't create its --pack-destination directory, so the build job failed with ENOENT and nothing was published. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Reclaim PR Agent review · run 130379557618
Reviewed all 1 diff chunks. No blocking defects found.
Full findings and Ponytail reviewPonytail suggestions:
net: -2 lines possible. |
Replace the placeholder team, which doesn't exist. @reclaimprotocol/core can join once it has write access to this repository. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Reclaim PR Agent review · run 130380601657
Reviewed all 1 diff chunks. No blocking defects found. Ponytail: Lean already. Ship. |
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.
Fix the release workflow
The first
release.ymlrun onmainfailed in the build job's Pack the packages step:npm pack --pack-destination distdoesn't createdist, so it failed withENOENTand nothing was published (run 42976549355). This createsdistfirst. I reproduced the failure locally onmainand confirmed that both 0.1.46 tarballs pack aftermkdir -p dist.Merging runs
release.ymlagain, which publishes 0.1.46 if npm trusted publishing is set up. If you published 0.1.46 manually, it creates only the tag and the MCP Registry entry.Set the code owner
.github/CODEOWNERSreplaces the placeholder team, which doesn't exist, with* @predatorx7.@reclaimprotocol/corecan be added once the team has write access to this repository. GitHub ignores owners without write access.🤖 Generated with Claude Code