Context

The 2.35.6 release workflow was dispatched from d1e4aa15 but waited more than three hours for a runner. By the time checkout started, 2.35.5-snapshot had advanced. The workflow still checked out the dispatch SHA, pushed the release tag, and then failed to push the next-development commit because the remote branch was no longer a fast-forward.

The release workflow now checks out the current branch ref when the job actually starts. It also delays the remote update until both version commits are ready, then pushes the branch and release tag atomically. If the branch changes during the remaining execution window, GitHub rejects both refs instead of leaving a release tag without the matching branch update.

The publish failure had a separate environment cause: ubuntu-latest moved to Ubuntu 26.04, which Playwright 1.59.0 does not support. The test-executing Build job and the Publish job are pinned to ubuntu-24.04, preserving the Playwright integration tests instead of skipping them. The report-only job remains on ubuntu-latest because it does not launch browsers.

The workflow files parse as valid YAML and git diff --check passes. A local stale-branch simulation confirmed that the atomic push rejects both the branch and tag. A targeted allure run executed all 17 allure-playwright tests successfully with no skipped tests; the PR Build will validate the same suite on the pinned Ubuntu 24.04 runner.

Checklist

• Sign Allure CLA
• Provide unit tests