🚀 [Feature]: Add PrereleaseLabels support and ReleaseType calculation #6
+36
−1
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.
The workflow now supports configurable prerelease labels and introduces
ReleaseTypeas a single source of truth for determining what action the publish workflow should take. Previously, theprereleaselabel check was hardcoded while all other labels were configurable, and adding a prerelease label to a PR did not trigger the publish workflow.PrereleaseLabels Configuration
You can now customize which labels trigger a prerelease build via the
PSModule.ymlsettings file:The default value is
prerelease, maintaining backward compatibility.ReleaseType - Single Source of Truth
A new
ReleaseTypeproperty is now calculated and included in theRunobject with these values:ReleasePrereleaseCleanupNoneThis simplifies the publish logic and makes debugging easier since
ReleaseTypeis visible in the Get-Settings logs.Changes
PrereleaseLabelssetting with default valueprereleaselabeledactionReleaseTypecalculation as the single source of truthPublishModulecondition to use$releaseType -ne 'None'ReleaseTypeto theRunobject for downstream consumptionPrereleaseLabelsandReleaseTypedefinitions