welcome[bot]
commented
1 year ago 🙌 Thanks for opening this pull request! You're awesome.
Closed Maytha8 closed 1 year ago
welcome[bot]
commented
1 year ago 🙌 Thanks for opening this pull request! You're awesome.
socket-security[bot]
commented
1 year ago 🚨 Potential security issues detected. Learn more about Socket for GitHub ↗︎
To accept the risk, merge this PR and you will not be notified again.
This module accesses the network.
Packages should remove all network access that isn't functionally unnecessary. Consumers should audit network access to ensure legitimate use.
Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support [AT] socket [DOT] dev.
If you happen to install a dependency that Socket reports as Known Malware you should immediately remove it and select a different dependency. For other alert types, you may may wish to investigate alternative packages or consider if there are other ways to mitigate the specific risk posed by the dependency.
To ignore an alert, reply with a comment starting with @SocketSecurity ignore followed by a space separated list of package-name@version specifiers. e.g. @SocketSecurity ignore foo@1.0.0 bar@* or ignore all packages with @SocketSecurity ignore-all
@SocketSecurity ignore http-proxy-agent@7.0.0@SocketSecurity ignore https-proxy-agent@7.0.0@SocketSecurity ignore npm@9.7.1@SocketSecurity ignore @octokit/request@6.2.5@SocketSecurity ignore node-fetch@2.6.11@SocketSecurity ignore semantic-release@21.0.5@SocketSecurity ignore agent-base@7.1.0@SocketSecurity ignore @semantic-release/github@8.1.0@SocketSecurity ignore @semantic-release/github@9.0.3@SocketSecurity ignore config-chain@1.1.13socket-security[bot]
commented
1 year ago New and updated dependency changes detected. Learn more about Socket for GitHub ↗︎
| Packages | Version | New capabilities | Transitives^1 | Size | Publisher | |
|---|---|---|---|---|---|---|
| husky | 🆕 | 8.0.3 | filesystem, shell, environment | +0 |
6.44 kB | typicode |
| @semantic-release/changelog | 🆕 | 6.0.3 | filesystem | +159 |
27.4 MB | semantic-release-bot |
| @semantic-release/git | 🆕 | 10.0.1 | None | +160 |
27.4 MB | semantic-release-bot |
| @semantic-release/npm | 🆕 | 10.0.4 | filesystem | +155 |
27.4 MB | semantic-release-bot |
| semantic-release | 🆕 | 21.0.5 | network, environment | +155 |
27.4 MB | semantic-release-bot |
| @semantic-release/github | 🆕 | 8.1.0 | network, filesystem | +165 |
27.8 MB | semantic-release-bot |
Maytha8
commented
1 year ago @theoludwig What are your thoughts on:
dev tag on npm, set the version to dev-<timestamp>, and create a pre-release on GitHub; andrelease script to package.json that allows you to easily publish to the latest tag and create a distribution release.Edit: the only issues with this are that manually releasing can be a security vulnerability and npm provenance doesn't apply here (consequences of publishing outside of a CI environment).
What is the purpose of this pull request? (put an "X" next to item)
What changes did you make? (Give an overview)
semantic-release.commitlint,standard, andts-standard.Which issue (if any) does this pull request address?
Is there anything you'd like reviewers to focus on?
Please check that all the configuration is what is needed. Before merging, make sure the GitHub repository secrets
GH_TOKENandNPM_TOKENare set to a GitHub Personal Access Token and NPM Access Token respectively.