Repository navigation
chore: add npm keywords and release 0.1.6 - #20
Merged
Merged
Conversation
Co-authored-by: zhangjing <zhangjing798@qq.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
package.jsonversion from0.1.5to0.1.6.keywordsaligned with the repo’s GitHub topics:sql,sandbox,docker,typescript,postgresql,mysql,npm,read-only,text-to-sql,ai-agents.No source, sandbox image digest, README, or workflow changes. README and INTEGRATION do not hardcode the npm package version.
Publish
Do not tag in this PR. After merge to
main, publish by pushing tagv0.1.6(must matchpackage.jsonversion). That tag triggers.github/workflows/publish-npm.yml.Test plan
package.jsonis0.1.6and includes the keywords array.package.json.v0.1.6and letpublish-npm.ymlpublish.