[taler-challenger] branch master updated: -version bump

[gnunet]

This is an automated email from the git hooks/post-receive script.

grothoff pushed a commit to branch master
in repository challenger.

The following commit(s) were added to refs/heads/master by this push:
     new 5622568  -version bump
5622568 is described below

commit 5622568db82a926b52bc8d75b572c2e2584e10f6
Author: Christian Grothoff <christian@grothoff.org>
AuthorDate: Fri Dec 13 23:14:06 2024 +0100

    -version bump
---
 configure.ac                | 2 +-
 debian/changelog            | 6 ++++++
 doc/doxygen/challenger.doxy | 2 +-
 3 files changed, 8 insertions(+), 2 deletions(-)

diff --git a/configure.ac b/configure.ac
index 92302c8..22313e5 100644
--- a/configure.ac
+++ b/configure.ac
@@ -4,7 +4,7 @@
 # This configure file is in the public domain
 
 AC_PREREQ([2.69])
-AC_INIT([challenger],[0.14.0],[taler-bug@gnu.org])
+AC_INIT([challenger],[0.14.1],[taler-bug@gnu.org])
 AC_CONFIG_SRCDIR([src/challenger/challenger-httpd.c])
 AC_CONFIG_HEADERS([challenger_config.h])
 # support for non-recursive builds
diff --git a/debian/changelog b/debian/changelog
index 1212690..f351d15 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,9 @@
+challenger (0.14.1) unstable; urgency=low
+
+  * Release 0.14.1
+
+ -- Christian Grothoff <grothoff@gnu.org>  Fri, 13 Dec 2024 23:50:47 +0200
+
 challenger (0.14.0) unstable; urgency=low
 
   * Release 0.14.0
diff --git a/doc/doxygen/challenger.doxy b/doc/doxygen/challenger.doxy
index c70b64e..9603b33 100644
--- a/doc/doxygen/challenger.doxy
+++ b/doc/doxygen/challenger.doxy
@@ -38,7 +38,7 @@ PROJECT_NAME           = "GNU Taler: Challenger"
 # could be handy for archiving the generated documentation or if some version
 # control system is used.
 
-PROJECT_NUMBER         = 0.14.0
+PROJECT_NUMBER         = 0.14.1
 
 # Using the PROJECT_BRIEF tag one can provide an optional one line description
 # for a project that appears at the top of each page and should give viewer a

-- 
To stop receiving notification emails like this one, please contact
gnunet@gnunet.org.