Skip to content

changesets: Release / Deploy#74

Open
MaximusHaximus wants to merge 1 commit intomasterfrom
changeset-release/master
Open

changesets: Release / Deploy#74
MaximusHaximus wants to merge 1 commit intomasterfrom
changeset-release/master

Conversation

@MaximusHaximus
Copy link
Copy Markdown
Contributor

What is this PR?

This is the automated Release / Deploy PR. It was re-opened manually after changesets/action v1.7.0 closed the previous PR (#71) when updating the version bump to include the changeset from PR #72, but did not create a new one.

What happens when you merge?

Merging triggers the full release and deployment pipeline:

  1. Git tags — version tags are pushed for the service (e.g. proof-generation-api@1.0.2)
  2. Docker build — a new image is built and pushed to GCP Artifact Registry
  3. Kargo promotion — the new image is promoted through dev → staging → production

Warning

Only merge when the team is ready for a production release.


Changesets included

  • brown-pens-return.md
  • mighty-moons-doubt.md
  • openapi-version-and-descriptions.md

@sonarqubecloud
Copy link
Copy Markdown

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