AzLocal.UpdateManagement v0.8.72 - pipeline-template polish (patch)#78
Merged
Conversation
…e-triggers marker (GH+ADO) The schedule-triggers AZLOCAL-CUSTOMIZE marker wrapped ~30 lines of author guidance (incl. the New-AzLocalApplyUpdatesScheduleConfig -OutputPath example and the default-path note). Update-AzLocalPipelineExample preserves the marker BODY from the customer's file, so author corrections inside the marker (e.g. the v0.8.71 .github -> config path fix) never reach an already-deployed consumer. Moved all guidance above the BEGIN marker; marker body now holds only the trigger directive (GH placeholder comment / ADO 'trigger: none'). Queued for next version bump.
…Step.0 -> Step.00 ... Step.9 -> Step.09) Queued for 0.8.72 (no version bump). The GitHub Actions sidebar and ADO pipelines list sort workflows alphabetically by their display name, so Step.10 lexically sorted between Step.1 and Step.2. Zero-padding the single-digit step numbers makes Step.10 sort last as intended. Scope (display/title text only, fully reversible): - GitHub Actions workflow `name:` fields (10 files; Step.10 unchanged) - Azure DevOps `name:` / stage `displayName:` Step.N labels - Header-comment titles (`# Step.N - ...`) on both platforms - One ADO "HOW TO RUN" prose line tracking its renamed display name Left unchanged: artifact names (azlocal-step.N-* functional identifiers) and cross-reference prose (e.g. "Step.9 / Step.10 wiring").
Patch release. No module code, API, or export-count change (60 exports). Bundles the two pipeline-template improvements committed on this branch since v0.8.71: Fixed - apply-updates.yml (GH + ADO): moved the schedule-path author guidance (incl. the New-AzLocalApplyUpdatesScheduleConfig -OutputPath example and the default-path note) OUTSIDE the schedule-triggers AZLOCAL-CUSTOMIZE marker. Update-AzLocalPipelineExample preserves the marker body from the customer's file, so guidance corrections inside the marker never reached already-deployed consumers. Guidance now lives above the BEGIN marker. Changed - Zero-padded single-digit Step.N pipeline display names to two digits (Step.0 -> Step.00 ... Step.9 -> Step.09) so Step.10 sorts last in the GitHub Actions sidebar / Azure DevOps pipelines list. Display/title text only; artifact names and cross-reference prose unchanged. - Bumped GENERATED_AGAINST_MODULE_VERSION pins 0.8.71 -> 0.8.72 across all bundled pipeline YAMLs. Version bump applied to psd1/psm1/CHANGELOG/README/Tests/docs.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
v0.8.72 - pipeline-template polish (patch)
Patch release. No module code, API, or export-count change (60 exports). Bundles the two pipeline-template improvements committed on
users/nebird/developmentsince v0.8.71.Fixed
apply-updates.yml(GitHub Actions + Azure DevOps): moved the schedule-path author guidance (including theNew-AzLocalApplyUpdatesScheduleConfig -OutputPathexample and the default-path note) outside theschedule-triggersAZLOCAL-CUSTOMIZEmarker.Update-AzLocalPipelineExamplepreserves the marker body from the customer's file, so guidance corrections inside the marker never reached already-deployed consumers. Guidance now lives above theBEGINmarker.Changed
Step.Ndisplay names to two digits (Step.0->Step.00...Step.9->Step.09) soStep.10sorts last in the GitHub Actions sidebar / Azure DevOps pipelines list. Display/title text only; artifact names and cross-reference prose unchanged.GENERATED_AGAINST_MODULE_VERSIONpins0.8.71->0.8.72across all bundled pipeline YAMLs.Version bump
Applied to
psd1/psm1/CHANGELOG.md/README.md/Tests/docs.Validation
ConvertFrom-Yaml(0 failures).