diff --git a/docs/source/conf.py b/docs/source/conf.py
index 12d12e77639af885a154773928fe52c21c870602..deb996ce41682ea9a05b736681a9fb9b594c8295 100644
--- a/docs/source/conf.py
+++ b/docs/source/conf.py
@@ -22,7 +22,7 @@ copyright = '2022, Brandon Rodriguez'
 author = 'Brandon Rodriguez'
 
 # The full version, including alpha/beta/rc tags
-release = '0.3.3'
+release = '0.4.0'
 
 
 # -- General configuration ---------------------------------------------------
diff --git a/docs/source/version_history.rst b/docs/source/version_history.rst
index 0633de29b79e0c911d1fe37c0ef649a78c353f04..72075ef0b4c803c4446abfe4af039a8db1d42f0f 100644
--- a/docs/source/version_history.rst
+++ b/docs/source/version_history.rst
@@ -2,28 +2,25 @@ Version History
 ***************
 
 
-0.3.3 - Clause Validation BugFixes
+0.4.0 - Reworked Clause Validation
 ==================================
-* Fixed some bugs with 0.3.2's clause validation.
-
-    * In particular, empty strings as part of VALUES clauses were dropped. This
-      is now fixed.
-
-* Some additional validation and MySQL bugs still remain.
-
-    * Continue to use 0.3.1 for MySQL for now.
-    * Due to these issues, in the future, release 0.3.2 and 0.3.3 will probably
-      be dropped once 0.4.0 is out.
-    * 0.4.0 is intended to be a stable release of the updated clause validation,
-      with compatibility for both MySQL and PostgreSQL.
-
-
-0.3.2 - Reworked Clause Validation Logic
-========================================
-* Reworked internal validation to correct some issues with PostgreSQL queries.
-* Refrained from releasing as 0.4 due to changes breaking MySQL.
-
-    * Use release 0.3.1 for MySQL for now.
+* Expanded/reworked handling of clauses and validation, to hopefully be much
+  more user-friendly.
+
+    * That is, creating clauses with py-dbcn should now feel much more natural,
+      with most extraneous escape character requirements removed.
+    * Previously, this was a problem particularly with quotation characters,
+      depending on the database engine. Now this should be handled much more
+      uniformly regardless of engine.
+    * This will receive further refining in the future, but it's a big step
+      up from original handling.
+
+* If any validation gives issues, each clause type can have validation
+  turned off via passing in the associated bool (value False) on constructing
+  the connector class.
+
+    * Clauses validation turned off this way will be entered as raw string into
+      the query.
 
 
 0.3.1 - Bugfix Release
diff --git a/pyproject.toml b/pyproject.toml
index 01af5f95906a6cd7adfc3edf020867a7bd6831f8..422f4a6cde91da5f3097e898563923a43650ef34 100644
--- a/pyproject.toml
+++ b/pyproject.toml
@@ -4,7 +4,7 @@ build-backend = 'setuptools.build_meta:__legacy__'
 
 [project]
 name = "py-dbcn"
-version = "0.3.3"
+version = "0.4.0"
 description = "Connector for Pythonic interaction with multiple database types."
 readme = "readme.md"
 authors = [{ name = "Brandon Rodriguez", email = "brodriguez8774@gmail.com"}]
diff --git a/setup.cfg b/setup.cfg
index 550ac01110de570f441434496928458dd50c2303..a48288ffeffe375697a58dd64e83dd46fe90c137 100644
--- a/setup.cfg
+++ b/setup.cfg
@@ -1,6 +1,6 @@
 [metadata]
 name = py-dbcn
-version = 0.3.3
+version = 0.4.0
 description = Connector for Pythonic interaction with multiple database types.
 long_description = file: readme.md
 url = https://github.com/brodriguez8774/py-dbcn