Skip to content

changelog-promotion-bundle: optional explicit version for version-keyed products (ECE) - #286

Open
cotti wants to merge 1 commit into
mainfrom
changelog-promotion-explicit-version
Open

changelog-promotion-bundle: optional explicit version for version-keyed products (ECE)#286
cotti wants to merge 1 commit into
mainfrom
changelog-promotion-explicit-version

Conversation

@cotti

@cotti cotti commented Aug 13, 2026

Copy link
Copy Markdown
Contributor

Why

Review feedback on elastic/cloud#157943 (lcawl): ECE's published release notes are V.R.M-keyed (e.g. 4.2.0 — see the live page), but the shared promotion workflow unconditionally derives the UTC run date as the bundle version. The docs-builder CLI already supports an explicit version with commit ranges — only this wrapper restricted it.

What

Adds an optional version input to changelog-promotion-bundle.yml:

  • Omitted (serverless, ECH): identical behavior to today — UTC run date derived.
  • Provided (ECE): validated as semver-style (4.2.0, pre-release suffixes allowed) or ISO date, then used as the bundle version. Validation happens via env with a strict regex — the input is never interpolated into the script and a malformed value fails the run with a clear error.

Header comment updated: the workflow covers promotion-triggered products generally; date-keyed is the default, not the definition.

Consumer

elastic/cloud#157943's caller gains a matching optional version field so ECE dispatches can pass 4.2.x. Part of docs-eng-team#741 Track 4.

…ed products

Date-promotion products default to the derived UTC run date, but not every
promotion-triggered product publishes date-keyed notes: ECE's release notes
are V.R.M-keyed (e.g. 4.2.0). Add an optional 'version' input — validated as
semver-or-ISO-date via env, never interpolated — used instead of the derived
date when provided. Omitted input keeps today's behavior for serverless/ECH.
@cotti
cotti requested a review from a team as a code owner August 13, 2026 17:06
@cotti
cotti requested review from Mpdreamz and reakaleek August 13, 2026 17:06
@github-actions

Copy link
Copy Markdown

Label error. Requires exactly 1 of: automation, breaking, bug, changelog:skip, chore, ci, dependencies, documentation, enhancement, feature, fix. Found:

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