Allow concurrent documentation publishing

[jamesfredley]

Depends On

This PR must not merge until apache/grails-github-actions#110 is merged to asf and the updated deploy-github-pages@asf ref is verified.

Summary

Remove the job-level grails-docs-publish queue from snapshot and release documentation publishing. Once the action-level optimistic retry is available, independent documentation jobs can run in parallel and let Git's normal fast-forward rules coordinate updates to the destination branch.

The diff removes only the two queue declarations added by #15988. It does not change documentation generation, credentials, destination paths, action references, or workflow-level release coordination.

Why Remove the Queue

GitHub Actions concurrency groups coordinate runs only within one repository. Grails Core, grails-static-website, and future publishers such as Grails Forge can all target the same website repository, but a grails-docs-publish group in Grails Core cannot coordinate those other repositories. The manual release-publish-docs.yml workflow is also a publisher and has never used this group.

Within Grails Core, the static group makes unrelated release documentation jobs serial:

• the 8.0.0-M5 release run waited 18 minutes 7 seconds for its documentation job to start;
• the 7.2.2 release run waited 11 minutes 15 seconds; and
• the 7.1.5 release run was still queued after more than 6 minutes when observed.

This turned a parallel release sequence into a serial one and required manual retriggering.

Replacement Safety

apache/grails-github-actions#110 retries only genuine non-fast-forward races. It fetches the new destination tip into the existing shallow checkout, verifies descendant history, rebases the unpublished local deployment commit, and retries a normal push. It never force-pushes or auto-resolves true conflicts.

Merge order is therefore mandatory:

1. Merge Safely retry concurrent documentation pushes grails-github-actions#110 to asf.
2. Verify deploy-github-pages@asf contains the retry implementation.
3. Merge this PR into 7.0.x.
4. Merge forward through the maintained branches normally.

Preserved Concurrency

The workflow-level release-pipeline-${{ github.event.release.target_commitish }} group remains unchanged. This PR removes only the documentation publishing mutex.

Verification

• Both edited workflow files parse successfully as YAML.
• git diff --check passes.
• The diff is exactly 12 deletions across two workflow files.
• grails-docs-publish no longer appears in .github/workflows.
• release-publish-docs.yml is byte-identical.
• No Gradle task was run because this is a YAML-only deletion.

[jdaugherty]

I'm confused, we discussed this in the weekly and I made my objection clear to this. Yet you seem to have gone in the opposite direction.

[Copilot]

Copilot encountered an error and was unable to review this pull request. You can try again by re-requesting a review.

[jamesfredley]

@jdaugherty do you have a solution that covers everything listed above? This wasted 3.5 hours this morning, that I did not have.

[jdaugherty]

Yes, I mentioned it on the call. We should be uploading these artifacts and then having a separate workflow to process them.