Skip to content

Conversation

@alexrashed
Copy link
Member

@alexrashed alexrashed commented Sep 22, 2025

Motivation

Last week we added a CI workflow to automatically sync and release this fork for us (see #78).
Unfortunately, one step is still not stable: The actual creation of the release on GitHub. While this is optional, it would be nice to have the release properly being shown in the UI.
The step fails with the following error:

To https://github.com/localstack/moto
 + 662f5b948...8e3016550 localstack -> localstack (forced update)
To https://github.com/localstack/moto
 * [new tag]             5.1.13.post7 -> 5.1.13.post7
tag 5.1.13.post7 exists locally but has not been pushed to getmoto/moto, please push it before continuing or specify the `--target` flag to create a new tag
Error: Process completed with exit code 1.

The logs clearly show that the tag is pushed, but is not recognized by GitHub right afterwards.
This PR tries to address this issue by wrapping the release creation into a "retry" action.

Changes

  • Wrap the creation of the release on GitHub into a "retry" action

@alexrashed alexrashed marked this pull request as ready for review September 22, 2025 11:27
Copy link
Member

@viren-nadkarni viren-nadkarni left a comment

Choose a reason for hiding this comment

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

Thanks for following up on this, looks good to me!

uses: nick-fields/retry@v3
with:
max_attempts: 5
retry_wait_seconds: 120
Copy link
Member

Choose a reason for hiding this comment

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

We could use a shorter wait and more retries to avoid keeping the CI worker blocked

@alexrashed alexrashed merged commit 7498008 into localstack Sep 22, 2025
19 of 27 checks passed
localstack-bot pushed a commit that referenced this pull request Sep 29, 2025
@alexrashed alexrashed deleted the fix-release-creation branch September 29, 2025 07:25
@alexrashed
Copy link
Member Author

FYI: There was one more fix necessary (adding timeout_minutes). I pushed a fix for this on the localstack branch and also combined the changes of this PR with the changes of #78, just to keep the distance / amount of commits on top of moto as low as possible.

@alexrashed
Copy link
Member Author

alexrashed commented Oct 6, 2025

FYI: One more fix was necessary (adding the GH_TOKEN env var to the step creating the release). I again combined this with the changes of #78 to have minimum distance to upstream moto.

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