Automated releases were not publishing packages to the Gitea Package Registry.
release.yml tags commits with [skip ci], which suppresses publish.yml when those tags are pushed. Gitea also does not emit release: published events for releases created by the CI bot, so triggering publish from a release event is not reliable.
This PR adds build and publish steps directly to release.yml, so automated releases publish in the same workflow run. publish.yml remains for manual v*.*.* tag pushes.
Test plan
Merge a PR with a version bump prefix and confirm release.yml builds and publishes the package
Confirm docs-only PRs still do not trigger a release
## Summary
Automated releases were not publishing packages to the Gitea Package Registry.
`release.yml` tags commits with `[skip ci]`, which suppresses `publish.yml` when those tags are pushed. Gitea also does not emit `release: published` events for releases created by the CI bot, so triggering publish from a release event is not reliable.
This PR adds build and publish steps directly to `release.yml`, so automated releases publish in the same workflow run. `publish.yml` remains for manual `v*.*.*` tag pushes.
## Test plan
- [ ] Merge a PR with a version bump prefix and confirm `release.yml` builds and publishes the package
- [ ] Confirm docs-only PRs still do not trigger a release
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.
Summary
Automated releases were not publishing packages to the Gitea Package Registry.
release.ymltags commits with[skip ci], which suppressespublish.ymlwhen those tags are pushed. Gitea also does not emitrelease: publishedevents for releases created by the CI bot, so triggering publish from a release event is not reliable.This PR adds build and publish steps directly to
release.yml, so automated releases publish in the same workflow run.publish.ymlremains for manualv*.*.*tag pushes.Test plan
release.ymlbuilds and publishes the package