Skip to content

Update dependency linq2db.SqlServer to v6#37

Open
renovate[bot] wants to merge 3 commits into
mainfrom
renovate/linq2db.sqlserver-6.x
Open

Update dependency linq2db.SqlServer to v6#37
renovate[bot] wants to merge 3 commits into
mainfrom
renovate/linq2db.sqlserver-6.x

Conversation

@renovate
Copy link
Copy Markdown

@renovate renovate Bot commented Apr 17, 2026

This PR contains the following updates:

Package Change Age Confidence
linq2db.SqlServer (source) 5.4.1.96.2.1 age confidence

Release Notes

linq2db/linq2db (linq2db.SqlServer)

v6.2.1: Release 6.2.1

This release contains only bugfixes.

Release notes
Nugets

Full Changelog: linq2db/linq2db@v6.2.0...v6.2.1

v6.2.0: Release 6.2.0

Release highlights:

  • a lot of fixes to reported issues including v6 regressions
  • various improvements to generated SQL
  • added stack guard for v
    isitors, could be managed using LinqToDB.Common.Configuration.TranslationThreadMaxHopCount setting
  • better handling of custom unary/binary operators and support for custom mappings for operators (in case of operator implementation violating contract)
  • support ~ operator translation for all databases
  • support for new .NET 6-10 LINQ operators: CountBy, Index, MaxBy, MinBy, ExceptBy, UnionBy, IntersectBy
  • [PostgreSQL] add timeout option support for native BulkCopy
  • [Oracle] fix found issues in NVARCHAR2 type mapping
  • [SQL Server 2005] scaffold support for JSON and VECTOR types
  • [ClickHouse] support for ClickHouse.Driver v0.9 and v1.0 provider versions. For v1.0+ provider we recommend to set ReadStringsAsByteArrays=true provider option
  • [YDB] continued provider implementation (still in progress)

Release notes
Nugets

Full Changelog: linq2db/linq2db@v6.1.0...v6.2.0

v6.1.0: Release 6.1.0

Release highlights:

  • fixes to reported issues and regressions
  • support of .NET 10 LeftJoin and RightJoin operators
  • re-enable DB2i support for LINQPad driver

Release notes
Nugets

Full Changelog: linq2db/linq2db@v6.0.0...v6.1.0

v6.0.0: Release 6.0.0

Since previous release candidate final release contains following changes:

  • .NET 10 support
  • EF.Core 10 integration
  • LINQPad driver releases now syncronized with Linq To DB releases
  • extension methods that vere available on DataConnection class now available for DataContext-based contexts too
  • DistinctBy support
  • Improved translation of aggregate and window functions
  • string.Join translation and better translation of Sql.ConcatStrings and Sql.StringAggregate calls
  • and many more small features and fixes to defects and regressions from prerelease versions

Provider-specific changes:

  • [Oracle] implement fixes for ORA-01704 string literal too long errors on big LOB parameters
  • [SQL Server 2025] Better VECTOR type support including mappings to float[] and mappings for vector functions
  • [SQLite] add System.Data.SQLite 2 provider support
  • [SQLite] fixes to all known issues n SQLite schema provider
  • added early preview of new provider for YDB database for early adopters

For full list of changes check this page

Release notes

Nugets

New Contributors

Full Changelog: linq2db/linq2db@v5.4.1...v6.0.0


Configuration

📅 Schedule: (UTC)

  • 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 this update again.


  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

@CodeLogicAI
Copy link
Copy Markdown

🚀 AI Library Upgrade workflow started

Checkout and dependency detection in progress. You will see further updates as each step completes.

@CodeLogicAI
Copy link
Copy Markdown

📋 Detected Library Changes

Relevant dependency changes were detected. Specialized scans will be initiated shortly.

Direct Dependency Changes

Type Group ID Artifact ID Old Version New Version
NUGET_CSPROJ N/A linq2db.SqlServer 5.4.1.9 6.2.1

@CodeLogicAI
Copy link
Copy Markdown

🔬 Library scan started

Scanning source branch libraries for upgrade analysis. This may take a few minutes.

@CodeLogicAI
Copy link
Copy Markdown

⚠️ Library scan skipped due to empty downloads

Specialized scan preparation produced no scannable library artifacts (.jar/.dll).

Workflow behavior for this PR:

  • SPECIALIZED_SCAN: marked FAILED
  • TICKET_GENERATION: marked FAILED (AI ticket generation skipped)
  • No AI_LIBRARY_UPGRADE comparison job is created
  • AI implementation is enqueued immediately using fallback instructions from the PR diff

@CodeLogicAI
Copy link
Copy Markdown

🚀 Starting AI implementation...

Beginning implementation of library upgrade changes. This may take several minutes.

Workflow Status

Step Status
DETECT_DEPENDENCIES ✅ SUCCESS
SPECIALIZED_SCAN ❌ FAILED
DIFF_COMPLETE ✅ SUCCESS
TICKET_GENERATION ❌ FAILED
TICKET_IMPLEMENTATION ⏳ PENDING
PUSH_CHANGES ⏳ PENDING

@CodeLogicAI
Copy link
Copy Markdown

AI Library Upgrade (empty scan artifacts)


Immediate fallback

Ticket generation was skipped because specialized scan artifacts could not be downloaded.

Proceeding to attempt AI implementation based on the PR diff using the fallback path.

💡 Configure your CI to post build results back to CodeLogic via the Build Pipeline Data API.

Documentation: https://docs.codelogic.com/Send_Build_Info/

The linq2db.SqlServer package v6.2.1 is a scaffolding package (T4 templates)
that requires the main linq2db package to be referenced separately for runtime
functionality. Added linq2db v6.2.1 to Directory.Packages.props and updated
Dapper.Tests.Performance.csproj to reference both packages.

The main linq2db package v6.2.1 supports .NET Framework 4.6.2+ and .NET Standard 2.0+,
ensuring compatibility with all target frameworks used in this project.
@CodeLogicAI
Copy link
Copy Markdown

✅ AI Library Upgrade Workflow Complete

Workflow Status

Step Status
DETECT_DEPENDENCIES ✅ SUCCESS
SPECIALIZED_SCAN ❌ FAILED
DIFF_COMPLETE ✅ SUCCESS
TICKET_GENERATION ❌ FAILED
TICKET_IMPLEMENTATION ✅ SUCCESS
PUSH_CHANGES ✅ SUCCESS

Result: Changes Successfully Implemented

✅ The AI has successfully implemented the library upgrade changes and pushed them to this PR.

Summary:

  • Comparison Job: 5732bb8f-4963-4431-a180-293d4548a3b5
  • Diff MVD: 3335f8ae-4255-4646-a9bc-07ad7fac71a8
  • Status: Commits pushed successfully

Please review the changes and ensure they meet your requirements.


Generated by CodeLogic AI Library Upgrade

@renovate
Copy link
Copy Markdown
Author

renovate Bot commented Apr 17, 2026

Edited/Blocked Notification

Renovate 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.

⚠️ Warning: custom changes will be lost.

Copy link
Copy Markdown
Member

@garrmark garrmark left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

make improvements using the new features of the library

Copy link
Copy Markdown
Member

@garrmark garrmark left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

make improvements using the new features of the library

Copy link
Copy Markdown

@CodeLogicAI CodeLogicAI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

CodeLogic AI Review Feedback

Status: Your feedback was saved and will be applied in the AI improvement run for this PR ✅

Reviewer feedback:

make improvements using the new features of the library

@CodeLogicAI
Copy link
Copy Markdown

🔧 PR review feedback detected, triggering improvement cycle...

A review comment was received. The AI will apply the feedback and perform cleanup updates.

Improvement Cycle Status

Metric Value
Trigger 🧑‍⚖️ PR Review Feedback
Pass One-shot (this review only)
Status 🔍 Applying Review Feedback
Queue 🚀 Checkout + implementation queued
After CI If the build fails, the build-failure improvement loop runs with its own iteration counter

@CodeLogicAI
Copy link
Copy Markdown

🚀 Starting AI improvement iteration...

Applying the latest human review feedback to this PR.

This commit modernizes the linq2db benchmark code to use v6+ recommended
patterns and removes deprecated APIs:

Changes:
- Replace deprecated DataConnection.DefaultSettings with DataOptions pattern
- Update Linq2DBContext to use DataOptions constructor (v6+ recommended)
- Remove obsolete Linq2DBSettings and ConnectionStringSettings classes
- Use fluent UseSqlServer() configuration method

Benefits:
- Aligns with linq2db v6 best practices and performance optimizations
- Simplifies configuration by removing custom ILinqToDBSettings implementation
- Leverages v6's improved connection management and reduced stack usage
- Prepares codebase for future linq2db enhancements

The new DataOptions pattern is the recommended approach in linq2db v6+ for
configuring database connections, replacing the legacy DefaultSettings API
which has been deprecated.

References:
- https://github.com/linq2db/linq2db/wiki/Linq-To-DB-6
- https://linq2db.github.io/articles/get-started/asp-dotnet-core/
@CodeLogicAI
Copy link
Copy Markdown

✅ AI Library Upgrade Workflow Complete

Workflow Status

Step Status
DETECT_DEPENDENCIES ✅ SUCCESS
SPECIALIZED_SCAN ❌ FAILED
DIFF_COMPLETE ✅ SUCCESS
TICKET_GENERATION ❌ FAILED
TICKET_IMPLEMENTATION ✅ SUCCESS
PUSH_CHANGES ✅ SUCCESS

Result: Changes Successfully Implemented

✅ The AI has successfully implemented the library upgrade changes and pushed them to this PR.

Summary:

  • Comparison Job: 5732bb8f-4963-4431-a180-293d4548a3b5
  • Diff MVD: 3335f8ae-4255-4646-a9bc-07ad7fac71a8
  • Status: Commits pushed successfully

Please review the changes and ensure they meet your requirements.


Generated by CodeLogic AI Library Upgrade

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Development

Successfully merging this pull request may close these issues.

2 participants