Release aftermath.

CHANGES.md

@@ -1,5 +1,9 @@
 # Change log
 
-## 0.9 (unreleased)
+## 1.0 (unreleased)
+
+- Nothing changed, yet.
+
+## 0.9 (2024-01-19)
 
 - initial release

README.md

@@ -1,9 +1,10 @@
 # vereqsyn
 
+[![Test](https://github.com/minddistrict/vereqsyn/actions/workflows/tests.yml/badge.svg)](https://github.com/minddistrict/vereqsyn/actions/workflows/tests.yml)
 [![PyPI - Version](https://img.shields.io/pypi/v/vereqsyn.svg)](https://pypi.org/project/vereqsyn)
 [![PyPI - Python Version](https://img.shields.io/pypi/pyversions/vereqsyn.svg)](https://pypi.org/project/vereqsyn)
 
-Bi-directional version.cfg <–> requirements.txt synchronization
+Bi-directional versions.cfg <–> requirements.txt synchronization
 
 This program can be used to synchronize a `versions.cfg` used by
 [zc.buildout](https://pypi.org/project/zc.buildout/) with a `requirements.txt`
@@ -37,8 +38,8 @@ vereqsyn versions.cfg requirements.txt
 
 ## Constraints
 
-* `version.cfg` is the source of truth. `requirements.txt` can get recreated.
-* So `version.cfg` can contain comments, the ones in `requirements.txt` are
+* `versions.cfg` is the source of truth. `requirements.txt` can get recreated.
+* So `versions.cfg` can contain comments, the ones in `requirements.txt` are
   lost when running recreate.
 
 ## Hacking

src/vereqsyn/__about__.py

@@ -1,4 +1,4 @@
 # SPDX-FileCopyrightText: 2024-present Michael Howitz <[email protected]>
 #
 # SPDX-License-Identifier: MIT
-__version__ = "0.9"
+__version__ = "1.0"