[dependabot]

Updated SQLitePCLRaw.core from 2.1.4 to 3.0.2.

Release notes

Sourced from SQLitePCLRaw.core's releases.

3.0.2

Update SourceGear.lib dependency to 3.50.4.2

3.0.1

• Change package ID of SQLitePCLRaw.lib.e_sqlite3 to SourceGear.sqlite3
• Minor changes to readmes and such

3.0.0

v3 release notes

2.1.11

• Update sqlite3 and sqlite3mc builds to SQLite 3.49.1

2.1.10

• Wasm assets for .NET 9
• Update sqlite3 and sqlite3mc builds to SQLite 3.46.1
• Update Android builds to add support for 16kb page size

2.1.9

• Update sqlite3 and sqlite3mc to SQLite 3.46.0
• Add support for risvc64 (thanks @​kasperk81)

2.1.8

Update e_sqlite3 and e_sqlite3mc builds to SQLite 3.45.1

2.1.7

• New packages with support for SQLite3 Multiple Ciphers, thanks to @​bricelam and @​utelle
• Fix for problems with VSTO, thanks to @​farzonl
• Fix for perf-related warning CA1859, thanks to @​bricelam
• Fix for incorrect handling of empty string with Span APIs, thanks to @​nil4
• Add sqlite3_serialize/deserialize, thanks to @​Trinitek and @​garthmz
• Add support for linux-musl-s390x, thanks to @​uweigand
• Fix problem with calling conventions on x86, thanks to @​filipnavara

The versions of the underlying SQLite code for the builds in this release are:

• 3.44.0 for e_sqlite3
• 3.44.0 for e_sqlite3mc
• 3.39.2 for e_sqlcipher

2.1.6

• Wasm assets and RID tweak for compatibility with upcoming .NET 8 release

2.1.5

• Fix support for iOS simulator on arm64 Macs
• Update e_sqlite3 builds to 3.41.2
• (e_sqlcipher builds remain at 3.39.2)

Commits viewable in compare view.

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

[github-actions]

@dependabot merge

[codacy-production]

Up to standards ✅

🟢 Issues 0 issues

Results:
0 new issues

View in Codacy

AI Reviewer: first review requested successfully. AI can make mistakes. Always validate suggestions.

_{TIP This summary will be updated as you push new changes.}

[codacy-production]

Pull Request Overview

This Pull Request is currently empty and does not apply the version update described in the title. Furthermore, the transition from SQLitePCLRaw version 2.x to 3.x is a major upgrade that frequently includes breaking changes, such as renamed package IDs and updated SQLite builds. These architectural changes are not addressed here. The PR should be updated to include the necessary project file modifications and tested against the breaking changes documented in the v3.0.2 release notes.

About this PR

• A major version upgrade (2.x to 3.x) likely involves breaking changes, such as package ID renames mentioned in the release notes, which are not addressed in this PR.
• The PR contains no code changes, so the version update has not been applied to the project files. Please ensure the package reference updates are committed.

Test suggestions

• Verify the project compiles successfully with the updated package version.
• Execute integration tests to ensure that database functionality remains intact after the major version bump.

Prompt proposal for missing tests

Consider implementing these tests if applicable:
1. Verify the project compiles successfully with the updated package version.
2. Execute integration tests to ensure that database functionality remains intact after the major version bump.

_{TIP Improve review quality by adding custom instructions
TIP How was this review? Give us feedback}