]> git.ipfire.org Git - thirdparty/dnspython.git/commitdiff
2.6.0 prep
authorBob Halley <halley@dnspython.org>
Fri, 9 Feb 2024 21:45:58 +0000 (13:45 -0800)
committerBob Halley <halley@dnspython.org>
Fri, 9 Feb 2024 21:45:58 +0000 (13:45 -0800)
.github/workflows/python-package.yml
README.md
dns/version.py
doc/conf.py
doc/whatsnew.rst

index 0a0670adf6c81cbb83ff496da4ae77a9cc8edd83..70be4158943add2a211db75b27b9316019fcf62d 100644 (file)
@@ -7,6 +7,7 @@ on:
   push:
     branches:
       - master
+      - 2.6
     paths:
       - '**.py'
   pull_request:
index 3a942955ee5a0e24a5c1f5854fa6f7f8b0b491e7..6e44880e18f4cca445d9773d74706f16487012a8 100644 (file)
--- a/README.md
+++ b/README.md
@@ -30,7 +30,7 @@ to facilitate the testing of DNS software.
 
 ## ABOUT THIS RELEASE
 
-This is the development version of dnspython 2.6.0.
+This is the development version of dnspython 2.7.0.
 Please read
 [What's New](https://dnspython.readthedocs.io/en/latest/whatsnew.html) for
 information about the changes in this release.
index 658cca2888f84968b0094cc6ff84bf6c86e33a67..7d3afb596d30ab633fe94fc95e5dd1456db85b31 100644 (file)
@@ -20,7 +20,7 @@
 #: MAJOR
 MAJOR = 2
 #: MINOR
-MINOR = 6
+MINOR = 7
 #: MICRO
 MICRO = 0
 #: RELEASELEVEL
index d62f885331569f5d295119bfa261f0e210cf4480..35b410b38b9e5cd3b0ca9808d39002857a7ff2e5 100644 (file)
@@ -61,9 +61,9 @@ author = "Dnspython Contributors"
 # built documents.
 #
 # The short X.Y version.
-version = "2.6"
+version = "2.7"
 # The full version, including alpha/beta/rc tags.
-release = "2.6.0"
+release = "2.7.0"
 
 # The language for content autogenerated by Sphinx. Refer to documentation
 # for a list of supported languages.
index 23a29e438fc7e70c974fcd660f0174f245b0b5c7..e588d5ce385df23e353816ebf96342659f116031 100644 (file)
@@ -3,9 +3,14 @@
 What's New in dnspython
 =======================
 
-2.6.0 (in development)
+2.7.0 (in development)
 ----------------------
 
+* TBD
+
+2.6.0
+-----
+
 * As mentioned in the "TuDoor" paper and the associated CVE-2023-29483, the dnspython
   stub resolver is vulnerable to a potential DoS if a bad-in-some-way response from the
   right address and port forged by an attacker arrives before a legitimate one on the