updates to the v3 release notes

Author: ericsink

Directory.Build.props

@@ -4,9 +4,9 @@
     <Copyright>Copyright 2014-2025 SourceGear, LLC</Copyright>
     <Company>SourceGear</Company>
     <Authors>Eric Sink</Authors>
-    <Version>3.0.0-pre20250729105745</Version>
-    <AssemblyVersion>3.0.0.2766</AssemblyVersion>
-    <FileVersion>3.0.0.2766</FileVersion>
+    <Version>3.0.1-pre20250805123245</Version>
+    <AssemblyVersion>3.0.1.2773</AssemblyVersion>
+    <FileVersion>3.0.1.2773</FileVersion>
     <Description>SQLitePCLRaw is a Portable Class Library (PCL) for low-level (raw) access to SQLite</Description>
     <ProviderLangVersion>10.0</ProviderLangVersion>
     <GenerateAssemblyProductAttribute>false</GenerateAssemblyProductAttribute>

v3.md

@@ -24,3 +24,56 @@
 - The targeted version of .NET Framework has changed from 4.6.2 to 4.7.1.
 - The default provider for .NET Framework has been changed back to using DLLImport (which worked well) instead of using dynamic loading (which caused more sadness than joy).
 
+## How to update to SQLitePCLRaw 3.0
+
+### From SQLitePCLRaw.bundle_e_sqlite3
+
+If you are using the .bundle_e_sqlite3 package, you don't need to do anything except update the version number:
+
+```
+    <PackageReference Include="sqlitepclraw.bundle_e_sqlite3" Version="3.0.1" />
+```
+
+But you may want to remove the .bundle_e_sqlite3 package reference and add these two instead:
+
+```
+    <PackageReference Include="sqlitepclraw.config.e_sqlite3" Version="3.0.1" />
+    <PackageReference Include="sourcegear.sqlite3" Version="3.50.3" />
+```
+
+Going forward, when you want to update to a new build of SQLite, you will only need to update the reference to the `SourceGear.sqlite3` package.
+
+### From SQLitePCLRaw.bundle_e_sqlcipher
+
+Beginning with the 3.0 release, I will no longer maintain and distribute encryption-enabled SQLite builds without cost.  As far as I know, I was the only one providing a no-cost nuget package of SQLite with encryption.  The `.bundle_e_sqlcipher` package is deprecated.
+
+My recommended solution for SQLite encryption is the SQLite Encryption Extension (SEE), which is the official implementation from the SQLite team:
+
+https://sqlite.org/com/see.html
+
+The SEE is not open source -- a paid license is required.  Once you have obtained a SEE license, if you would like to get SEE builds in the form of a nuget package, you can subscribe to SourceGear's SQLite build service.
+
+If you would like to stay with SQLCipher, you can purchase supported builds from Zetetic, or you can build their open source code yourself.
+
+Another open source option is SQLite3 Multiple Ciphers (from @utelle).  Nuget packages for SQLite3MC are available to customers of SourceGear's SQLite build service.
+
+### From SQLitePCLRaw.bundle_green
+
+The `.bundle_green` package is identical to `.bundle_e_sqlite3` except on iOS, where the package references the SQLite library provided by the operating system.  I recommend changing from `_bundle_green` to the pairing of `.bundle.config.sqlite3` and `SourceGear.sqlite3` described above.
+
+If you prefer to continue using the system SQLite on iOS while using `e_sqlite3` builds on all other platforms, you would need to setup specific package references for the different providers and native libraries for each platform.
+
+If you only use iOS and want to use the system SQLite, you can just do this:
+
+```
+    <PackageReference Include="sqlitepclraw.core" Version="3.0.1" />
+    <PackageReference Include="sqlitepclraw.provider.sqlite3" Version="3.0.1" />
+```
+
+and make this call to initialize things:
+
+```
+    SQLitePCL.raw.SetProvider(new SQLitePCL.SQLite3Provider_sqlite3());
+```
+
+