CI Fix, propagate release name preprocessing #7599
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
PR description
Fixed Issue(s)
Fixes pre-processed release name propagation in the release workflow jobs via a dedicated preprocessing job.
Post-24.8.0 release, preprocessing of release names was added to ensure they are well formed. The envar method of propagation is limited to a single job however. Subsequent release workflow jobs do not have this value and are failing.
This PR:
pre_process_release_name
Verified on a fork that release name is propagated to the dependent jobs: