Summary

Two related CI/CD defects in the release pipeline:

1. release-please "draft": true configuration creates a race condition that causes release-please to propose erroneous v3.0.0 major version bumps (PRs chore(main): release hve-core 3.0.0 #530, chore(main): release hve-core 3.0.0 #532, chore(main): release hve-core 3.0.0 #534, chore(main): release hve-core 3.0.0 #539, chore(main): release hve-core 3.0.0 #540, chore(main): release hve-core 3.0.0 #542).
2. Extension publish workflows require manual version input via workflow_dispatch, adding unnecessary friction to the release process.

Problem 1: Draft Release Invisibility Race Condition

Root Cause

PR #538 introduced "draft": true in release-please-config.json to solve HTTP 422 errors when uploading assets to immutable published releases. While draft releases are mutable (allowing asset uploads), they have a critical side effect: draft releases do not create git tags.

Within a single release-please invocation, the following sequence occurs:

1. release-please creates a draft release for v2.3.3
2. In the same invocation, release-please searches for the hve-core-v2.3.3 tag to anchor the next version calculation
3. The tag does not exist because draft releases skip tag creation
4. release-please falls back to scanning the entire commit history (320+ commits)
5. It encounters an old commit with a BREAKING CHANGES trailer
6. It proposes a v3.0.0 major version bump via a new PR

The tag bridge step added in PR #538 runs after release-please completes — too late to prevent the race condition within the same invocation.

Evidence

CI log from the release-please step clearly shows:

Found version 2.3.3 for . based on a draft GitHub release
Searching for tag hve-core-v2.3.3
Could not find tag hve-core-v2.3.3
Backfilling commit history to find latest release
Looking at 320 commits

Fix

• Remove "draft": true from release-please-config.json (both root and package level)
• Remove "force-tag-creation": true (requires release-please v17.2.0+; current v17.1.3 silently ignores it)
• Replace the 20-line tag bridge step in main.yml with a 2-line post-creation draft conversion:

gh release edit "$TAG" --draft=true -R "${{ github.repository }}"

This lets release-please create a published release (tag created, searchable), then immediately converts it to draft so assets can be uploaded to a mutable release. The existing publish-release job already runs gh release edit --draft=false at the end to finalize.

Sequence After Fix

release-please creates published v2.3.x release → tag created immediately
  ↓
post-creation step converts release to draft (mutable for asset upload)
  ↓
package/attest/upload jobs upload assets to draft release
  ↓
publish-release job converts draft → published (final)

Problem 2: Extension Publish Workflows Require Manual Version Input

Root Cause

Both extension-publish-prerelease.yml and extension-publish.yml define version as a required workflow_dispatch input. Operators must manually look up the latest release tag and type in the version string every time they trigger a publish, which is error-prone and unnecessary.

Fix

extension-publish-prerelease.yml:

• Change version input from required: true to required: false with default: ''
• When empty, auto-detect from gh release view --json tagName -q '.tagName'
• Strip the hve-core-v prefix
• Derive the pre-release ODD minor version: if the latest release has an even minor version, bump minor by 1 and reset patch to 0 (per the ODD/EVEN channel convention)

extension-publish.yml:

• When version input is empty, auto-detect from gh release view --json tagName -q '.tagName'
• Strip the hve-core-v prefix automatically

Both jobs receive GH_TOKEN: ${{ github.token }} in the detection step for gh CLI authentication.

Files Changed

Branch

fix/release-please-draft-visibility

Related

• Closes bogus v3.0.0 PRs: chore(main): release hve-core 3.0.0 #530, chore(main): release hve-core 3.0.0 #532, chore(main): release hve-core 3.0.0 #534, chore(main): release hve-core 3.0.0 #539, chore(main): release hve-core 3.0.0 #540, chore(main): release hve-core 3.0.0 #542
• Supersedes approach from PR fix(workflows): add manual tag creation for draft releases until release-please-action updates #538 (draft-first strategy)
• Original HTTP 422 error: Cannot upload assets to an immutable release