Repository navigation
Polish rdrop identity and prepare 0.2.1 registry release - #11
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.
Use rdrop for Raindrop.io as the public product name while preserving repository, npm, CLI and plugin identifiers. Update README/onboarding, plugin descriptions and display metadata, install pins, npm search metadata and release titles for 0.2.1.
Add an npm-backed MCP Registry manifest and a manually dispatched publishing workflow. It checks out the requested release tag, validates all seven npm tarballs against GitHub checksums and published SHA-512 integrity, then publishes with short-lived GitHub OIDC. The official publisher archive is pinned by version and SHA-256. Registry defaults remain local stdio and read-only.
Validation:
make check,make check-integrations, officialmcp-publisher validate, Claude plugin/marketplace validation, organizing skill validation, all-platform npm builds and local offline launcher smoke. Reviewed packaged README links/onboarding/badges and local documentation references. Exercised the release verifier with valid metadata, mismatched registry integrity and a bad archive checksum. No Go runtime behavior changes.