chore(deps): update dotnet monorepo to v10 (major)#271
chore(deps): update dotnet monorepo to v10 (major)#271mohammad-arif662 merged 4 commits intomainfrom
Conversation
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #271 +/- ##
==========================================
+ Coverage 75.48% 75.63% +0.14%
==========================================
Files 38 38
Lines 4083 4083
Branches 487 487
==========================================
+ Hits 3082 3088 +6
+ Misses 817 812 -5
+ Partials 184 183 -1 🚀 New features to boost your workflow:
|
3a9e004 to
2035708
Compare
|
/gemini review |
There was a problem hiding this comment.
Code Review
This pull request updates several core .NET and F# dependencies to a new major version (v10), which corresponds to the upcoming .NET 10 release. These are significant upgrades, especially the jump for FSharp.Core from v7 to v10. Such major version updates carry a high risk of introducing breaking changes. The projects in this solution currently target older frameworks like net8.0 and netstandard2.0, which may not be compatible with these new package versions. It is critical to perform a full build and run all automated tests to ensure compatibility before merging these changes. Manual testing of key features would also be prudent.
Cognite.Simulator.Extensions/Cognite.Simulator.Extensions.csproj
Outdated
Show resolved
Hide resolved
|
@mohammad-arif662 , I see there are several references to using dotnet 8 in the github actions files, such as There may also be other files that needs to be updated to fully make this repo use .NET 10. As this is a major version bump, I think also there should be a full manual test run with the changes in this utils library included in the repos that consume this library. |
84703f5 to
7e868c0
Compare
Edited/Blocked NotificationRenovate will not automatically rebase this PR, because it does not recognize the last commit author and assumes somebody else may have edited the PR. You can manually request rebase by checking the rebase/retry box above. |
|
These changes are manually tested by running the connector (which uses this library) and by running simulation with timeseries using this connector. |
Cognite.Simulator.Extensions/Cognite.Simulator.Extensions.csproj
Outdated
Show resolved
Hide resolved
|
as @abdullah-cognite suggested it's better to build this locally and try to build / run simconnect using this version. |
Tested it by building these changes and used it to build simconnect connector and executed model parsing and simulation run in VM. |
|
risk review ok |
This PR contains the following updates:
7.0.403→10.0.1019.0.11→10.0.19.0.11→10.0.19.10.0→10.1.09.0.11→10.0.1Release Notes
dotnet/dotnet (FSharp.Core)
v10.0.101: .NET 10.0.1 / 10.0.101You can build .NET 10.0 from the repository by cloning the release tag
v10.0.101and following the build instructions in the main README.md.Alternatively, you can build from the sources attached to this release directly.
More information on this process can be found in the dotnet/dotnet repository.
Attached are PGP signatures for the GitHub generated tarball and zipball. You can find the public key at https://dot.net/release-key-2023
v10.0.100: .NET 10.0.0 / 10.0.100You can build .NET 10.0 from the repository by cloning the release tag
v10.0.100and following the build instructions in the main README.md.Alternatively, you can build from the sources attached to this release directly.
More information on this process can be found in the dotnet/dotnet repository.
Attached are PGP signatures for the GitHub generated tarball and zipball. You can find the public key at https://dot.net/release-key-2023
To produce artifacts with the .NET 10 GA version strings, users must pass the branding argument to the build:
--branding rtm.v9.0.101: .NET 9.0.101You can build .NET 9.0 from the repository by cloning the release tag
v9.0.101and following the build instructions in the main README.md.Alternatively, you can build from the sources attached to this release directly.
More information on this process can be found in the dotnet/dotnet repository.
Attached are PGP signatures for the GitHub generated tarball and zipball. You can find the public key at https://dot.net/release-key-2023
dotnet/extensions (Microsoft.Extensions.TimeProvider.Testing)
v10.0.0What's Changed
METGEN004error message: print return type inErrorInvalidMethodReturnTypeby @eduherminio in #6905SummarizingChatReducerby @MackinnonBuck in #6908New Contributors
Full Changelog: dotnet/extensions@v9.10.0...v10.0.0
Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about these updates again.
This PR was generated by Mend Renovate. View the repository job log.