Skip to content

ci: replace pre-releases with PR build artifacts - #86

Open
Cliffback wants to merge 1 commit into
mainfrom
ci/build-artifacts
Open

ci: replace pre-releases with PR build artifacts#86
Cliffback wants to merge 1 commit into
mainfrom
ci/build-artifacts

Conversation

@Cliffback

Copy link
Copy Markdown
Owner

Context

The label-triggered pre-release.yml created a real semver git tag (vX.Y.Z-rc.N) plus a GitHub pre-release. Because release-please computes the next version from the highest semver tag, that RC tag made it treat the RC as the current release and produced the next PR as 1.10.0-rc.1 instead of a stable 1.9.0 — the "release candidate in the title" bug. It also cluttered the releases page.

Change

Drop the durable "release candidate" mechanism and use build artifacts instead:

  • Delete pre-release.yml and cleanup-pre-releases.yml (no more RC git tags → release-please is untouched, no release-page clutter).
  • experimental-build.yml: now builds a 90-day artifact automatically for release-please PRs (opened/synchronize) and on demand via the test-build label for any other PR. A download link is posted in a PR comment (replaced in place); older artifacts self-expire after 90 days. Label removal is now guarded so it only runs when label-triggered.
  • test-build.yml: retention bumped 7d → 90d.

Result

  • release-please PRs → automatic 90-day build artifact (built from the PR head, so it carries the upcoming version + changelog).
  • dev PRs → 90-day artifact on demand via the test-build label.
  • manual main-build retained (test-build.yml).
  • clean releases page; no more "RC" confusion.

Drop the durable "release candidate" pre-release workflows (pre-release.yml, cleanup-pre-releases.yml). They created a semver git tag that interfered with release-please and cluttered the releases page.

Instead, produce 90-day build artifacts in experimental-build: automatically for release-please PRs, and on demand via the test-build label for other PRs. Bump test-build retention to 90 days.
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