Skip to content

Commit 95bdc9f

Browse files
committed
preparing for releasing v2.1.2
1 parent 70b5cc6 commit 95bdc9f

3 files changed

Lines changed: 9 additions & 5 deletions

File tree

CHANGELOG.md

Lines changed: 7 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -12,11 +12,15 @@ This file should adhere to [Keep a Changelog](https://keepachangelog.com/en/1.1.
1212

1313
Changelogs prior to v1.2 follows other formats and are available in the v1.2-release.
1414

15-
This project should adhere to [Semantic Versioning](https://semver.org/spec/v2.0.0.html), though some earlier releases may be incompatible with the SemVer standard. Also, the niquest/request hack in 2.x.xx vs 2.x.9xx is
15+
This project should adhere to [Semantic Versioning](https://semver.org/spec/v2.0.0.html), though some earlier releases may be incompatible with the SemVer standard.
1616

17-
## [2.1.1] - [2025-11-09]
17+
## [2.1.2] - [2025-11-08]
1818

19-
Version 2.1.0 comes without niquests in the dependency file. Version 2.1.1 comes with niquests in the dependency file. See above.
19+
Version 2.1.0 comes without niquests in the dependency file. Version 2.1.2 come with niquests in the dependency file. Also fixed up some minor mistakes in the CHANGELOG.
20+
21+
## [2.1.1] - [2025-11-08] [YANKED]
22+
23+
Version 2.1.0 comes without niquests in the dependency file. Version 2.1.1 should come with niquests in the dependency file, but I made a mistake.
2024

2125
## [2.1.0] - [2025-11-08]
2226

RELEASE-HOWTO.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -17,7 +17,7 @@ I have no clue on the proper procedures for doing releases, and I keep on doing
1717
* Any changes done, go back to the start of this list
1818
* Write up some release notes. (I typically keep a short summary of the changes in the CHANGELOG, and use that as the release notes).
1919
* Verify that we're on the right branch - `git checkout master`. (`master` may not always be right - sometimes we may want to use a dedicated branch connected to the release-series, i.e. `v1.3`)
20-
* Set the variable `VERSION=1.4.0`
20+
* Set the variable `VERSION=2.2.0`
2121
* Commit the changes (typically `CHANGELOG.md`, perhaps documentation): `git commit -am "preparing for releasing v${VERSION}"`
2222
* Create a tag: `git tag -as v${VERSION}` - use the release notes in the tag message. Don't push it yet.
2323
* Make a clone: `git clone caldav/ caldav-release ; cd caldav-release ; git checkout v${VERSION}`

pyproject.toml

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -32,7 +32,7 @@ classifiers = [
3232

3333
dependencies = [
3434
"lxml",
35-
#"niquests",
35+
"niquests",
3636
"recurring-ical-events>=2.0.0",
3737
"typing_extensions;python_version<'3.11'",
3838
"icalendar>6.0.0"

0 commit comments

Comments
 (0)