Publish a new release to prod #146
Labels
No labels
No milestone
No project
No assignees
2 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
Grandiras/Ponente#146
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
🤖 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.
v2.5.0 is live on ponente.app.
What shipped
20 commits since
v2.4.0, seven member-visible bullets — features, so a minor bump:/profile(your Atmosphere name and picture), moving a card to another board, "Report a problem", asking for access from the sign-in page, the phone nav moving to the bottom of the screen, the Ponente wordmark returning you to the board you were on, and a round of tidy-ups. No migrations in this range.What I did
check-stack-image.sh, so I used a public equivalent:dev.ponente.app/client-metadata.jsonservedscope: atproto repo:app.bsky.actor.profile blob:image/*, which only the newProfileScopecode produces. Prod at that moment still served bareatproto. Both healthy.FEEDBACK_REPOSITORY/FEEDBACK_TOKEN,ATPROTO_PROFILE_SCOPE, and the wholeBACKUP_*set. Checked the new image starts on prod's existing compose file — both new settings are optional, and unsetATPROTO_PROFILE_SCOPEmeansgranularin code, so/profileworks on the tag alone.dotnet build -c Releaseclean,dotnet test389/389 passing. The e2e suite I could not run — this container has no podman or docker, so there is no compose stack to point Playwright at. CI (build) was green on every merge in the range and on the changelog PR.main(a753bcc). Branch deleted; nothing left for the workflow to open.v2.5.0on the merge commit.build-and-push(run 1064) succeeded and:latestmoved with it —v2.5.0andlatestare bothsha256:c1148bb9….ponente-apprecreated, then/healthzok andponente.app/client-metadata.jsonnow serves the granular scope — the same marker that proved dev, so this is the new image and not a cached page./,/login,/requestall 200 with the right titles;/calendarcorrectly bounces to sign-in; the PDS health endpoint is 200.What is left, and it needs a human
Production is missing this release's compose and env changes. The auto-update timer recreates only the app container, from the compose file the server already holds — only
./deploy/deploy.shre-syncs it, and there is no route from this job container to the server. Two consequences:FEEDBACK_REPOSITORYandFEEDBACK_TOKENindeploy/.envplus the passthrough this batch added todocker-compose.prod.yml. Nothing breaks meanwhile — the menu row hides itself rather than swallowing what somebody typed.deploy/backup/and theponente-backup@units are new in 2.5.0 and are installed bydeploy.sh, not by the timer.Production is not pinned —
IMAGE_TAGuntouched, so the next release deploys itself as usual. I filed thedeploy.shfollow-up as its own issue rather than leaving it here.⏱ 16m 41s · 42 turns · tokens: 64.3k in / 16.5k out (+2424.2k cache-read)
📜 Full session transcript
→ Filed follow-up issue #148: Run deploy.sh: production is missing the 2.5.0 compose and env changes (Report a problem, backups)