Prepare 2.1.1 patch release (#14703)

* prepare 2.1.1 patch release

* changing version in the c bindings

* spelling check on release notes

Author: 1ucian0

Cargo.lock

@@ -3,7 +3,7 @@ members = ["crates/*"]
 resolver = "2"
 
 [workspace.package]
-version = "2.1.0"
+version = "2.1.1"
 edition = "2021"
 rust-version = "1.79"  # Keep in sync with README.md, rust-toolchain.toml, and tools/install_rust_msrv.sh
 license = "Apache-2.0"

Cargo.toml

@@ -13,7 +13,7 @@ after_includes = """
 
 #define QISKIT_VERSION_MAJOR 2
 #define QISKIT_VERSION_MINOR 1
-#define QISKIT_VERSION_PATCH 0
+#define QISKIT_VERSION_PATCH 1
 
 #define QISKIT_VERSION_NUMERIC(M,m,p) ((M)<<16|(m)<<8|(p))
 #define QISKIT_VERSION (QISKIT_VERSION_MAJOR<<16 | QISKIT_VERSION_MINOR<<8 | QISKIT_VERSION_PATCH)

crates/cext/cbindgen.toml

@@ -32,7 +32,7 @@
 # The short X.Y version
 version = "2.1"
 # The full version, including alpha/beta/rc tags
-release = "2.1.0"
+release = "2.1.1"
 
 language = "en"
 

docs/conf.py

@@ -1 +1 @@
-2.1.0
+2.1.1

qiskit/VERSION.txt

@@ -1,7 +1,7 @@
 ---
 fixes:
   - |
-    Fixed the deprecation warning for Python 3.9 so that it correctly is identified
+    Fixed the deprecation warning for Python 3.9 so that it is correctly identified
     as being caused by user code when importing Qiskit. Previously, it would not
-    be identified as being caused by user code and this meant that Python's default
+    be identified as being caused by user code, and this meant that Python's default
     warning filters would not display the warning to the user.

releasenotes/notes/fix-deprecation-warning-e512acab95844e36.yaml

@@ -3,10 +3,10 @@ fixes:
   - |
     Fixed the behavior of the ``max_trials`` argument for :class:`.VF2Layout`
     when set to ``None`` or a negative number. The pass was documented as
-    limiting the search to being based on the size of the circuit or target
-    if the option was set to ``None`` and as accepting negative values to
-    specify an unbounded search. However in the 2.1.0 this behavior was
-    incorrectly changed so that ``None`` ran an unbounded search and trying
-    to use a negative number would raise an error. These oversights have
+    limiting the search to be based on the size of the circuit or target
+    if the option was set to ``None``, and as accepting negative values to
+    specify an unbounded search. However, in 2.1.0 this behavior was
+    incorrectly changed so that ``None`` ran an unbounded search and 
+    using a negative number would raise an error. These oversights have
     been corrected so that the pass behaves as documented and is consistent
     with previous releases.

releasenotes/notes/fix-max-trials-vf2-1af00e09dd25a9a7.yaml

@@ -2,5 +2,5 @@
 fixes:
   - |
     Fixed a performance regression when incrementally building :class:`.ParameterExpression`
-    from combining a large number of sub-expressions.
+    by combining a large number of sub-expressions.
     Fixed `#14653 <https://github.com/Qiskit/qiskit/issues/14653>`__

releasenotes/notes/fix-performance-of-large-expression-351afeb1a7ebf4d6.yaml

@@ -0,0 +1,3 @@
+---
+prelude: >
+    Qiskit 2.1.1 is a small patch release, fixing several bugs found in the 2.1 series.