feat: add multi-tool support for nsite deployment tools #3
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
- Add support for 4 deployment tools: nsyte (default), nsite-cli, nous-cli, nostr-deploy-cli - Add new 'tool' input parameter to select deployment tool - Add 'private_key' input for tools that don't support bunker authentication - Maintain backward compatibility with nsyte as default tool - Add tool-specific documentation in docs/ directory - Update README with tool comparison table and security warnings - Add comprehensive tests for all supported tools - Bump version to 2.0.0 for this major feature release BREAKING CHANGE: While backward compatible, adds significant new functionality 🤖 Generated with [Claude Code](https://claude.ai/code) Co-Authored-By: Claude <[email protected]>
- Pin nsite-cli to version 0.1.16 - Pin nous-cli to version 0.1.3 - Pin nostr-deploy-cli to version 0.7.6 - Update action to output actual pinned versions - Update tests to verify correct versions - Update documentation to reflect version pinning This ensures reproducible deployments and prevents unexpected breaking changes from tool updates. 🤖 Generated with [Claude Code](https://claude.ai/code) Co-Authored-By: Claude <[email protected]>
- Add prominent colored header showing selected tool - Display tool type, version, and auth method - Add success/failure banners with color coding - Use GitHub Actions notice annotation for tool selection - Improve visibility of deployment status This makes it immediately clear which tool is being used and the deployment outcome. 🤖 Generated with [Claude Code](https://claude.ai/code) Co-Authored-By: Claude <[email protected]>
- Enable version selection for NPX tools (not just nsyte) - Automatically handle version format differences between tools - nsyte: adds "v" prefix if missing (e.g., "0.5.3" → "v0.5.3") - NPX tools: strips "v" prefix if present (e.g., "v0.1.16" → "0.1.16") - Users can input versions with or without "v" prefix - Simplify documentation to just show examples 🤖 Generated with [Claude Code](https://claude.ai/code) Co-Authored-By: Claude <[email protected]>
- Remove Status column from supported tools table - Pin nsyte to v0.12.3 by default (instead of latest) - All tools now use specific versions by default for stability - Empty version input uses tool-specific defaults - Update documentation to show default versions - Update tests to verify default version behavior This ensures reproducible deployments by default while still allowing version overrides. 🤖 Generated with [Claude Code](https://claude.ai/code) Co-Authored-By: Claude <[email protected]>
- Create versions.json as single source of truth for all tool versions - Load versions dynamically in action.yml - Add update-version-docs.sh script to sync README - Add MAINTENANCE.md with version update instructions - Update tests to read expected versions from config This makes it easy to update tool versions by editing a single file. 🤖 Generated with [Claude Code](https://claude.ai/code) Co-Authored-By: Claude <[email protected]>
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.
BREAKING CHANGE: While backward compatible, adds significant new functionality
Resolves #2