Release ritual for Tabula 1.2.1

tabulapdf · May 22, 2018 · 9849c4f · 9849c4f
1 parent 3b1f4d0
commit 9849c4f
Show file tree

Hide file tree

Showing 2 changed files with 2 additions and 2 deletions.
diff --git a/build.xml b/build.xml
@@ -5,7 +5,7 @@
   <property name="build.dir" value="build"/>
   <property name="mac.dir" value="${build.dir}/mac" />
   <property name="windows.dir" value="${build.dir}/windows" />
-  <property name="full_version" value="1.2.0.18022700"/>
+  <property name="full_version" value="1.2.1.18052200"/>
   <property name="launch4j.dir" location="${build.dir}/../launch4j"  />
   <property name="launch4j.bindir" location="${build.dir}/../launch4j/bin" />
 

diff --git a/webapp/static/js/tabula.js b/webapp/static/js/tabula.js
@@ -3,7 +3,7 @@ window.Tabula = Tabula || {};
 $.ajaxSetup({ cache: false }); // fixes a dumb issue where Internet Explorer caches Ajax requests. See https://github.com/tabulapdf/tabula/issues/408
 var base_uri = $('base').attr("href");
 
-Tabula.UI_VERSION = "1.2.0-2018-02-27"; // when we make releases, we should remember to up this.
+Tabula.UI_VERSION = "1.2.1-2018-05-22"; // when we make releases, we should remember to up this.
 // Add '-pre' to the end of this for a prerelease version; this will let
 // our "new version" check give you that channel.