You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@opendal.apache.org by "Xuanwo (via GitHub)" <gi...@apache.org> on 2026/09/11 05:50:51 UTC
[PR] feat(release): automate the ATR release lifecycle [opendal]
Xuanwo opened a new pull request, #8279:
URL: https://github.com/apache/opendal/pull/8279
# Which issue does this PR close?
Related to #8052.
# Rationale for this change
Weekly candidates currently stop at source upload and build dispatch. Release managers must separately notify GitHub about voting, create final refs, publish packages, announce the release, and bring prepared versions back to main. Connect those steps to ATR's formal vote result while keeping verification and vote decisions with the release manager.
# What changes are included in this PR?
- Prepare `releases/<version>-rc.N` and maintain an actionable candidate Discussion with ATR revision, verification links, CLI commands and an announcement draft. Synchronize voting hourly, with one reminder per vote round.
- After ATR records a passing resolution, create the retained `releases/<version>` branch and signed final tag at the RC branch commit, cross-checked against its tag. Explicitly dispatch final package workflows, including Ruby, and promote the approved Java RC's Nexus repository. Skip disabled workflows.
- Resume using existing refs, workflow runs, registry state and announcements. Complete GitHub/ATR announcements, create a draft version-sync PR preserving newer main versions, and remove same-version RC branches while retaining their tags.
- Reuse the version tool through `update-version --sync`, choose weekly baselines from published GitHub Releases, and update the release skill and runbooks.
# Are there any user-facing changes?
The new lifecycle applies only to `releases/<version>-rc.N`. **The ongoing 0.59.2-rc.1 vote is excluded:** its branch is `release-candidates/weekly-34560096534-1`, so merging this PR will not migrate it, modify its vote/artifacts/refs, or automatically publish it after resolution. It continues through the existing manual publication procedure. A push to main records the weekly cutoff history; it does not prepare another candidate.
A version-sync PR created with `GITHUB_TOKEN` needs a maintainer reopen or push to trigger PR CI before merging.
External validation: the OpenDAL ATR finish allowlist now contains both new caller workflows, saved and read back on 2026-09-11. A [read-only Actions check](https://github.com/apache/opendal/actions/runs/34567110352) using the actual Nexus CI secrets confirmed authentication, close/promote permissions and the current closed staging repository. That check also exposed the unwrapped Nexus repository response; the parser and regression fixture now match it. Tests exercise real Git/GPG final-ref creation. No end-to-end production publication was executed.
# AI Usage Statement
- Harness: Codex desktop. Model: GPT-6; model variant and effort setting were not exposed. Role: implemented the release orchestration, tests and documentation, and performed local and read-only online verification under maintainer direction. Live publication and announcement execution remain untested.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: commits-unsubscribe@opendal.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [PR] feat(release): automate version planning and ATR publication [opendal]
Posted by "Xuanwo (via GitHub)" <gi...@apache.org>.
Xuanwo merged PR #8279:
URL: https://github.com/apache/opendal/pull/8279
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: commits-unsubscribe@opendal.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org