Tag 2.5.0 release

CHANGELOG.md

@@ -4,39 +4,36 @@ This list is not comprehensive, and only lists new features and major changes,
 but not every minor bugfix. The goatcounter.com service generally runs the
 latest master.
 
-Unreleased v2.5.0
+2023-12-10 v2.5.0
 -----------------
 This release requires Go 1.21.
 
 Features:
 
-- Quite a few tables are rewritten to a more efficient format. For
-  small-to-medium instances this will take a few minutes at the most, but if you
-  have very large instances this may take a few hours. It also requires enough
-  free disk space to rewrite the `hits` table.
+- Quite a few tables are rewritten to a more efficient format. For small to
+  medium instances this will take a few minutes at the most, but if you have
+  very large instances this may take a few hours. It also requires enough free
+  disk space to rewrite the `hits` table.
 
-  If you want to run steps manually, then you can view the migratio with:
+  If you want to run steps manually then you can view the migration with:
 
       % goatcounter db migrate -show 2023-05-16-1-hits
 
   Or if you use PostgreSQL:
 
       % goatcounter db migrate -show -db postgresql+dbname=goatcounter 2023-05-16-1-hits
 
-- UA Client hints are now used to get the browser and system name (if present).
-
 - The `User-Agent` header is no longer stored; only the browser and system
   parsed out of there. It's pretty reliable, and especially mobile browser
-  User-Agents are ridiculously unique.
+  User-Agents are ridiculously unique. It was always stored only "in case the
+  detection got it horribly wrong", but this has never been needed.
 
-- Add `proxy` option in `serve -tls` flag –  to give a hint that a secure
+- Add `proxy` option in `serve -tls` flag,  to give a hint that a secure
   connection will be used, so we know what value to use for the cookie
   secure/samesite flags.
 
 - Add *experimental* "dark mode"; this needs to be enabled explicitly in the
-  user settings.
-
-  I need help to make this decent:
+  user settings. I need help to make this decent:
   https://github.com/arp242/goatcounter/issues/586#issuecomment-1287995673
 
 - Show difference of pageviews compared to previous period on the dashboard.

README.md

@@ -80,7 +80,7 @@ There are three ways:
 Running your own
 ----------------
 **Note this README is for the latest master and may be inaccurate for the latest
-released version; use the [`release-2.4`][latest] branch for the 2.4 README.**
+released version; use the [`release-2.5`][latest] branch for the 2.5 README.**
 
 The [release page][releases] has binaries for Linux amd64, arm, and arm64. These
 are statically compiled, contain everything you need, and should work in pretty
@@ -95,7 +95,7 @@ Generally speaking only the latest release is supported, although critical fixes
 (security, data loss, etc.) may get backported to previous releases.
 
 [releases]: https://github.com/arp242/goatcounter/releases
-[latest]: https://github.com/arp242/goatcounter/tree/release-2.4
+[latest]: https://github.com/arp242/goatcounter/tree/release-2.5
 
 ### Deploy scripts and such
 - ["StackScript" for Linode][stackscript]; Alpine Linux VPS; you can also use
@@ -125,12 +125,12 @@ Generally speaking only the latest release is supported, although critical fixes
 
 
 ### Building from source
-You need Go 1.19 or newer and a C compiler (for SQLite). If you compile it with
+You need Go 1.21 or newer and a C compiler (for SQLite). If you compile it with
 `CGO_ENABLED=0` you don't need a C compiler but can only use PostgreSQL.
 
 You can install from source to $GOBIN (`go env GOBIN`) with:
 
-    % git clone --branch=release-2.4 https://github.com/arp242/goatcounter.git
+    % git clone --branch=release-2.5 https://github.com/arp242/goatcounter.git
     % cd goatcounter
     % go build -ldflags="-X zgo.at/goatcounter/v2.Version=$(git log -n1 --format='%h_%cI')" ./cmd/goatcounter