Skip to content

ci: add a github actions for publishing to npm - #114

Closed
Sarthak160 wants to merge 1 commit into
mainfrom
npm-release
Closed

Sarthak160 wants to merge 1 commit into
mainfrom
npm-release

Conversation

@Sarthak160

Copy link
Copy Markdown
Contributor

No description provided.

Signed-off-by: Sarthak Shyngle <50234097+Sarthak160@users.noreply.github.com>
@Sarthak160
Sarthak160 requested a review from Sonichigo June 25, 2024 09:16
@Sonichigo

Copy link
Copy Markdown
Contributor

@Sarthak160 have you tested it ?

- name: Setup Node.js
uses: actions/setup-node@v2
with:
node-version: '16' # Change this to the Node.js version you are using

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

please use node 20 or lts. v16 is outdated

@keploy

keploy Bot commented Apr 15, 2025 •

Copy link
Copy Markdown

Nice Pr 😄. We currently support Unit Test Generation only for Go projects.
Stay tuned – support for more languages is coming soon! 🚀

1 similar comment
@keploy-staging

Copy link
Copy Markdown

Nice Pr 😄. We currently support Unit Test Generation only for Go projects.
Stay tuned – support for more languages is coming soon! 🚀

@slayerjain

Copy link
Copy Markdown
Member

Closing this as superseded. Thanks for starting it: this was the first publish workflow for the SDK.

#123 added sdk-publish.yml, which carries the same idea further. It publishes from an sdk-vX.Y.Z tag, refuses a tag that does not match package.json's version, sets registry-url so the npm token is used, checks the packed tarball's licenses, and publishes that tarball with provenance. @keploy/sdk@2.0.11 went out through it.

@slayerjain slayerjain closed this Nov 4, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants