diff --git a/croniter-0.3.34.tar.gz b/croniter-0.3.34.tar.gz
deleted file mode 100644
index cc427b6..0000000
--- a/croniter-0.3.34.tar.gz
+++ /dev/null
@@ -1,3 +0,0 @@
-version https://git-lfs.github.com/spec/v1
-oid sha256:7186b9b464f45cf3d3c83a18bc2344cc101d7b9fd35a05f2878437b14967e964
-size 25508
diff --git a/croniter-0.3.36.tar.gz b/croniter-0.3.36.tar.gz
new file mode 100644
index 0000000..ad7843a
--- /dev/null
+++ b/croniter-0.3.36.tar.gz
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:9d3098e50f7edc7480470455d42f09c501fa1bb7e2fc113526ec6e90b068f32c
+size 29539
diff --git a/python-croniter.changes b/python-croniter.changes
index 63bce9c..69df282 100644
--- a/python-croniter.changes
+++ b/python-croniter.changes
@@ -1,3 +1,15 @@
+-------------------------------------------------------------------
+Thu Nov 26 09:22:47 UTC 2020 - Dirk Mueller <dmueller@suse.com>
+
+- update to 0.3.36:
+- Updated docs section regarding ``max_years_between_matches`` to be more shorter and hopefully more relevant.
+- Add a new initialization parameter ``max_years_between_matches`` to support finding the next/previous date beyond the default 1 year window, if so desired.  Updated README to include additional notes and example of this usage.  Fixes #145.
+- The ``croniter_range()`` function was updated to automatically determines the appropriate ``max_years_between_matches`` value, this preventing handling of the ``CroniterBadDateError`` exception.
+- Updated exception handling classes:  ``CroniterBadDateError`` now only
+  applies during date finding operations (next/prev), and all parsing errors can now be caught using ``CroniterBadCronError``.  The ``CroniterNotAlphaError`` exception is now a subclass of ``CroniterBadCronError``.  A brief description of each exception class was added as an inline docstring.
+- Updated iterable interfaces to replace the ``CroniterBadDateError`` with ``StopIteration`` if (and only if) the ``max_years_between_matches`` argument is provided.  The rationale here is that if the user has specified the max tolerance between matches, then there's no need to further inform them of no additional matches.  Just stop the iteration.  This also keeps backwards compatibility.
+- Minor docs update
+
 -------------------------------------------------------------------
 Fri Jul 17 07:25:05 UTC 2020 - Dirk Mueller <dmueller@suse.com>
 
diff --git a/python-croniter.spec b/python-croniter.spec
index 77320e3..1f3183a 100644
--- a/python-croniter.spec
+++ b/python-croniter.spec
@@ -18,7 +18,7 @@
 
 %{?!python_module:%define python_module() python-%{**} python3-%{**}}
 Name:           python-croniter
-Version:        0.3.34
+Version:        0.3.36
 Release:        0
 Summary:        Python iterators for datetime objects with cron-like format
 License:        MIT