chore: bump psake to 5.0.4#65
Conversation
Bump the pinned psake build dependency from 4.9.1 to 5.0.4 (latest stable). The repo uses no features removed in psake 5.0: build.ps1 invokes psake with an explicit -BuildFile and reads $psake.build_success, and there is no OutputHandler/ColoredOutput/$framework or standalone-runner usage. Standalone validation on this repo before propagating to the other modules. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (1)
📝 WalkthroughWalkthroughThe pull request updates the Pester test framework dependency version in the build manifest from 4.9.1 to 5.0.4. This is a straightforward version bump affecting only the declared dependency constraint; no other build dependencies or configuration are modified. ChangesDependency Version Update
Estimated Code Review Effort🎯 1 (Trivial) | ⏱️ ~2 minutes Poem
🚥 Pre-merge checks | ✅ 4 | ❌ 1❌ Failed checks (1 warning)
✅ Passed checks (4 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
There was a problem hiding this comment.
Pull request overview
This PR updates the pinned psake build dependency used by the repository’s PowerShell build pipeline.
Changes:
- Bumps
psakefrom4.9.1to5.0.4inbuild.depend.psd1. - Keeps the existing PSDepend structure and build dependency configuration unchanged.
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
…l reference (#67) PSScriptAnalyzer 1.25.0 intermittently throws "Object reference not set to an instance of an object." from inside the analyzer engine, failing the Lint task on otherwise-green builds. It has struck both Linux (#65) and Windows (#66) CI runners at random, so it is not platform-specific and a non-Windows disable would not cover it. Retry the analysis up to three times on that specific null reference, while letting any genuine analysis error surface immediately. Co-authored-by: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Summary
psakebuild dependency inbuild.depend.psd1from 4.9.1 to 5.0.4 (latest stable, a major version bump).Compatibility with psake 5.0 breaking changes
The repo uses none of the removed/changed surfaces:
build.ps1invokes psake with an explicit-BuildFile(the removed default-file fallback doesn't apply) and reads$psake.build_success(still supported).Import-Module psake; Invoke-psake(the removedpsake.ps1/psake.cmdrunners aren't used).OutputHandler/ColoredOutput/$frameworkusage.Task -FromModule … -Dependssyntax still binds on 5.0.4.Test Plan
Breaking Changes
None expected for consumers; dev/build dependency only.
Summary by CodeRabbit