Prevent infinite release loop

[automartin5000]

In attempting to recreate the GitHub workflows, I'm a bit stuck on how the workflows work to prevent an infinite loop of releases. The publish:git task creates a new commit/tag and pushes it to remote. However, using the on push to main trigger like projen does would create an infinite loop of releases.

There seems to be a couple shell scripts that handle this check (here and here)? But I don't entirely understand how they work.

Also, even with checks in the GitHub Workflow, I would expect to see duplicate workflow executions every time there's a release with one terminating early, and I'm not seeing that here.

I feel like I'm missing something obvious 😅

[mrgrain]

The manual release trigger that you are using supports making a commit to main to update a change log file.

The projen repo itself uses the continuous release trigger, which does not do that. Instead the change log is exclusively published to the GitHub Releases page.

You are right that the commit to main would trigger an other workflow run, which then terminates early. That's by design, assuming you want to build & test every commit to main.

There are a number of protections in place to make sure that there is not an infinite release loop. They should work, but I can understand the reluctance to trust them. Maybe you could closely monitor your first release and stand by to step in if needed.