abhisin98/Changelogs & Package Releases

Automated release pipeline for monorepo package versioning, changelog generation, PR preview comments, Git tagging, GitHub Releases, and package publishing to a configurable registry.

View on GitHub

Trust Signals

Scorecard Score: not yet scored
Maintenance Recency: Activelast commit Aug 20, 2026
License: None

Pinned Snippet

workflow.ymlSHA-pinned

uses: abhisin98/avivox-action-changelogs-and-package-releases@904d53cfec7b0d54d905ebb4c535a99348b5f0ab # v1

tags can be moved; commit SHAs can't. why a SHA?

Inputs

name	description	required	default
release-type	Release strategy (`auto` \| `major` \| `minor` \| `patch` \| `beta` \| `canary`). `auto` detects version bumps via conventional commits.	—	auto
pr-number	Pull request number used for beta version metadata and the PR preview comment. Defaults to the number of the pull request that triggered the workflow — only pass this explicitly if the workflow runs on a non-pull_request event (e.g. workflow_dispatch).	—	${{ github.event.pull_request.number }}
head-sha	HEAD commit SHA used for beta and canary version metadata. Defaults to the head commit SHA of the pull request that triggered the workflow — only pass this explicitly if the workflow runs on a non-pull_request event.	—	${{ github.event.pull_request.head.sha }}
commit-and-push	Whether to commit version bumps and changelogs, create Git tags, and push changes to remote.	—	true
create-release	Whether to create GitHub Releases with extracted changelog release notes.	—	true
commit-message	Commit message template for release version bumps and changelog updates.	—	chore(release): publish package versions and changelogs [skip ci]
github-token	GitHub token or GitHub App token for API operations (commits, tags, releases, PR comments). If empty, default token is used.	—	${{ github.token }}
publish-packages	Whether to publish updated packages to the package registry.	—	true
package-manager	Package manager CLI used to publish packages (`pnpm` \| `npm` \| `yarn`).	—	npm
package-access	Package visibility access level (`public` \| `restricted`).	—	public
publish-package-tag	Custom distribution tag (`dist-tag`) for publishing (e.g. `latest`, `beta`, `canary`). If empty, defaults to `latest` for stable releases, `beta` for beta releases, and `canary` for canary releases.	—	—
publish-extra-args	Custom arguments to append to the publish command (e.g. `--registry https://...`, `--dry-run`).	—	—

Outputs

name	description
packages	JSON array of packages whose version was bumped in this run (unchanged packages are excluded). Each entry contains the package's directory path in `dir`.