From 509232d68b98f07876eb921b56ac3b2d68a47f16 Mon Sep 17 00:00:00 2001
From: Egor Tensin <egor@tensin.name>
Date: Wed, 14 Oct 2026 14:26:09 +0500
Subject: add CHANGELOG.md

---
 CHANGELOG.md   | 56 ++++++++++++++++++++++++++++++++++++++++++++++++++++++++
 DEVELOPMENT.md |  5 +++--
 2 files changed, 59 insertions(+), 2 deletions(-)
 create mode 100644 CHANGELOG.md

diff --git a/CHANGELOG.md b/CHANGELOG.md
new file mode 100644
index 0000000..93b78e5
--- /dev/null
+++ b/CHANGELOG.md
@@ -0,0 +1,56 @@
+v8.0
+====
+
+### Breaking changes
+
+* Since Bitbucket deprecated "app passwords", an Atlassian API token is now
+required in place of those.
+    * In cgitize.toml, the field `bitbucket.username` is replaced with
+`bitbucket.email`, since the API tokens are tied to the Atlassian account now.
+
+v7.0
+====
+
+### Breaking changes
+
+* For forge users, only publicly visible repositories are fetched by default.
+    * New fields in cgitize.toml `{github,bitbucket,gitlab}.users.*.{public,private}`
+control whether to fetch public or private repositories, or both.
+    * The `public` field is set to `true` by default; `private` is `false`.
+
+v6.0
+====
+
+* Major version bumps for the dependencies.
+* Otherwise, no breaking changes.
+
+v5.0
+====
+
+### Breaking changes
+
+* GitHub: private user repositories are also cloned now.
+    * This change is consistent with how Gitlab and Bitbucket backend work.
+    * If `github.token` is set in cgitize.toml, `github.username` must also be
+set.
+
+v5.1
+----
+
+### New features
+
+* In case of an error, a message is displayed in the frontend's header.
+
+v4.0
+====
+
+### Breaking changes
+
+* Fields `access_token` & `app_password` in cgitize.toml renamed to simply
+`token`.
+* Repositories are cloned into directories with the ".git" suffix now.
+
+v3.0
+====
+
+* The latest release that I'm still not too lazy to look up.
diff --git a/DEVELOPMENT.md b/DEVELOPMENT.md
index 2802f63..34105e6 100644
--- a/DEVELOPMENT.md
+++ b/DEVELOPMENT.md
@@ -61,9 +61,10 @@ Upgrading dependencies
 Releases
 --------
 
-* Make a new tag using the semantic versioning policy (you can use [tag-release]
-to do that), review and push it.
 * For a new major version, update the version in the docker-compose definition
 in docker/README.md.
+* Update CHANGELOG.md if necessary.
+* Make a new tag using the semantic versioning policy (you can use [tag-release]
+to do that), review and push it.
 
 [tag-release]: https://github.com/egor-tensin/tag-release
-- 
cgit v1.3