Bundle release improvements

[eric-schneider]

Two things:

1. [bug] It appears that when at least two PRs are merged in rapid succession, the workflow creates the correct number of tags, but sets them both on the same (most recent?) commit. This results in multiple releases with the same content. See prod-6 and prod-7: https://github.com/riptano/docs-ui/releases
2. [enhancement] We probably shouldn't generate a new release for updates to preview-src/* and README.adoc.

[mlr]

@eric-schneider @colegoldsmith thanks for the bug report!

I just pushed a couple commits that will:

1. Prevent release jobs running concurrently. If multiple PRs are merged in quick succession, the second merge will wait for the first to complete before proceeding.
2. Each release is now generated for the target commit (the one merged that triggered the release) rather than what is on main. This should prevent the releases having duplicate content.

As for item number 2 - we can prevent a release by adding [no-release] to the commit (see my most recent commits). This puts the control in the hands of the author for whether or not a build is triggered.

That said, I do agree it would be nice if the release was also skipped if the only changes were to README or preview-src. I'll leave this issue open to track that enhancement.

[eric-schneider]

As for item number 2 - we can prevent a release by adding [no-release] to the commit (see my most recent commits). This puts the control in the hands of the author for whether or not a build is triggered.

@mlr Argh I'm sorry. You told me about this feature and I totally forgot. Going forward I'll make sure to use [no-release] as necessary.

[mlr]

@eric-schneider it's my bad for not adding it to the README 😅 I will get that updated soon