-
-
Notifications
You must be signed in to change notification settings - Fork 1
add github workflow for npm release #8
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
Review the following changes in direct dependencies. Learn more about Socket for GitHub. |
All alerts resolved. Learn more about Socket for GitHub. This PR previously contained dependency changes with security issues that have been resolved, removed, or ignored. Ignoring alerts on:
|
c156ce1
to
7f7e88a
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This all looks pretty good, but I have a few comments that should help tighten things up a bit.
- name: Deploy to `${{ inputs.destination_dir }}` directory of `gh-pages` branch | ||
uses: peaceiris/actions-gh-pages@de7ea6f8efb354206b205ef54722213d99067935 | ||
with: | ||
# This `PUBLISH_DOCS_TOKEN` needs to be manually set per-repository. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I have added the github-pages
environment and set PUBLISH_DOCS_TOKEN
in that environment.
ac9b2c8
to
87748e0
Compare
This pull request sets up GitHub code scanning for this repository. Once the scans have completed and the checks have passed, the analysis results for this pull request branch will appear on this overview. Once you merge this pull request, the 'Security' tab will show more code scanning analysis results (for example, for the default branch). Depending on your configuration and choice of analysis tool, future pull requests will be annotated with code scanning analysis results. For more information about GitHub code scanning, check out the documentation. |
@SocketSecurity ignore @npmcli/agent@2.2.2 @npmcli/promise-spawn@7.0.2 @npmcli/promise-spawn@7.0.2 foreground-child@3.3.1 make-fetch-happen@13.0.1 minipass-fetch@3.0.5 node-gyp@10.3.1 prettier@3.6.1 @npmcli/node-gyp@3.0.0 abbrev@2.0.0 cosmiconfig@7.1.0 diff@5.2.0 expand-tilde@2.0.2 global-prefix@1.0.2 npm-normalize-package-bin@3.0.1 read-cmd-shim@4.0.0 resolve-dir@1.0.1 validate-npm-package-name@5.0.1 @npmcli/agent@2.2.2This package used by lavamoat @npmcli/promise-spawn@7.0.2This package used by lavamoat @npmcli/promise-spawn@7.0.2This package used by lavamoat foreground-child@3.3.1This package used by lavamoat make-fetch-happen@13.0.1This package used by lavamoat minipass-fetch@3.0.5This package used by lavamoat node-gyp@10.3.1This package used by lavamoat prettier@3.6.1This package use for code formatting @npmcli/node-gyp@3.0.0This package used by lavamoat abbrev@2.0.0This package used by lavamoat cosmiconfig@7.1.0This package used by depcheck diff@5.2.0This package used by @metamask/auto-changelog expand-tilde@2.0.2This package used by depcheck global-prefix@1.0.2This package used by depcheck npm-normalize-package-bin@3.0.1This package used by lavamoat read-cmd-shim@4.0.0This package used by lavamoat resolve-dir@1.0.1This package used by depcheck validate-npm-package-name@5.0.1This package used by lavamoat |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Changes to workflows look good to me. Thanks for your patience :)
No description provided.