chore: Add release workflow #2
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.
This pull request introduces a GitHub Actions workflow for publishing the package to npm and updates the package version to
0.0.3. These changes ensure the package is automatically published when a release is created and that the versioning is consistent across the project.Workflow automation:
.github/workflows/release.yamlto publish the package to npm. The workflow triggers on release events, sets up a Node.js environment, installs dependencies, and publishes the package with provenance and public access.Version updates:
versionfield inpackage.jsonfrom0.0.2to0.0.3to reflect the new release.versionproperty in theMcpServerinitialization insrc/server.tsto match the new package version (0.0.3).