Skip to content

Conversation

Jonas-Isr
Copy link
Member

@Jonas-Isr Jonas-Isr commented Aug 29, 2025

Context

If the Perform Release workflow is triggered so early that the CI workflow of the release PR is not yet green, the Perform Release workflow will fail after the deployment of our code but before merging all the PRs.

This PR adds a note to the release PR to not trigger the Perform Release workflow too early.

Feature scope:

  • add note to release PR

Definition of Done

  • Functionality scope stated & covered
  • Tests cover the scope above
  • Error handling created / updated & covered by the tests above
  • Documentation updated
  • Release notes updated

@Jonas-Isr Jonas-Isr self-assigned this Aug 29, 2025
@Jonas-Isr Jonas-Isr added the please review Request to review a pull request label Aug 29, 2025
@Jonas-Isr Jonas-Isr enabled auto-merge (squash) August 29, 2025 13:27
- [ ] Trigger the [Perform Release Workflow](${{ github.event.repository.html_url }}/actions/workflows/perform-release.yml)
- [ ] Once the `Perform Release` workflow is through, head over to [Central Sonatype](https://central.sonatype.com/publishing/deployments) and log in with the credentials in the Team Password Safe. There should be a published release.")
- [ ] Once all tests of this PR are green, trigger the [Perform Release Workflow](${{ github.event.repository.html_url }}/actions/workflows/perform-release.yml)
- [ ] Once the `Perform Release` workflow is through, head over to [Central Sonatype](https://central.sonatype.com/publishing/deployments) and log in with the credentials in the Team Password Safe. There should be a validated release that can be released by clicking the _release_ button.")
Copy link
Member Author

@Jonas-Isr Jonas-Isr Sep 1, 2025

Choose a reason for hiding this comment

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

I added the bottom note (and did not set the release process to autopublish as we have for AI SDK) to make sure we do not end up in a scenario were we release a version on Maven central but the Gh workflow fails to merge the PRs afterwards, leaving us in an incomplete state.

I am not 100% happy with this approach and would appreciate some feedback.

@Jonas-Isr Jonas-Isr merged commit 793d533 into main Sep 1, 2025
14 checks passed
@Jonas-Isr Jonas-Isr deleted the add-note-to-release-PR branch September 1, 2025 11:06
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
please review Request to review a pull request
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants