Now depends on kombu 3.0.14

Changelog

@@ -17,10 +17,30 @@ new in Celery 3.1.
 
 - **Requirements**:
 
-    - Now depends on :ref:`Kombu 3.0.13 <kombu:version-3.0.13>`.
+    - Now depends on :ref:`Kombu 3.0.14 <kombu:version-3.0.14>`.
 
-- **Beat**: No longer attempts to upgrade a newly created database file
-  (Issue #1923).
+- **Redis:** Important note about events (Issue #1882).
+
+    There is a new transport option for Redis that enables monitors
+    to filter out unwanted events.  Enabling this option in the workers
+    will increase performance considerably:
+
+    .. code-block:: python
+
+        BROKER_TRANSPORT_OPTIONS = {'fanout_patterns': True}
+
+    Enabling this option means that your workers will not be able to see
+    workers with the option disabled (or is running an older version of
+    Celery), so if you do enable it then make sure you do so on all
+    nodes.
+
+    See :ref:`redis-caveats-fanout-patterns`.
+
+    This will be the default in Celery 3.2.
+
+- **Results**: 
+
+    Max cached results default decreased to 100.
 
 - **Events**: The "Substantial drift" warning message is now logged once
   per node name only (Issue #1802).
@@ -31,6 +51,23 @@ new in Celery 3.1.
     This can be enabled by using the new ``%i`` and ``%I`` format specifiers
     for the log file name.  See :ref:`worker-files-process-index`.
 
+- **Multi**: With ``-opt:index`` (e.g. ``-c:1``) the index now always refers
+  to the position of a node in the argument list.
+
+    This means that referring to a number will work when specifying a list
+    of node names and not just for a number range:
+
+    .. code-block:: bash
+
+        celery multi start A B C D -c:1 4 -c:2-4 8
+
+    In this example ``1`` refers to node A (as it's the first node in the
+    list).
+
+- **Signals**: The sender argument to ``Signal.connect`` can now be a proxy
+  object, which means that it can be used with the task decorator
+  (Issue #1873).
+
 - **Task**: A regression caused the ``queue`` argument to ``Task.retry`` to be
   ignored (Issue #1892).
 
@@ -42,12 +79,36 @@ new in Celery 3.1.
   even if one of the tasks in the chain is ``ignore_result=True``
   (Issue #1905).
 
+- **Canvas**: A chord task raising an exception will now result in
+  any errbacks (``link_error``) to the chord callback to also be called.
+
+- **Task**: Task callbacks and errbacks are now called using the group
+  primitive.
+
+- **Task**: ``Task.apply`` now properly sets ``request.headers``
+  (Issue #1874).
+
+- **Beat**: No longer attempts to upgrade a newly created database file
+  (Issue #1923).
+
+- **Beat**: New setting :setting:``CELERYBEAT_SYNC_EVERY`` can be be used
+  to control file sync by specifying the number of tasks to send between
+  each sync.
+
+    Contributed by Chris Clark.
+
 - **Canvas**: Chords can now be combined when using the amqp result backend
   (a chord where the callback is also a chord).
 
 - **Commands**: :program:`celery inspect memdump` no longer crashes
   if the :mod:`psutil` module is not installed (Issue #1914).
 
+- **Worker**: Remote control commands now always accepts json serialized
+  messages (Issue #1870).
+
+- **Worker**: Gossip will now drop any task related events it receives
+  by mistake (Issue #1882).
+
 
 .. _version-3.1.9:
 

requirements/default.txt

@@ -1,3 +1,3 @@
 pytz>dev
 billiard>=3.3.0.14,<3.4
-kombu>=3.0.13,<4.0
+kombu>=3.0.14,<4.0

setup.cfg

@@ -12,4 +12,4 @@ upload-dir = docs/.build/html
 [bdist_rpm]
 requires = pytz >= 2011b
            billiard >= 3.3.0.14
-           kombu >= 3.0.13
+           kombu >= 3.0.14