Releases: jefflinse/pr-semver-bump
Releases · jefflinse/pr-semver-bump
v1.7.1: Fixes searching for pull requests based on commit sha.
What's Changed
- fix query for searching for pull requests by @Ghislain89 in #53
New Contributors
- @Ghislain89 made their first contribution in #53
Full Changelog: v1.7.0...v1.7.1
v1.7.0: Upgrade to Node 20 runtime
Upgrades the Node runtime from version 16 to 20.
v1.6.0: Add "noop-labels" to allow for PRs that result in no new version
- Adds a
noop-labels
configuration option for specifying one or more labels that, if present, will result in no new version after a PR is merged.
New 'base-branch' option, dependency updates, and bug fixes
- Adds a new, optional
base-branch
parameter. When set totrue
, the action filters out tags that are not on the PR base branch to find the latest version tag. - Fixes the expected logic around what happens when a prefix or suffix is required but not present in the PR body
- Updates all dependencies to their latest versions
v1.3.2: Update Dependencies
npm audit fix --force
npm run all
for verification
v1.3.1: Support for rebase merges; dependency updates
- Update all dependencies
- Regenerate
.eslintrc.json
using AirBnB config as base - Update all JS files to conform to eslint rules
Security Updates
- Updates
jest
to the latest version to resolve a Dependabot alert related tonode-notifier
Support Squash merges for default squash merge message
v1.2.1 * Support Squash merges for default squash merge message
Better prefix and suffix matching for release notes
Release notes are now extracted line-by-line instead of all at once.
Previously, release notes were extracted in a single regex evaluation. This greatly limited the forms the boundary patterns could take, often forcing PRs to use a particular structure. This change evaluates the boundary conditions on a line-by-line basis (grep-style). This allows for greater flexibility in how PRs are structured.
Initial Release
Initial release of pr-semver-bump with two main modes:
validate
mode is meant to run whenever a pull request is created or updated and ensures that the PR contains a valid release label and (optionally) some release notes.bump
mode is meant to run whenever a pull request merges to master and automatically bumps and tags a new annotated version tag containing the release notes.