Grandiras/Ponente

Fork 0

Release a new patch for the scrolling issue #152

New issue

Closed

opened 2026-08-23 14:55:58 +00:00 by Grandiras · 2 comments

Grandiras commented

2026-08-23 14:55:58 +00:00

Owner

No description provided.

claude-bot was assigned by Grandiras

2026-08-23 14:59:11 +00:00

claude-bot commented

2026-08-23 14:59:16 +00:00

Collaborator

🤖 On it — follow along in the action run; the reply will link the full session transcript.

📜 Live transcript — updating every ~5 minutes while the task runs.

🤖 On it — follow along in [the action run](https://git.grandiras.net/Grandiras/claude-bot/actions/runs/378); the reply will link the full session transcript.  📜 [Live transcript](https://git.grandiras.net/Grandiras/claude-bot/src/branch/claude-logs/transcripts/Grandiras/Ponente/issue-152/run-378.md) — updating every ~5 minutes while the task runs.

claude-bot referenced this issue

2026-08-23 15:00:32 +00:00

Changelog for 2.5.1 #153

claude-bot commented

2026-08-23 15:12:37 +00:00

Collaborator

v2.5.1 is live on ponente.app.

The scrolling fix was already merged (PR #151 for #150) and sitting in Changelog.Unreleased; this run turned it into a release.

What I did

Checked what landed since v2.5.0 — three commits: the phone column-scroll fix, a deploy/backups doc update, and now the changelog. The diff of docker-compose*.yml, deploy/.env*.example, deploy/docker-compose.prod.yml and appsettings.json across that range is empty, so there are no new env keys and nothing a human had to add to deploy/.env before this tag was safe to cut. (I can't run check-env-keys.sh from a job container — deploy/.env isn't here — so I checked it the way the runbook says to when dispatched from an issue: from the config diff.)
Promoted the changelog with promote-changelog.py 2.5.1. One bullet, a fix only → patch, which matches what the issue asked for. Landed as PR #153 ("Changelog for 2.5.1") on release/v2.5.1; CI green; merged as 016f14d, branch deleted.
Tagged v2.5.1 on that merge commit and pushed it.

What I verified

dotnet test Ponente.sln — 389 passed, 0 failed (includes DocumentationTests).
CI on the PR: build green. On the tag: build-and-push run 1079, sha 016f14d, success.

Registry — :latest moved to the new image, which is the thing production follows:

v2.5.1   sha256:e50c3578…f28a7018
latest   sha256:e50c3578…f28a7018   ← same digest
v2.5.0   sha256:c1148bb9…c491b495

The host picked it up: https://ponente.app/healthz → ok, and production is now serving the fixed assets — app.css contains the .card-chosen:not(.card-ghost) lift rule and js/sortable-interop.js contains DRAG_PRESS_MS, neither of which existed in v2.5.0. A nonsense control selector matches 0 times, so the grep is actually discriminating. / redirects to the login page and it renders (200).
Production was not pinned — it deployed on its own within the minute, which is what a working IMAGE_TAG=latest looks like. I changed nothing in deploy/.env.

Caveats

I did not run the Playwright e2e suite: it needs the local compose stack, and this job container has no container runtime. The fix's own e2e coverage (the additions to board.spec.js and mobile.spec.js in PR #151) ran on that PR's CI before it merged.
The fix itself is a touch gesture, so there is nothing useful to screenshot — no image attached.
No PR was opened by the workflow for this run; a release lands its change through its own PR, which is already merged. /tmp/no-pr.txt records that.

⏱ 13m 7s · 29 turns · tokens: 41.1k in / 7.7k out (+940.3k cache-read)
📜 Full session transcript

**v2.5.1 is live on ponente.app.** The scrolling fix was already merged (PR #151 for #150) and sitting in `Changelog.Unreleased`; this run turned it into a release. **What I did** 1. **Checked what landed since v2.5.0** — three commits: the phone column-scroll fix, a deploy/backups doc update, and now the changelog. The diff of `docker-compose*.yml`, `deploy/.env*.example`, `deploy/docker-compose.prod.yml` and `appsettings.json` across that range is **empty**, so there are no new env keys and nothing a human had to add to `deploy/.env` before this tag was safe to cut. (I can't run `check-env-keys.sh` from a job container — `deploy/.env` isn't here — so I checked it the way the runbook says to when dispatched from an issue: from the config diff.) 2. **Promoted the changelog** with `promote-changelog.py 2.5.1`. One bullet, a fix only → patch, which matches what the issue asked for. Landed as PR [#153](https://git.grandiras.net/Grandiras/Ponente/pulls/153) ("Changelog for 2.5.1") on `release/v2.5.1`; CI green; merged as `016f14d`, branch deleted. 3. **Tagged `v2.5.1`** on that merge commit and pushed it. **What I verified** - `dotnet test Ponente.sln` — **389 passed, 0 failed** (includes `DocumentationTests`). - CI on the PR: `build` green. On the tag: `build-and-push` run 1079, sha `016f14d`, **success**. - Registry — `:latest` moved to the new image, which is the thing production follows: ``` v2.5.1 sha256:e50c3578…f28a7018 latest sha256:e50c3578…f28a7018 ← same digest v2.5.0 sha256:c1148bb9…c491b495 ``` - The host picked it up: `https://ponente.app/healthz` → `ok`, and production is now **serving the fixed assets** — `app.css` contains the `.card-chosen:not(.card-ghost)` lift rule and `js/sortable-interop.js` contains `DRAG_PRESS_MS`, neither of which existed in v2.5.0. A nonsense control selector matches 0 times, so the grep is actually discriminating. `/` redirects to the login page and it renders (200). - Production was **not pinned** — it deployed on its own within the minute, which is what a working `IMAGE_TAG=latest` looks like. I changed nothing in `deploy/.env`. **Caveats** - I did not run the Playwright e2e suite: it needs the local compose stack, and this job container has no container runtime. The fix's own e2e coverage (the additions to `board.spec.js` and `mobile.spec.js` in PR #151) ran on that PR's CI before it merged. - The fix itself is a touch gesture, so there is nothing useful to screenshot — no image attached. - No PR was opened by the workflow for this run; a release lands its change through its own PR, which is already merged. `/tmp/no-pr.txt` records that. --- ⏱ 13m 7s · 29 turns · tokens: 41.1k in / 7.7k out (+940.3k cache-read) 📜 [Full session transcript](https://git.grandiras.net/Grandiras/claude-bot/src/branch/claude-logs/transcripts/Grandiras/Ponente/issue-152/run-378.md)

Grandiras closed this issue

2026-08-23 15:14:01 +00:00

No labels

No milestone

No project

No assignees

2 participants

Notifications

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference

Grandiras/Ponente#152

No description provided.

Rows
Columns