Skip to content

Repair CRAN release automation - #765

Open
renkun-ken wants to merge 1 commit into
masterfrom
codex/release-automation
Open

renkun-ken wants to merge 1 commit into
masterfrom
codex/release-automation

Conversation

@renkun-ken

Copy link
Copy Markdown
Member

The existing TagBot container rejects GitHub workflow tokens as invalid personal access tokens, preventing CRAN releases from being published on GitHub. Replace it with a Python standard-library publisher that supports workflow-token authentication.

  • Resolve GitHub's default branch and select the committed release version and matching NEWS section, excluding unmerged feature-branch changes.
  • Publish the exact release tag idempotently; reject conflicting tags, drafts, and prereleases rather than moving or overwriting them.
  • Retain scheduled publication, add manual preview/publication, serialize publication jobs, and restrict write permission to that job.
  • Add offline regression tests and release-procedure documentation; begin development at 0.3.19.9000 with a release-automation changelog entry.

Validation: all 17 release-script tests and actionlint pass on this independent branch. Tests cover preview safety, annotated/conflicting tags, default-branch selection, repeated publication, and recovery after tag creation. Whitespace checks pass.

This PR is based directly on master and contains release automation and its lifecycle metadata. Supersedes the release-automation portion of #762. Broader R-version/native-analysis CI changes are left for separate follow-up.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant