-
-
Notifications
You must be signed in to change notification settings - Fork 0
chore: Update target frameworks and add build error suppression #210
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
Merged
Changes from all commits
Commits
Show all changes
4 commits
Select commit
Hold shift + click to select a range
fc49ea1
fix: add SuppressTfmSupportBuildErrors property to Directory.Build.props
arika0093 32e88b6
I207 test only run .NET 9 or later temporary
arika0093 8017575
fix: remove .NET 6.0 from target frameworks in CI workflow
arika0093 f93e4e4
fix: correct property name in NestedSelectExpr test for clarity
arika0093 File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Some comments aren't visible on the classic Files Changed page.
There are no files selected for viewing
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
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
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
Oops, something went wrong.
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.
Uh oh!
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🧩 Analysis chain
🏁 Script executed:
Repository: arika0093/Linqraft
Length of output: 1714
🌐 Web query:
.NET 6.0 end of life support date💡 Result:
.NET 6.0 reached end of support on November 12, 2024. [1][2]
Sources:
🏁 Script executed:
Repository: arika0093/Linqraft
Length of output: 553
🏁 Script executed:
Repository: arika0093/Linqraft
Length of output: 21166
🏁 Script executed:
Repository: arika0093/Linqraft
Length of output: 4401
🏁 Script executed:
cat Directory.Build.props | head -100Repository: arika0093/Linqraft
Length of output: 115
Document .NET 6.0 removal as a breaking change if the library no longer supports it.
The test matrix removal of .NET 6.0 aligns with its end-of-life status (November 12, 2024), but the CHANGELOG for v0.6.0 does not document this as a breaking change despite including other
[breaking]entries. If .NET 6.0 support has been removed from the library's target frameworks, this must be explicitly documented in the release notes to inform users of the new minimum supported .NET version.Ensure:
[breaking]entry is added to CHANGELOG documenting the minimum .NET version changeAlso applies to: 21-21
🤖 Prompt for AI Agents
Uh oh!
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The library side works on .NET6 (and older versions), but simply because version management of the test library is complicated, tests are run only on .NET8 and above.
(For example,
xunit.runner.visualstudiodoes not work well with v3 in the case of .NET6)There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🧩 Analysis chain
🏁 Script executed:
Length of output: 157
🏁 Script executed:
Length of output: 5580
🏁 Script executed:
Length of output: 1681
@arika0093 Thank you for the clarification! You're absolutely right. I can confirm that the library projects target netstandard2.0 (as defined in
src/Directory.Build.props), which means they remain fully compatible with .NET 6.0 and older versions.The test matrix change only affects which .NET versions are used to run the tests, not the library's compatibility. This is indeed NOT a breaking change for consumers of the library.
I apologize for the confusion in my initial comment. The CHANGELOG does not need to document this as a breaking change since it's purely a test infrastructure simplification.
✏️ Learnings added