Update releasing process

[cryptodev-2s]

Explanation

This PR updates the release process to take in considerations recent changes on create-release-branch.

• Compel users to release packages with breaking changes alongside their dependents [https://github.com/Compel users to release packages with breaking changes alongside their dependents create-release-branch#101]
• Compel users to release new versions of dependencies alongside their dependents [https://github.com/Compel users to release new versions of dependencies alongside their dependents create-release-branch#102]
• Reorder workflow to update changelogs first [https://github.com/Reorder workflow to update changelogs first create-release-branch#109]

References

• Closes Update creating partial release documentation #1741

Changelog

N/A

Checklist

• I've updated the test suite for new or updated code as appropriate
• I've updated documentation (JSDoc, Markdown, etc.) for new or updated code as appropriate
• I've highlighted breaking changes using the "BREAKING" category above as appropriate

[mikesposito]

Nice changes! I left some suggestions

[mikesposito]

I have two more non blocking suggestions, but it looks good

[mikesposito]

Should we wait for the create-release-branch package to be released and updated in core before merging this?

Perhaps we can bump the package in this PR, so that we effectively change the release process along with the docs

[mcmire]

I agree with @mikesposito that we will want to wait until we make a new release of create-release-branch, after which we can bump the version in this repo, but I've made some suggestions in the meantime.

[mcmire]

Two more suggestions below. Also, do you want to update create-release-branch in this branch?

[socket-security]

Updated dependencies detected. Learn more about Socket for GitHub ↗︎

Packages	Version	New capabilities	Transitives	Size	Publisher
@metamask/create-release-branch	1.1.0...2.0.1	None	+1/-0	429 kB

[socket-security]

👍 Dependency issues cleared. Learn more about Socket for GitHub ↗︎

This PR previously contained dependency changes with security issues that have been resolved, removed, or ignored.

Ignoring: @metamask/[email protected]

Next steps

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

[mikesposito]

@SocketSecurity ignore @metamask/[email protected]

The package version 2.0.1 has been published ~30 mins ago: https://www.npmjs.com/package/@metamask/create-release-branch/v/2.0.1?activeTab=versions

[mikesposito]

Looks good!