ci: add release workflow for crates.io and npm distribution#18
Merged
Conversation
Set up cross-platform release CI triggered by version tags (v*). Builds native binaries for 5 targets (macOS arm64/x64, Linux x64/arm64, Windows x64), publishes Rust crates to crates.io in dependency order, and distributes CLI binaries via platform-specific npm packages. - Add publish metadata (description, repository, keywords) to all crates - Add LICENSE (MIT) - Create npm wrapper package with platform-specific optionalDependencies - Create GitHub Actions release workflow with matrix build - Add version-bump script for synchronized version updates - Update README with installation instructions Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com> Signed-off-by: Yonghye Kwon <developer.0hye@gmail.com>
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.
Summary
v*tag pushmarknest-core→marknest→marknest-server)npx marknest)Key changes
How to release
Required GitHub secrets
CARGO_REGISTRY_TOKEN: crates.io API tokenNPM_TOKEN: npm automation access tokenTest plan
cargo checkpasses with updated Cargo.tomlcargo publish --dry-runsucceeds formarknest-coremarknestname available on npm🤖 Generated with Claude Code