Releases: MetaMask/action-publish-release
Releases · MetaMask/action-publish-release
3.2.2
Fixed
- Pin the Git tag created in the action to the commit that ran the action, not
main
(#96)
3.2.1
Fixed
- Skip packages with version 0.0.0 (#89)
- Don't attempt publishing published versions (#91)
- Previously it would only compare the current package version with the
latest
version. It would incorrectly attempt publishing already-published non-latest
versions
3.2.0
Added
- Add optional
npm-tag
input to use when checking latest version (#82, #83)
3.1.0
Added
- List package versions in releases for monorepos with independent versioning (#79)
3.0.0
Changed
- BREAKING: Bump minimum Node.js version to 14 (#64)
Fixed
- Handle undefined
versioningStrategy
(#60)
2.1.0
Added
- Support monorepos with independent versions (#51)
2.0.2
Changed
- Resolve GitHub action deprecation warnings (#55)
2.0.1
Changed
- Bump actions, removing deprecation warning (#53)
- Get version and repository info from package.json, improving compatibility with forked repositories. (#49)
2.0.0
Changed
- BREAKING: Use the version in
package.json
to determine the release version instead of the name of the release branch (#46)
- Projects that use this action should no longer pass a
release-branch-prefix
input. Additionally, they should make sure that when a release branch is merged, the version of the package (or root package in the case of a monorepo) is updated to the desired release version.
1.0.3
Changed
- Bump
@metamask/auto-changelog
from 2.3.0
to 2.4.0
(#34)