Open
Conversation
Adds three reusable workflows for automating the Changesets lifecycle: - changeset-release.yml: versioning and publishing via changesets/action - changeset-check.yml: advisory PR comments for missing changesets - update-lockfile.yml: auto-commits lockfile updates on version PRs Includes documentation for each workflow and an adoption guide in the README covering prerequisites, caller examples, secrets, and the end-to-end release flow.
aaronmedina-dev
assigned
aaronmedina-dev and
TheOrangePuff and unassigned
TheOrangePuff
aaronmedina-dev
requested review from
AdamJHall,
TheOrangePuff and
crispy101
TheOrangePuff
requested changes
Feb 17, 2026
Addresses PR feedback to avoid duplicating documentation. The README now links to the individual workflow docs which already contain inputs, secrets, setup instructions, and example caller YAML.
… docs Moves the prerequisites (Changesets setup, config.json, convenience scripts) and end-to-end release flow documentation from the README into changeset-release.md so all adoption info lives in the individual docs.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description of the proposed changes
Adds three reusable workflows for automating the full Changesets lifecycle across Aligent projects. This follows the same pattern used in aligent/cdk-constructs and aligent/take-flight, extracted into shared workflows so any project can adopt them with minimal configuration.
Workflows added:
changeset-release.yml- Runs on pushes to main. Uses the officialchangesets/actionto either create a version PR (when changeset files exist) or publish packages (when the version PR has been merged). Supports private and public registries, custom version/publish commands, and post-publish hooks.changeset-check.yml- Runs on pull requests. Advisory check that detects when code changes affect publishable packages but no changeset has been added. Posts a comment listing affected packages with instructions, and silently removes it once a changeset is added. Uses the GitHub API to fetch changed files so no full git history is needed.update-lockfile.yml- Runs on pull requests targeting version PR branches. Whenchangesets/actionbumps package.json versions, the lockfile becomes stale. This workflow regenerates and commits the lockfile so CI passes on the version PR.Also included:
docs/Other solutions considered (if any)
Considered extracting the shared Node.js setup steps (checkout, setup-node, corepack, cache, pre-install) into a composite action to reduce duplication across the three workflows. However, composite actions cannot access the
secretscontext, soNPM_TOKENwould need to be passed as a regular input which risks leaking it in logs. The existingnode-pr.ymlworkflow uses the same repeated-steps approach for this reason.Notes to PR author
Notes to reviewers
DO-1994: Add shared changeset workflows