Skip to content

chore(main): release 0.0.20 - #134

Merged
JamesKyburz merged 1 commit into
mainfrom
release-please--branches--main--components--starterstack
Mar 9, 2024
Merged

chore(main): release 0.0.20#134
JamesKyburz merged 1 commit into
mainfrom
release-please--branches--main--components--starterstack

Conversation

@github-actions

@github-actions github-actions Bot commented Mar 9, 2024

Copy link
Copy Markdown
Contributor

🤖 I have created a release beep boop

0.0.20 (2024-03-09)

Bug Fixes

  • graphql tests: npm install (c9a7743)
  • graphql: run tests post build (eea2785)
  • proxy user with tests (0dc81a3)

This PR was generated with Release Please. See documentation.

@github-actions github-actions Bot added the release please release-please pull request label Mar 9, 2024
@github-actions

github-actions Bot commented Mar 9, 2024

Copy link
Copy Markdown
Contributor Author

⚡ These are the changes that will be released when this pull request is merged. ⚡

See full diff in compare view

@github-actions github-actions Bot added the release:next next release ready for production label Mar 9, 2024
@socket-security

socket-security Bot commented Mar 9, 2024

Copy link
Copy Markdown

@socket-security

socket-security Bot commented Mar 9, 2024

Copy link
Copy Markdown

🚨 Potential security issues detected. Learn more about Socket for GitHub ↗︎

To accept the risk, merge this PR and you will not be notified again.

Alert Package NoteSource
Install scripts npm/esbuild@0.20.1

View full report↗︎

Next steps

What is an install script?

Install scripts are run when the package is installed. The majority of malware in npm is hidden in install scripts.

Packages should not be running non-essential scripts during install and there are often solutions to problems people solve with install scripts that can be run at publish time instead.

Take a deeper look at the dependency

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.

Remove the package

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.

Mark a package as acceptable risk

To ignore an alert, reply with a comment starting with @SocketSecurity ignore followed by a space separated list of ecosystem/package-name@version specifiers. e.g. @SocketSecurity ignore npm/foo@1.0.0 or ignore all packages with @SocketSecurity ignore-all

  • @SocketSecurity ignore npm/esbuild@0.20.1

@github-actions
github-actions Bot force-pushed the release-please--branches--main--components--starterstack branch from fa7c9ca to 314e634 Compare March 9, 2024 17:00
@github-actions
github-actions Bot force-pushed the release-please--branches--main--components--starterstack branch from 314e634 to edbd5bb Compare March 9, 2024 20:30
@JamesKyburz
JamesKyburz merged commit 360c96b into main Mar 9, 2024
@JamesKyburz
JamesKyburz deleted the release-please--branches--main--components--starterstack branch March 9, 2024 20:34
@github-actions

github-actions Bot commented Mar 9, 2024

Copy link
Copy Markdown
Contributor Author

@github-actions github-actions Bot added autorelease: tagged and removed release please release-please pull request labels Mar 9, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

autorelease: tagged release:next next release ready for production

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant