Skip to content

Promote develop to master for production - #20

Merged
jmgasper merged 18 commits into
masterfrom
develop
Nov 5, 2026
Merged

jmgasper merged 18 commits into
masterfrom
develop

Conversation

@jmgasper

@jmgasper jmgasper commented Nov 5, 2026 •

Copy link
Copy Markdown
Contributor

Promote develop to master for the production rollout of groups-api-v6. This includes the deployment migration and the application/security fixes listed below.

The workflow uses the scoped CircleCI OIDC deployment role, immutable image releases, image scanning, and ECS health verification. Production deployment requires the approve-prod CircleCI approval. Deployment roles cannot read Parameter Store or secret values.

Included changes:

Release readiness (verified 2026-11-05):

  • Production OIDC role and permission boundary, restricted context, immutable ECR repository, and service/adapter preflight verified. Deployment roles explicitly deny Parameter Store and secret reads.
  • Production workflow requires approve-prod. Health-check bootstrap is either installed or supported by the reviewed release adapter.
  • The reviewed development commit is running on stable ECS tasks; running image tags match the source commit.

Remaining release gates:

  • Complete operator dev validation, required GitHub checks/reviews, and CircleCI production approval.

Production readiness records and promotion index: private infrastructure repository.

jmgasper added 18 commits August 5, 2026 15:47
fix(security): remediate September 2026 findings
Adopt tc-core-library-js v4 shared authentication and bus clients
…kage-constraints

fix: allow Alpine package updates in CircleCI Docker builds
…026-11

fix: remediate ECR and GitHub security findings
…s-rc2

chore: adopt core v4.0.0-rc.2 identity denylists
…yment

Prepare groups-api-v6 develop deployment with OIDC v2.0.5
@github-advanced-security

Copy link
Copy Markdown

You are seeing this message because GitHub Code Scanning has recently been set up for this repository, or this pull request contains the workflow file for the Code Scanning tool.

What Enabling Code Scanning Means:

  • The 'Security' tab will display more code scanning analysis results (e.g., for the default branch).
  • Depending on your configuration and choice of analysis tool, future pull requests will be annotated with code scanning analysis results.
  • You will be able to see the analysis results for the pull request's branch on this overview once the scans have completed and the checks have passed.

For more information about GitHub Code Scanning, check out the documentation.

@jmgasper
jmgasper marked this pull request as ready for review November 5, 2026 01:54
@jmgasper
jmgasper merged commit 219da79 into master Nov 5, 2026
14 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.

2 participants