Add CC by Node Fortress #1430
Open
Add CC by Node Fortress #1430
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
This closes #1429
![cursor[bot]](https://avatars.githubusercontent.com/in/1210556?s=60&v=4){kind=small}
| "versions": { | ||
| "0.1.10": { | ||
| "checksum": "kjstVxN6bQRSF78u0tRnaDbYi8UWw/rXZNgw/LJXl7A=" | ||
| } |
There was a problem hiding this comment.
New snap entry nested inside wrong parent object
High Severity
The new npm:@nodefortress/cc-snap entry is incorrectly nested inside the npm:@hivemindhq/snap object instead of being added as a sibling registry entry. The indentation shows it's at 6 spaces (nested) when it should be at 4 spaces (top-level), matching other entries like npm:@metamask/bitcoin-wallet-snap. This will make the new snap invisible to the registry lookup since it's a property of another snap rather than a proper registry entry.
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.
This closes #1429
Note
Medium Risk
Registry-only change, but any schema/JSON-structure mistake here can break downstream registry consumers or publishing pipelines.
Overview
Registers a new snap,
npm:@nodefortress/cc-snap(CC by Node Fortress), including author/support links, description/category, and an initial0.1.10checksum entry insrc/registry.json.Written by Cursor Bugbot for commit 5e2649e. This will update automatically on new commits. Configure here.