diff --git a/PKG-INFO b/PKG-INFO
index cb6e42f..70bb0b2 100644
--- a/PKG-INFO
+++ b/PKG-INFO
@@ -1,65 +1,65 @@
 Metadata-Version: 2.1
 Name: swh.scheduler
-Version: 0.0.33
+Version: 0.0.34
 Summary: Software Heritage Scheduler
 Home-page: https://forge.softwareheritage.org/diffusion/DSCH/
 Author: Software Heritage developers
 Author-email: swh-devel@inria.fr
 License: UNKNOWN
 Project-URL: Bug Reports, https://forge.softwareheritage.org/maniphest
 Project-URL: Funding, https://www.softwareheritage.org/donate
 Project-URL: Source, https://forge.softwareheritage.org/source/swh-scheduler
 Description: swh-scheduler
         =============
         
         Job scheduler for the Software Heritage project.
         
         Task manager for asynchronous/delayed tasks, used for both recurrent (e.g.,
         listing a forge, loading new stuff from a Git repository) and one-off
         activities (e.g., loading a specific version of a source package).
         
         
         # Tests
         
         ## Running test manually
         
         ### Test data
         
         To be able to run (unit) tests, you need to have the
         [[https://forge.softwareheritage.org/source/swh-storage-testdata.git|swh-storage-testdata]]
         in the parent directory. If you have set your environment following the
         [[ https://docs.softwareheritage.org/devel/getting-started.html#getting-started|Getting started]]
         document everythong should be set up just fine.
         
         Otherwise:
         
         ```
         ~/.../swh-scheduler$ git clone https://forge.softwareheritage.org/source/swh-storage-testdata.git ../swh-storage-testdata
         ```
         
         ### Required services
         
         Unit tests that require a running celery broker uses an in memory broker/result
         backend by default, but you can choose to use a true broker by setting
         `CELERY_BROKER_URL` and `CELERY_RESULT_BACKEND` environment variables up.
         
         For example:
         
         ```
         $ CELERY_BROKER_URL=amqp://localhost pifpaf run postgresql nosetests
         
         .....................................
         ----------------------------------------------------------------------
         Ran 37 tests in 15.578s
         
         OK
         ```
         
 Platform: UNKNOWN
 Classifier: Programming Language :: Python :: 3
 Classifier: Intended Audience :: Developers
 Classifier: License :: OSI Approved :: GNU General Public License v3 (GPLv3)
 Classifier: Operating System :: OS Independent
 Classifier: Development Status :: 5 - Production/Stable
 Description-Content-Type: text/markdown
 Provides-Extra: testing
diff --git a/swh.scheduler.egg-info/PKG-INFO b/swh.scheduler.egg-info/PKG-INFO
index cb6e42f..70bb0b2 100644
--- a/swh.scheduler.egg-info/PKG-INFO
+++ b/swh.scheduler.egg-info/PKG-INFO
@@ -1,65 +1,65 @@
 Metadata-Version: 2.1
 Name: swh.scheduler
-Version: 0.0.33
+Version: 0.0.34
 Summary: Software Heritage Scheduler
 Home-page: https://forge.softwareheritage.org/diffusion/DSCH/
 Author: Software Heritage developers
 Author-email: swh-devel@inria.fr
 License: UNKNOWN
 Project-URL: Bug Reports, https://forge.softwareheritage.org/maniphest
 Project-URL: Funding, https://www.softwareheritage.org/donate
 Project-URL: Source, https://forge.softwareheritage.org/source/swh-scheduler
 Description: swh-scheduler
         =============
         
         Job scheduler for the Software Heritage project.
         
         Task manager for asynchronous/delayed tasks, used for both recurrent (e.g.,
         listing a forge, loading new stuff from a Git repository) and one-off
         activities (e.g., loading a specific version of a source package).
         
         
         # Tests
         
         ## Running test manually
         
         ### Test data
         
         To be able to run (unit) tests, you need to have the
         [[https://forge.softwareheritage.org/source/swh-storage-testdata.git|swh-storage-testdata]]
         in the parent directory. If you have set your environment following the
         [[ https://docs.softwareheritage.org/devel/getting-started.html#getting-started|Getting started]]
         document everythong should be set up just fine.
         
         Otherwise:
         
         ```
         ~/.../swh-scheduler$ git clone https://forge.softwareheritage.org/source/swh-storage-testdata.git ../swh-storage-testdata
         ```
         
         ### Required services
         
         Unit tests that require a running celery broker uses an in memory broker/result
         backend by default, but you can choose to use a true broker by setting
         `CELERY_BROKER_URL` and `CELERY_RESULT_BACKEND` environment variables up.
         
         For example:
         
         ```
         $ CELERY_BROKER_URL=amqp://localhost pifpaf run postgresql nosetests
         
         .....................................
         ----------------------------------------------------------------------
         Ran 37 tests in 15.578s
         
         OK
         ```
         
 Platform: UNKNOWN
 Classifier: Programming Language :: Python :: 3
 Classifier: Intended Audience :: Developers
 Classifier: License :: OSI Approved :: GNU General Public License v3 (GPLv3)
 Classifier: Operating System :: OS Independent
 Classifier: Development Status :: 5 - Production/Stable
 Description-Content-Type: text/markdown
 Provides-Extra: testing
diff --git a/version.txt b/version.txt
index ce82f77..5b8e11d 100644
--- a/version.txt
+++ b/version.txt
@@ -1 +1 @@
-v0.0.33-0-g923e0b5
\ No newline at end of file
+v0.0.34-0-gf326cef
\ No newline at end of file