Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Bump version: v5.5.0 #259

Merged
merged 1 commit into from
Sep 12, 2024
Merged

Bump version: v5.5.0 #259

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions docs/advanced_concepts.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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:
Expand Down Expand Up @@ -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.
2 changes: 1 addition & 1 deletion docs/task_headers_payloads.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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.
Expand Down
2 changes: 1 addition & 1 deletion karton/core/__version__.py
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1 +1 @@
__version__ = "5.4.0"
__version__ = "5.5.0"
Loading