Releases: aws-powertools/actions
v1.5.1
What's Changed
Patch release to upgrade dependencies and workflow actions - no new features.
Full Changelog: v1.5.0...v1.5.1
v1.5.0
Summary
This release fixes a bug in the version-n-changelog GitHub Action that caused it to fail starting due to a reference to the secrets object. The release also improves the logic around handling the version-type input.
Full Changelog: v1.4.0...v1.5.0
v1.4.0
Summary
This release fixes a bug in the version-n-changelog GitHub Action that caused the release-type input to be ignored. The release also adds new logic to detect when the GitHub Action is running in debug mode and enable verbose logging in the CLI.
Full Changelog: v1.3.0...v1.4.0
v1.3.0
Summary
Starting from this release the version-n-changelog GitHub Action sets the new version number as GitHub Output. This allows consumers to use the output and reference it elsewhere, for example in the title of a PR.
Full Changelog: v1.2.0...v1.3.0
v1.2.0
Summary
This release updates the version-n-changelog GitHub Action to better query repository labels, avoiding pagination issues and ensuring labels are found regardless of their count.
Full Changelog: v1.1.0...v1.2.0
v1.1.0
Summary
This release fixes the version-n-changelog GitHub Action by changing the way it references the cached-node-modules GitHub Action. Specifically, it changes the path so that it can be run from other repositories.
The release also removes the unused files input from the create-pr action.
Full Changelog: v1.0.0...v1.1.0
v1.0.0
Summary
This release adds a new GitHub Action that can be used by other repositories to bump the version of a Node.js project and create/update its changelog based on its git history. The action is built on top of bump-n-go an opinionated CLI I built as a side project that matches exactly how we version/operate projects in this org.
The action looks at the git history of a project and then analyzes all the conventional commits made since the last git tag (or the beginning if none exists). Based on this it determines the next version increase (patch, minor, major) and applies this version to the project, including monorepos!
In doing so it also creates/update the main CHANGELOG.md file of the project with all the changes, and the package-specific CHANGELOG.md files for each workspace in the case of a monorepo.
When determining a version and creating the changelog, the action will only account for commits having types that affect end-user behavior. As such, commits changing CI, code style, tests, etc. don't generate a version bump and don't appear in the CHANGELOG.md files.
The release also:
- updates the existing
cached-node-modulesaction by bumping the default Node.js version and changing the case of one of the input to match other similar actions - removes the unfinished/unused `close-issue-message action, since we're no longer interested in it and its functionalities are covered by our GitHub App
- adds to the repo the
create-praction, currently duplicated in at least 3 repos in this org and that can now be centralized - adds
README.mdfiles documenting the action to all actions