The post-merge publish step only ran when HEAD was a release commit. If publish failed (e.g. tea login issue) and was retried on a later push, the Gitea release was never created because HEAD was no longer the release commit.
Fix
Always run publish in post-merge. The devx.ci.publish module is idempotent — it checks if the release already exists and skips if so.
Closes GRM-87
## Problem
The post-merge publish step only ran when HEAD was a release commit. If publish failed (e.g. tea login issue) and was retried on a later push, the Gitea release was never created because HEAD was no longer the release commit.
## Fix
Always run publish in post-merge. The `devx.ci.publish` module is idempotent — it checks if the release already exists and skips if so.
Closes GRM-87
Auto-merge: If all CI checks pass, this PR will be merged automatically.
## Automated PR Review
- Architecture compliance: OK
- Best practices: OK
- Security: OK
- i18n: OK
- Resource management: OK
- Documentation: OK
- Tests: OK
- Commit conventions: OK
No issues found by automated checks.
---
**Auto-merge:** If all CI checks pass, this PR will be merged automatically.
emil
merged commit a13401df13 into master2026-06-25 21:15:03 +00:00
emil
deleted branch GRM-87-always-run-publish2026-06-25 21:15:04 +00:00
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
emil
Problem
The post-merge publish step only ran when HEAD was a release commit. If publish failed (e.g. tea login issue) and was retried on a later push, the Gitea release was never created because HEAD was no longer the release commit.
Fix
Always run publish in post-merge. The
devx.ci.publishmodule is idempotent — it checks if the release already exists and skips if so.Closes GRM-87
Automated PR Review
No issues found by automated checks.
Auto-merge: If all CI checks pass, this PR will be merged automatically.