build: prepare release 25.10.1

Author: alehander92

CHANGELOG.md

@@ -2,12 +2,23 @@
 
 All notable changes to this project will be documented in this file.
 
-## Unreleased
+## 25.10.1 - 2025-10-30
 
-- Documented that Python recordings now run through the db backend using the active interpreter, including CLI help and installation guidance for the `codetracer_python_recorder` package.
-- Added a Python getting-started guide covering recorder installation, `ct record`, and replay workflows.
-- `ct record` now verifies that `codetracer_python_recorder` is importable before launching the db backend and prints remediation hints when the module is missing or broken.
-- CI smoke test for the Python recorder validates metadata fields and exercises failure paths for missing interpreters or recorder modules.
+We are releasing our new version enabling support for Python recordings!
+
+They are based on our [codetracer-python-recorder](https://github.com/metacraft-labs/codetracer-python-recorder)
+and one needs to install it (e.g. with `pip install codetracer-python-recorder`) to be able to use `ct record <script.py>`
+
+One can read more in the [docbook section for Python](https://docs.codetracer.com/getting_started/python.html)
+
+There are also some bugfixes, and a lot of work on various other features which are still in development.
+
+Bugfixes:
+  - bugfix(ruby): Fix ruby output being on a single line (fix for one of the newer ruby recorders this time)
+  - bugfix(frontend): add uniform disabled style for future in both event log and terminal
+  - security fixes, cleanups and upgrades of packages
+Refactorings:
+  - refactor additional parts of our frontend/index code
 
 ## 25.09.2 - 2025-09-25(hotfix)
 

build-python/setup.cfg

@@ -1,6 +1,6 @@
 [metadata]
 name = codetracer
-version = 25.9.2
+version = 25.10.1
 description = Time-traveling debugger for polyglot codebases
 long_description = file: README.md
 long_description_content_type = text/markdown

release_checklist.md

@@ -5,6 +5,7 @@
 * Update version.nim with the new version, following [calendar versioning](https://calver.org/): `YY.OM.<build>`:
   e.g. the first build for a month can be `25.03.1`, the next one `25.03.2` etc
 * Update Info.plist with the new version following the same format.
+* Update build-python/setup.cfg with the new version following the same format.
 * Open a pull request with the changes
 * Check if CI builds and upload the artifacts correctly. Test the artifacts: if needed, one can
   fix/change things and push again

resources/Info.plist

@@ -24,9 +24,9 @@
     <string>APPL</string>
 
     <!-- CAUTION: DO NOT MOVE THE VALUE TO A NEW LINE!!! THIS NEEDS TO BE EDITABLE WITH SED! -->
-    <key>CFBundleShortVersionString</key><string>25.09.2</string>
+    <key>CFBundleShortVersionString</key><string>25.10.1</string>
 
-    <key>CFBundleVersion</key><string>25.09.2</string>
+    <key>CFBundleVersion</key><string>25.10.1</string>
 
     <key>DTCompiler</key>
     <string>com.apple.compilers.llvm.clang.1_0</string>

src/ct/version.nim

@@ -6,8 +6,8 @@ import strutils
 
 const
   CodeTracerYear* = 25
-  CodeTracerMonth* = 9
-  CodeTracerBuild* = 2
+  CodeTracerMonth* = 10
+  CodeTracerBuild* = 1
 
   CodeTracerVersionStr* = $CodeTracerYear & "." & ($CodeTracerMonth).align(2, '0') & "." & $CodeTracerBuild