AzLocal.UpdateManagement v0.8.71 - JUnit export strict-mode fix + sideload schedule-path default + de-numbered pipeline doc refs#77
Merged
Conversation
…eload schedule-path default + de-numbered pipeline doc refs Fixes Export-ResultsToJUnitXml CurrentState/Progress strict-mode crash on UpdateStarted rows (guarded all bare property reads). Corrects GitHub Actions sideload-updates.yml APPLY_UPDATES_SCHEDULE_PATH default from .github/ to config/. De-numbers stale Step.N_*.yml filename refs in audit/assess/authentication-test pipelines + schedule example. Bumps version 0.8.7 -> 0.8.71 (psd1/psm1/test + 22 YAML pins), CHANGELOG, README, release-history.
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
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.
Summary
Patch release v0.8.71. Fixes a production strict-mode crash in JUnit export, corrects the GitHub Actions sideload schedule-path default, and de-numbers stale
Step.N_*.ymlfilename references left behind in pipeline doc strings after the v0.8.7 rename. No public API or export-count change (still 60).Fixes
Export-ResultsToJUnitXmlstrict-mode crash (production) - a live Apply Updates run failed withFailed to export results: The property 'CurrentState' cannot be found on this object. AnUpdateStartedsuccess row legitimately lacksCurrentState/Progress, but the failure and success/default branches read those properties unguarded, which throws underSet-StrictMode -Version Latest. All bare reads (CurrentState,Progress,UpdateName) are now guarded withPSObject.Properties[...]. Regression test added.sideload-updates.ymlAPPLY_UPDATES_SCHEDULE_PATHdefault corrected from./.github/apply-updates-schedule.ymlto./config/apply-updates-schedule.yml, matching whereCopy-AzLocalPipelineExampledrops the starter.Step.N_*.ymlreferences inapply-updates-schedule-audit.yml,assess-update-readiness.yml,authentication-test.yml(both platforms) and theapply-updates-schedule.example.ymlstarter.Version bump 0.8.7 -> 0.8.71
.psd1ModuleVersion + ReleaseNotes,.psm1$script:ModuleVersion, the Pester version assertion, and all 22 bundled YAMLGENERATED_AGAINST_MODULE_VERSIONpins.docs/release-history.md.Testing
Full Pester suite green: 1101 total, 1100 passed, 0 failed, 1 skipped (env-only live-integration).