Fix auto publishing

[shilman]

📦 Published PR as canary version: 1.0.2--canary.11.6da43ba36bdc1d30a6e096c567234deb91775b14.0

✨ Test out this PR locally via:

npm install @storybook/react-docgen-typescript-plugin@1.0.2--canary.11.6da43ba36bdc1d30a6e096c567234deb91775b14.0
# or 
yarn add @storybook/react-docgen-typescript-plugin@1.0.2--canary.11.6da43ba36bdc1d30a6e096c567234deb91775b14.0

Version

Published prerelease version: v1.0.2-next.0

Changelog

🐛 Bug Fix

• Fix auto publishing #11 (@shilman)
• Merge canary to next #6 (@zhzz @shilman @bebraw)
• Fix package name in README #5 (@shilman)
• Fix publishing settings #3 (@shilman)
• fix: Fix rebuild performance for webpack 5 #1 (@bebraw)

⚠️ Pushed to next

• Fix CI branches (@shilman)
• Merge branch 'pr/46' into next (@shilman)
• fix: Fix lint error (@bebraw)
• fix: Add missing getModuleEvaluationSideEffectsState (@bebraw)
• fix: Fix a lint error (@bebraw)
• chore: Drop a redundant dependency (@bebraw)
• fix: Restore old webpack 4 code path to fix hmr after refresh (@bebraw)

Authors: 3

• Egor Pogadaev (@zhzz)
• Juho Vepsäläinen (@bebraw)
• Michael Shilman (@shilman)

[socket-security]

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

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

Issue	Package	Version	Note	Source
Shell access	requireg	0.2.2	Module: child_process Location: lib/resolvers.js	package.json via auto@10.46.0
Shell access	ts-node	10.9.1	Module: child_process Location: dist/child/spawn-child.js	package.json via auto@10.46.0, jest@26.6.3, ts-jest@26.5.6

Next steps

What is shell access?

This module accesses the system shell. Accessing the system shell increases the risk of executing arbitrary code.

Packages should avoid accessing the shell which can reduce portability, and make it easier for malicious shell access to be introduced.

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 package-name@version specifiers. e.g. @SocketSecurity ignore foo@1.0.0 bar@* or ignore all packages with @SocketSecurity ignore-all

• @SocketSecurity ignore requireg@0.2.2
• @SocketSecurity ignore ts-node@10.9.1

[socket-security]

New and updated dependency changes detected. Learn more about Socket for GitHub ↗︎

Packages		Version	New capabilities	Transitives1	Size	Publisher
auto	⬆️	10.2.3...10.46.0	None	+55/-24	10.5 MB	alisowski

🚮 Removed packages: auto-config-hipstersmoothie@4.0.0

Footnotes

1. https://docs.socket.dev ↩