Skip to content

Move PowerShell build to depend on .NET SDK 10.0.101#26595

Merged
daxian-dbw merged 6 commits intoPowerShell:masterfrom
pwshBot:master_package_references-83d6755e6
Dec 15, 2025
Merged

Move PowerShell build to depend on .NET SDK 10.0.101#26595
daxian-dbw merged 6 commits intoPowerShell:masterfrom
pwshBot:master_package_references-83d6755e6

Conversation

@pwshBot
Copy link
Collaborator

@pwshBot pwshBot commented Dec 9, 2025

Transitive - false - none - Automated by PowerShell Bot

@pwshBot pwshBot requested review from a team and jshigetomi as code owners December 9, 2025 20:13
`JsonSchema.Net` 8.0.0 has multiple breaking changes and broke the build. Revert back to 7.4.0. A separate PR is needed to update `JsonSchema.Net` to 8.0.0
@daxian-dbw
Copy link
Member

daxian-dbw commented Dec 11, 2025

JsonSchema.Net 8.0.0 has multiple breaking changes and broke the build. Revert back to 7.4.0.
A separate PR is needed to update JsonSchema.Net to 8.0.0


Also, System.CommandLine should be pinned to 2.0.0. It's for a test project where we expect the assembly version to be 2.0.0.0 and there is no security issue with the 2.0.0 version.

@daxian-dbw daxian-dbw added the CL-BuildPackaging Indicates that a PR should be marked as a build or packaging change in the Change Log label Dec 11, 2025
@iSazonov
Copy link
Collaborator

If we pin a version, it would be nice to add protection comment in csproj.

@daxian-dbw
Copy link
Member

I need to first find out how we pin a version :) so that automated updates like this one won't change it.

@kilasuit
Copy link
Collaborator

@daxian-dbw - In other project's I've used a file / variable built from a hosted file that contianed all allowed & explict dependency versions particularly with ARM templates & required another manual update to that list to allow them being used elsewhere. Can either @Jaykul's Configuration Module / PSDepend or similar be used here which I think should be coming in PSResourceGet at some point for longer term maintainability? I know we now have the ability for version ranges to be of use that we perhaps didn't as easily when I last needed to do something like this.
Short term/long term could be a test that fails when checking for this as a way to get this started & unblock here?

Just food for thought as to how to fix this.

@daxian-dbw daxian-dbw merged commit 3f54d4a into PowerShell:master Dec 15, 2025
50 of 52 checks passed
kilasuit pushed a commit to kilasuit/PowerShell that referenced this pull request Jan 2, 2026
@daxian-dbw daxian-dbw changed the title [master] Update branch for release Move PowerShell build to depend on .NET SDK 10.0.101 Jan 21, 2026
daxian-dbw pushed a commit to daxian-dbw/PowerShell that referenced this pull request Jan 21, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Backport-7.6.x-Migrated CL-BuildPackaging Indicates that a PR should be marked as a build or packaging change in the Change Log

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants