Bump version on next: prerelease from 7.1.0-alpha.35 to 7.1.0-alpha.36
#23091
Conversation
![github-actions[bot]](https://avatars.githubusercontent.com/in/15368?s=60&v=4){kind=small}
… "getPackageVersion" method in all package managers
Release: A bunch of fixes to the release tooling
CLI: Prebundle boxen to resolve a ESM/CJS incompatibility
CLI: Fix "Invalid version null" issues by improved version detection
shilman
force-pushed
the
version-prerelease-from-7.1.0-alpha.35
branch
from
e4a03d4
to
be60007
Compare
|
🚨 Potential security issues detected. Learn more about Socket for GitHub ↗︎ To accept the risk, merge this PR and you will not be notified again.
Next stepsWhat is network access?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 deeper look at the dependencyTake 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 packageIf 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 riskTo ignore an alert, reply with a comment starting with
|
…tories Telemetry: Count onboarding stories
shilman
force-pushed
the
version-prerelease-from-7.1.0-alpha.35
branch
from
be60007
to
3c95cf1
Compare
This is an automated pull request that bumps the version from
7.1.0-alpha.35to7.1.0-alpha.36.Once this pull request is merged, it will trigger a new release of version
7.1.0-alpha.36.If you're not a core maintainer with permissions to release you can ignore this pull request.
To do
Before merging the PR, there are a few QA steps to go through:
And for each change below:
This is a list of all the PRs merged and commits pushed directly to
next, that will be part of this release:d5b2ab25bd774e515e069a64cec59bbca598217fIf you've made any changes doing the above QA (change PR titles, revert PRs), manually trigger a re-generation of this PR with this workflow and wait for it to finish. It will wipe your progress in this to do, which is expected.
When everything above is done:
Generated changelog
7.1.0-alpha.36