Bump version: v5.5.0 (#259)

CERT-Polska · Sep 12, 2024 · a80712c · a80712c
1 parent 89a885d
commit a80712c
Show file tree

Hide file tree

Showing 3 changed files with 4 additions and 4 deletions.
diff --git a/docs/advanced_concepts.rst b/docs/advanced_concepts.rst
@@ -251,7 +251,7 @@ You can enable it by setting:
 Negated filter patterns
 -----------------------
 
-.. versionadded:: 5.4.1
+.. versionadded:: 5.5.0
 
 There is one more pattern syntax, not documented in the :code:`Filter Patterns` section anymore.
 It is possible to define a negated filter, and they are handled in a special way. For example let's consider following filters:
@@ -316,6 +316,6 @@ In this case there are no special cases, and matching checks every filter top to
 
 .. note::
 
-    Since "new style" patterns were introduced in Karton version 5.4.1, "old style" negations are not recommended and should be considered deprecated.
+    Since "new style" patterns were introduced in Karton version 5.5.0, "old style" negations are not recommended and should be considered deprecated.
 
     Nevertheless, Karton still supports them and they will keep working indefinitely. So don't worry, there are no breaking changes here.
diff --git a/docs/task_headers_payloads.rst b/docs/task_headers_payloads.rst
@@ -104,7 +104,7 @@ Filter logic can be used to fulfill specific use-cases:
 ``[{"foo": "bar"}, {"foo": "baz"}]``  'foo' header is required and must have 'bar' or 'baz' value.
 ====================================  ==============================================================================
 
-.. versionadded:: 5.4.1
+.. versionadded:: 5.5.0
 
 Sometimes a more flexible behavior is necessary. This should be done with caution, as Karton can handle quite complex
 workflows without resorting to this. The need to use complex task filtering rules may mean that one is doing something not in the "spirit" of Karton.

diff --git a/karton/core/__version__.py b/karton/core/__version__.py
@@ -1 +1 @@
-__version__ = "5.4.0"
+__version__ = "5.5.0"