ci(changesets): version packages

[elevatebart]

This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to dev, this PR will be updated.

Releases

[email protected]

Minor Changes

• ab2b90a6 Thanks @elevatebart! - add a param to all templates to access the full doc

[what-the-diff]

PR Summary

• Removal of Redundant File
  The file .changeset/olive-horses-prove.md was deemed unnecessary and has been removed from the project codebase, offering a cleaner project structure.

• Update in Documentation
  The vue-docgen-cli/CHANGELOG.md file has been updated to include the details of the newly released version 4.77.0. It also notes a minor change where a new parameter has been added to all templates enhancing their capability to access the full document.

• Version Increment in vue-docgen-cli package
  The vue-docgen-cli/package.json file, which conveys the metadata for the specific package, has been updated. The previous version was 4.67.0 and it has now been incremented to the latest version 4.77.0 to reflect recent changes and improvements made.

[cypress]

Passing run #614 ↗︎

0

57

0

0

0

Details:

ci(changesets): version packages
Project: vue-styleguidist	Commit: ced10c27ec
Status: Passed	Duration: 15:30 💡
Started: Mar 7, 2024 9:35 PM	Ended: Mar 7, 2024 9:51 PM

Review all test suite changes for PR #1648 ↗︎

[socket-security]

New and removed dependencies detected. Learn more about Socket for GitHub ↗︎

Package	New capabilities	Transitives	Size	Publisher
npm/[email protected]	environment Transitive: eval, filesystem, unsafe	+34	22.4 MB	vue-styleguidist-bot
npm/[email protected]	filesystem Transitive: environment, eval, unsafe	+17	14.3 MB	vue-styleguidist-bot
npm/[email protected]	filesystem Transitive: environment, eval, unsafe	+14	12.6 MB	vue-styleguidist-bot
npm/[email protected]	None	0	38.7 kB	vue-styleguidist-bot
npm/[email protected]	Transitive: environment, eval, filesystem, unsafe	+18	14.6 MB	vue-styleguidist-bot
npm/[email protected]	Transitive: environment, eval, filesystem, unsafe	+16	12.7 MB	vue-styleguidist-bot
npm/[email protected]	Transitive: environment, eval, filesystem, unsafe	+19	14 MB	vue-styleguidist-bot
npm/[email protected]	Transitive: environment, eval, filesystem, unsafe	+17	12.9 MB	vue-styleguidist-bot
npm/[email protected]	environment	+1	138 kB	soda
npm/[email protected]	environment, filesystem Transitive: eval, unsafe	+33	22.3 MB	vue-styleguidist-bot

View full report↗︎

[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.

Alert	Package	Note	Source
Install scripts	npm/[email protected]	Install script: postinstall Source: node ./postinstall.js	packages/vue-inbrowser-compiler-utils/package.json pnpm-lock.yaml

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/[email protected] or ignore all packages with @SocketSecurity ignore-all

• @SocketSecurity ignore npm/[email protected]