Skip to content

Make version a required input, keep derivation as advisory#16

Merged
darrylabbate merged 1 commit into
actionsfrom
version-input-required
May 20, 2026
Merged

Make version a required input, keep derivation as advisory#16
darrylabbate merged 1 commit into
actionsfrom
version-input-required

Conversation

@darrylabbate
Copy link
Copy Markdown
Member

This removes the GHA workflow's ability to determine the version string on its own.

If the specified version string differs from the logic defined in the derivation script, a warning annotation is logged.

See test workflow here: https://github.com/darrylabbate/aws-libfabric/actions/runs/26064754139

Version selection is a business decision. The operator now explicitly
provides the release version string. The derivation script remains as
a local helper tool for suggesting the next version.

- Rename version_override to version (required)
- Validate format: X.Y.ZamznN.N or X.Y.Z (OFIWG passthrough)
- Warn if input differs from derivation suggestion
- OFIWG detection: check absence of 'amzn' in version string
@darrylabbate darrylabbate requested review from a team and bwbarrett May 18, 2026 23:07
echo "::debug::Derived version=${RELEASE_VERSION} tag=${TAG}"
if [ -n "${SUGGESTED}" ] && [ "${SUGGESTED}" != "${RELEASE_VERSION}" ]; then
ANNOTATION_LOG=$(echo "${DERIVATION_LOG}" | sed 's/$/%0A/' | tr -d '\n')
echo "::warning title=Specified version differs from derived suggestion::Specified version: ${RELEASE_VERSION}%0ADerived suggestion: ${SUGGESTED}%0A%0A${ANNOTATION_LOG}"
Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Should we fail here explicitly?

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

No. Version specification is a business-owned decision (i.e. manual process). The version derivation logic is "best effort" and should catch most mistakes, but it should be purely advisory. We also can't treat something like this as infallible. Maybe if our version format followed a standard like SemVer.

Failing here would be very disruptive in some scenarios and would require an extra "force" parameter of some kind.

@darrylabbate darrylabbate merged commit 65558a1 into actions May 20, 2026
6 checks passed
@darrylabbate darrylabbate deleted the version-input-required branch May 20, 2026 18:16
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.

2 participants