Keep YamlDotNet at 11.2.1#3817
Conversation
bb6fd36 to
dc73e12
Compare
dc73e12 to
628e57a
Compare
|
@dependabot rebase |
--- updated-dependencies: - dependency-name: YamlDotNet dependency-version: 18.0.0 dependency-type: direct:production update-type: version-update:semver-major - dependency-name: YamlDotNet dependency-version: 18.0.0 dependency-type: direct:production update-type: version-update:semver-major ... Signed-off-by: dependabot[bot] <support@github.com>
628e57a to
52ad922
Compare
|
The base commit for this pull request has not changed. |
|
@copilot some of the PR pipelines are failing. find the root cause and fix it |
Co-authored-by: polatengin <118744+polatengin@users.noreply.github.com>
Co-authored-by: polatengin <118744+polatengin@users.noreply.github.com>
Co-authored-by: polatengin <118744+polatengin@users.noreply.github.com>
Fixed in 47067b6 and 0046ae3. Root cause was YamlDotNet 18.x being incompatible with the PSRule 2.9.0 module dependency in the same PowerShell session, which caused the module test jobs to fail with YamlDotNet assembly load/type load errors. I reverted the incompatible dependency and lockfile updates and validated the module tests locally. |
|
since copilot reverted the YamlDotNet dependency update and there is no file change remaining in this PR, I'm closing it for now. @BernieWhite we have to check if we can update PSRule to unblock YamlDotNet dependency update in here. Copilot mentioned it in this comment. |
|
OK, I won't notify you again about this release, but will get in touch when a new version is available. You can also ignore all major, minor, or patch releases for a dependency by adding an If you change your mind, just re-open this PR and I'll resolve any conflicts on it. |
Keeps YamlDotNet at 11.2.1 because updating to 18.0.0 is incompatible with the current PSRule module dependency.