Skip to content

New: [AEA-0000] - Tag jira when release is created#93

Merged
anthony-nhs merged 12 commits intomainfrom
update_jira
Mar 18, 2026
Merged

New: [AEA-0000] - Tag jira when release is created#93
anthony-nhs merged 12 commits intomainfrom
update_jira

Conversation

@anthony-nhs
Copy link
Contributor

@anthony-nhs anthony-nhs commented Mar 18, 2026

Summary

  • Routine Change

Details

  • add new optional params to update jira when a when release is created

Copilot AI review requested due to automatic review settings March 18, 2026 09:50
@github-actions
Copy link
Contributor

This PR is linked to a ticket in an NHS Digital JIRA Project. Here's a handy link to the ticket:

AEA-0000

Copy link

Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

Adds optional Jira issue tagging when a semantic-release run creates a release, controlled by workflow inputs/env vars.

Changes:

  • Extend release.config.cjs to optionally run a new local semantic_release_jira plugin when UPDATE_JIRA=true.
  • Introduce packages/semantic_release_jira plugin that discovers a Lambda via CloudFormation export and invokes it with release + ticket data.
  • Update the reusable release workflow to accept Jira-related inputs and (attempt to) assume an AWS role for the Lambda invocation.

Reviewed changes

Copilot reviewed 4 out of 4 changed files in this pull request and generated 4 comments.

File Description
release.config.cjs Adds env-gated inclusion of a local semantic-release plugin for Jira tagging.
packages/semantic_release_jira/index.js New semantic-release success hook that extracts Jira keys from commits and invokes an AWS Lambda.
package.json Adds AWS SDK clients needed by the Jira plugin.
.github/workflows/tag-release-devcontainer.yml Adds inputs/env vars for Jira behavior and an AWS credentials step.
Comments suppressed due to low confidence (1)

.github/workflows/tag-release-devcontainer.yml:118

  • The semantic-release config now references a local plugin (./packages/semantic_release_jira), but this sparse checkout does not include packages/semantic_release_jira, so the plugin code won’t be available at runtime and semantic-release will fail to load it. Include the plugin directory in the sparse checkout and ensure it’s copied/available in the working directory where semantic-release runs (or change the config to reference a resolvable module path).
                  sparse-checkout: |
                      package.json
                      package-lock.json
                      release.config.cjs
                      releaseNotesTemplates/commit.hbs

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

You can also share your feedback on Copilot code review. Take the survey.

@anthony-nhs anthony-nhs changed the title Chore: [AEA-0000] - Tag jira when release is created New: [AEA-0000] - Tag jira when release is created Mar 18, 2026
@sonarqubecloud
Copy link

@anthony-nhs anthony-nhs merged commit 7a89b11 into main Mar 18, 2026
11 checks passed
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.

3 participants