Cleanup version_added < 5

docs/cli/gel.rst

@@ -200,9 +200,9 @@ Branch
 
 .. versionadded:: 5.0
 
-    |EdgeDB| 5.0 introduced :ref:`branches <ref_datamodel_branches>` to replace
-    databases. If you are running an earlier version of Gel,
-    you will instead use the database commands above.
+|EdgeDB| 5.0 introduced :ref:`branches <ref_datamodel_branches>` to replace
+databases. If you are running an earlier version of Gel,
+you will instead use the database commands above.
 
 :cli:synopsis:`\\branch create NAME`
   Create a new branch. The backslash command mirrors the options of the CLI's

docs/datamodel/access_policies.rst

@@ -1,5 +1,3 @@
-.. versionadded:: 2.0
-
 .. _ref_datamodel_access_policies:
 
 ===============
@@ -442,8 +440,6 @@ making the current user able to see their own ``User`` record.
 Custom error messages
 ^^^^^^^^^^^^^^^^^^^^^
 
-.. versionadded:: 3.0
-
 .. index:: access policy, errmessage, using
 
 When you run a query that attempts a write and is restricted by an access

docs/datamodel/constraints.rst

@@ -153,8 +153,6 @@ tuple of properties or links.
 Partial constraints
 ^^^^^^^^^^^^^^^^^^^
 
-.. versionadded:: 2.0
-
 .. index:: constraint exclusive on, except
 
 Constraints on object types can be made partial, so that they don't apply

docs/datamodel/globals.rst

@@ -1,5 +1,3 @@
-.. versionadded:: 2.0
-
 .. _ref_datamodel_globals:
 
 =======

docs/datamodel/index.rst

@@ -114,8 +114,8 @@ Branch
 
 .. versionadded:: 5.0
 
-   Prior to |EdgeDB| 5 and Gel, *branches* were called "databases"
-   (and "databases" is what Gel branches map to in PostgreSQL).
+Prior to |EdgeDB| 5 and Gel, *branches* were called "databases"
+(and "databases" is what Gel branches map to in PostgreSQL).
 
 Instances can be branched when working on new features, similar to branches in
 your VCS. Each branch has its own schema and data.

docs/datamodel/introspection/mutation_rewrites.rst

@@ -1,5 +1,3 @@
-.. versionadded:: 3.0
-
 .. _ref_datamodel_introspection_mutation_rewrites:
 
 =================

docs/datamodel/introspection/triggers.rst

@@ -1,5 +1,3 @@
-.. versionadded:: 3.0
-
 .. _ref_datamodel_introspection_triggers:
 
 =========

docs/datamodel/links.rst

@@ -643,8 +643,6 @@ There are 4 available target deletion policies.
 Source deletion
 ^^^^^^^^^^^^^^^
 
-.. versionadded:: 2.0
-
 Source deletion policies determine what action should be taken when the
 *source* of a given link is deleted. They are declared with the ``on source
 delete`` clause.

docs/datamodel/mutation_rewrites.rst

@@ -1,5 +1,3 @@
-.. versionadded:: 3.0
-
 .. _ref_datamodel_mutation_rewrites:
 
 =================

docs/datamodel/primitives.rst

@@ -112,8 +112,6 @@ details, see :ref:`EdgeQL > Literals > Tuples <ref_eql_literal_tuple>`.
 Ranges
 ^^^^^^
 
-.. versionadded:: 2.0
-
 Ranges represent some interval of values. The intervals can be bound or
 unbound on either end. They can also be empty, containing no values. Only
 some scalar types have corresponding range types:

docs/datamodel/triggers.rst

@@ -1,5 +1,3 @@
-.. versionadded:: 3.0
-
 .. _ref_datamodel_triggers:
 
 ========
@@ -162,40 +160,39 @@ Now, whenever we run a query, we get a log entry as well:
     the same trigger to be run in two different stages. These triggers will
     generate an error.
 
-.. versionadded:: 4.0
 
-    Our audit logging works, but the update logs have a major shortcoming: they
-    log an update even when nothing changes. Any time an ``update`` query runs,
-    we get a log, even if the values are the same. We can prevent that by
-    using the trigger's ``when`` to run the trigger conditionally. Here's a
-    rework of our ``update`` logging query:
+Our audit logging works, but the update logs have a major shortcoming: they
+log an update even when nothing changes. Any time an ``update`` query runs,
+we get a log, even if the values are the same. We can prevent that by
+using the trigger's ``when`` to run the trigger conditionally. Here's a
+rework of our ``update`` logging query:
 
-    .. code-block:: sdl
+.. code-block:: sdl-invalid
 
-        trigger log_update after update for each
-        when (__old__.name != __new__.name)
-        do (
-          insert Log {
-            action := 'update',
-            target_name := __new__.name,
-            change := __old__.name ++ '->' ++ __new__.name
-          }
-        );
+    trigger log_update after update for each
+    when (__old__.name != __new__.name)
+    do (
+      insert Log {
+        action := 'update',
+        target_name := __new__.name,
+        change := __old__.name ++ '->' ++ __new__.name
+      }
+    );
 
-    If this object were more complicated and we had many properties to compare,
-    we could use a ``json`` cast to compare them all in one shot:
+If this object were more complicated and we had many properties to compare,
+we could use a ``json`` cast to compare them all in one shot:
 
-    .. code-block:: sdl
+.. code-block:: sdl-invalid
 
-        trigger log_update after update for each
-        when (<json>__old__ {**} != <json>__new__ {**})
-        do (
-          insert Log {
-            action := 'update',
-            target_name := __new__.name,
-            change := __old__.name ++ '->' ++ __new__.name
-          }
-        );
+    trigger log_update after update for each
+    when (<json>__old__ {**} != <json>__new__ {**})
+    do (
+      insert Log {
+        action := 'update',
+        target_name := __new__.name,
+        change := __old__.name ++ '->' ++ __new__.name
+      }
+    );
 
 You might find that one log entry per row is too granular or too noisy for your
 use case. In that case, a ``for all`` trigger may be a better fit. Here's a

docs/edgeql/analyze.rst

@@ -1,7 +1,5 @@
 .. _ref_eql_analyze:
 
-.. versionadded:: 3.0
-
 Analyze
 =======
 

docs/edgeql/group.rst

@@ -1,5 +1,3 @@
-.. versionadded:: 2.0
-
 .. _ref_eql_group:
 
 Group

docs/edgeql/literals.rst

@@ -451,8 +451,6 @@ To declare relative duration literals:
 Date durations
 ^^^^^^^^^^^^^^
 
-.. versionadded:: 2.0
-
 The :eql:type:`cal::date_duration` represents spans consisting of some number
 of *months* and *days*. This type is primarily intended to simplify logic
 involving :eql:type:`cal::local_date` values.
@@ -491,8 +489,6 @@ EdgeQL supports a set of functions and operators on duration types.
 Ranges
 ------
 
-.. versionadded:: 2.0
-
 .. index:: ranges, lower bound, upper bound, inclusive, inc_lower, inc_upper,
            empty
 

docs/edgeql/parameters.rst

@@ -19,16 +19,14 @@ parameters are supplied externally.
 Note that we provided an explicit type cast before the parameter. This is
 required, as it enables Gel to enforce the provided types at runtime.
 
-.. versionadded:: 3.0
+Parameters can be named or unnamed tuples.
 
-    Parameters can be named or unnamed tuples.
-
-    .. code-block:: edgeql
+.. code-block:: edgeql
 
-        select <tuple<str, bool>>$var;
-        select <optional tuple<str, bool>>$var;
-        select <tuple<name: str, flag: bool>>$var;
-        select <optional tuple<name: str, flag: bool>>$var;
+    select <tuple<str, bool>>$var;
+    select <optional tuple<str, bool>>$var;
+    select <tuple<name: str, flag: bool>>$var;
+    select <optional tuple<name: str, flag: bool>>$var;
 
 Usage with clients
 ------------------

docs/edgeql/select.rst

@@ -230,8 +230,6 @@ identically to concrete/non-computed links like ``Villain.nemesis``.
 Splats
 ^^^^^^
 
-.. versionadded:: 3.0
-
 .. index:: select, splats, *, **, select *, select all, [is ].*, [is ].**
 
 Splats allow you to select all properties of a type using the asterisk (``*``)

docs/edgeql/sets.rst

@@ -265,8 +265,6 @@ Use the :eql:op:`union` operator to merge two sets.
 Finding common members
 ----------------------
 
-.. versionadded:: 3.0
-
 .. index:: intersect
 
 Use the :eql:op:`intersect` operator to find common members between two sets.
@@ -297,8 +295,6 @@ resulting set.
 Removing common members
 -----------------------
 
-.. versionadded:: 3.0
-
 .. index:: except
 
 Use the :eql:op:`except` operator to leave only the members in the first set

docs/edgeql/types.rst

@@ -93,22 +93,20 @@ typed; you can't simply convert an object to an object of a different type.
 
 .. lint-off
 
-.. versionadded:: 3.0
+You can cast a UUID into an object:
 
-    You can cast a UUID into an object:
-
-    .. code-block:: edgeql-repl
+.. code-block:: edgeql-repl
 
-        db> select <Hero><uuid>'01d9cc22-b776-11ed-8bef-73f84c7e91e7';
-        {default::Hero {id: 01d9cc22-b776-11ed-8bef-73f84c7e91e7}}
+    db> select <Hero><uuid>'01d9cc22-b776-11ed-8bef-73f84c7e91e7';
+    {default::Hero {id: 01d9cc22-b776-11ed-8bef-73f84c7e91e7}}
 
-    If you try to cast a UUID that no object of the type has as its ``id``
-    property, you'll get an error:
+If you try to cast a UUID that no object of the type has as its ``id``
+property, you'll get an error:
 
-    .. code-block:: edgeql-repl
+.. code-block:: edgeql-repl
 
-        db> select <Hero><uuid>'aaaaaaaa-aaaa-aaaa-aaaa-aaaaaaaaaaaa';
-        gel error: CardinalityViolationError: 'default::Hero' with id 'aaaaaaaa-aaaa-aaaa-aaaa-aaaaaaaaaaaa' does not exist
+    db> select <Hero><uuid>'aaaaaaaa-aaaa-aaaa-aaaa-aaaaaaaaaaaa';
+    gel error: CardinalityViolationError: 'default::Hero' with id 'aaaaaaaa-aaaa-aaaa-aaaa-aaaaaaaaaaaa' does not exist
 
 .. lint-on
 

docs/guides/contributing/documentation.rst

@@ -991,8 +991,6 @@ versionadded:: 2.0``.
 
     .. eql:type:: cal::date_duration
 
-        .. versionadded:: 2.0
-
         A type for representing a span of time in days.
 
 **Rendered**

docs/reference/ddl/access_policies.rst

@@ -1,5 +1,3 @@
-.. versionadded:: 2.0
-
 .. _ref_eql_ddl_access_policies:
 
 ===============
@@ -121,11 +119,9 @@ Most sub-commands and options of this command are identical to the
 
 The following subcommands are allowed in the ``create access policy`` block:
 
-.. versionadded:: 3.0
-
-    :eql:synopsis:`set errmessage := <value>`
-        Set a custom error message of :eql:synopsis:`<value>` that is displayed
-        when this access policy prevents a write action.
+:eql:synopsis:`set errmessage := <value>`
+    Set a custom error message of :eql:synopsis:`<value>` that is displayed
+    when this access policy prevents a write action.
 
 :eql:synopsis:`create annotation <annotation-name> := <value>`
     Set access policy annotation :eql:synopsis:`<annotation-name>` to

docs/reference/ddl/globals.rst

@@ -1,5 +1,3 @@
-.. versionadded:: 2.0
-
 .. _ref_eql_ddl_globals:
 
 =======

docs/reference/ddl/migrations.rst

@@ -334,8 +334,6 @@ Create and execute the current migration:
 Reset schema to initial
 =======================
 
-.. versionadded:: 3.0
-
 :eql-statement:
 
 Reset the database schema to its initial state.
@@ -354,8 +352,6 @@ Reset the database schema to its initial state.
 Migration Rewrites
 ==================
 
-.. versionadded:: 3.0
-
 Migration rewrites allow you to change the migration history as long as your
 final schema matches the current database schema.
 

docs/reference/ddl/mutation_rewrites.rst

@@ -1,5 +1,3 @@
-.. versionadded:: 3.0
-
 .. _ref_eql_ddl_mutation_rewrites:
 
 =================

docs/reference/ddl/triggers.rst

@@ -1,5 +1,3 @@
-.. versionadded:: 3.0
-
 .. _ref_eql_ddl_triggers:
 
 ========
@@ -62,24 +60,22 @@ Declare a trigger that inserts a ``Log`` object for each new ``User`` object:
       );
     };
 
-.. versionadded:: 4.0
-
-    Declare a trigger that inserts a ``Log`` object conditionally when an update
-    query makes a change to a ``User`` object:
+Declare a trigger that inserts a ``Log`` object conditionally when an update
+query makes a change to a ``User`` object:
 
-    .. code-block:: edgeql
+.. code-block:: edgeql
 
-        alter type User {
-          create trigger log_update after update for each
-          when (<json>__old__ {**} != <json>__new__ {**})
-          do (
-            insert Log {
-              action := 'update',
-              target_name := __new__.name,
-              change := __old__.name ++ '->' ++ __new__.name
-            }
-          );
+    alter type User {
+      create trigger log_update after update for each
+      when (<json>__old__ {**} != <json>__new__ {**})
+      do (
+        insert Log {
+          action := 'update',
+          target_name := __new__.name,
+          change := __old__.name ++ '->' ++ __new__.name
         }
+      );
+    }
 
 
 Drop trigger

docs/reference/edgeql/analyze.rst

@@ -1,7 +1,5 @@
 .. _ref_eql_statements_analyze:
 
-.. versionadded:: 3.0
-
 Analyze
 =======