Skip to content

CCM-14750: tools: package release-check tool - #287

Draft
m-houston wants to merge 4 commits into
mainfrom
ccm-14750-release-check-tool
Draft

m-houston wants to merge 4 commits into
mainfrom
ccm-14750-release-check-tool

Conversation

@m-houston

@m-houston m-houston commented Sep 22, 2026

Copy link
Copy Markdown

Summary

  • add a publishable @nhsdigital/nhs-notify-release-check package under tools/release-check
  • compare arbitrary git release tags with Jira versions and release notes, including the clinical review checks from comms-mgr
  • add multi-release support with comma-separated selectors and * / ? wildcard matching for git tags and Jira version names
  • aggregate commit ranges, Jira issues, and release-note references across the selected releases in one report
  • add the package publishing workflow and workspace wiring for shared-modules consumers
  • include the missing clinical safety and clinical lead counts in the CLI summary output

Why

  • delivers CCM-14750 by moving the reusable release-check logic into shared-modules so other repositories can install and run it consistently
  • supports production catch-up checks where one deployment needs to validate several prior pre-production release cycles together

Validation

  • cd tools/release-check && npm run test:unit -- --runInBand
  • cd tools/release-check && npm run typecheck
  • cd tools/release-check && npm run lint
  • cd tools/release-check && npm run build
  • cd tools/release-check && node dist/cli.js --repo ../../../nhs-notify-client-config --git-tag 0.1.0 --jira-version 71260
  • `cd tools/release-check && node dist/cli.js --repo ../../../nhs-notify-client-config --git-tags '0.1.0,v0.2.,v0.3.' --jira-versions 'client-config-*'
  • cd tools/release-check && npm pack (verifies package name/tarball metadata)

Generalise the release-check logic into a publishable shared-modules package so other repositories can compare git releases against Jira versions and release notes. Include the publish workflow, package wiring, and the comms-mgr clinical review checks in the packaged CLI output.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
@m-houston
m-houston requested a review from a team as a code owner September 22, 2026 16:30
@m-houston m-houston changed the title tools: package release-check tool tools: package release-check tool (CCM-14750) Sep 22, 2026
@m-houston
m-houston marked this pull request as draft September 22, 2026 16:31
@m-houston m-houston changed the title tools: package release-check tool (CCM-14750) CCM-14750: tools: package release-check tool Sep 22, 2026
m-houston and others added 3 commits September 22, 2026 17:42
Align the published package name with the NHS Notify naming convention by switching the package metadata, workflow filters, and documentation to @nhsdigital/nhs-notify-release-check.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Extend the packaged release-check CLI so it can compare multiple git release tags against multiple Jira release versions in one run. Support comma-separated selectors, glob-style wildcards, aggregated release-note lookups, de-duplicated commit and issue sets, and reporting that explains the selected release scope.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Skip the missing clinical lead and safety category checks for Jira issues whose issue type is Bug, while keeping the rest of the release comparison logic unchanged.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant