Rollback: cut and document a dedicated pre-removal Blazor tag before deletion #205
Closed
opened 2026-07-09 21:21:46 +02:00 by timothy
·
3 comments
No Branch/Tag Specified
main
renovate/dotnet-monorepo
renovate/meziantou.analyzer-3.x
renovate/lucene.net
renovate/sqlitepclraw.bundle_e_sqlite3-3.x
renovate/cliwrap-3.x
913-scripted-playout-401
release/v26.15.0-notes
issue-806-guard-populations
scratch/767b-poisoned
scratch/767b-control
release/v26.14.0-notes
release/v26.14.0
docs/510-skill-logo-bug-policy
fix/510-watermark-resolution-policy
fix/629-verdict-classifier-falseopens
fix/609-decisions-edit-token-scope
issue-135-clear-to-none
release/v26.12.0-notes
fix/409b-lastscan-api-parity
fix/401-updatechannel-mirror-422
fix/327-playlist-rename-validation
fix/410-scancancel-log-level
fix/409-447-librariesscreen-neverscanned
fix/338-zap-exit-code
fix/367-plex-budget-message
fix/310-debom-legacy-cs
ci/604-lane-rebalance
feat/388-design-mirror
feat/247-test-ownership
feat/247-primary-action
feat/357-player-owned-playback
feat/357-jellyfin-plugin-poc
fix/289-mcp-hardening
issue58-mcp
feat/244-channels-extract
ci/auto-bump-prod-compose
feat/multi-rerun-collections-api
feat/collections-api
feat/quick-wins
feat/185-docs-part2
feat/140-collections-screen
feat/146-channel-edit
feat/147-classic-ui-link
issue22-renovate-dashboard
feat/91-cutover
feat/63-composite-create
feat/65-library-browse
feat/85-epg
feat/86-schedule-editor
feat/109-dashboard-data
feat/99-session-tracking
fix/dockerfile-node-tag
feat/59-spa-foundation
docs/59-ui-redesign-brief
feat/102-json-guide
feat/111-schedule-durations
feat/104-artwork-upload
feat/103-media-sources-api
feat/playouts-read-api
feat/108-health-api
feat/105-picker-list-endpoints
issue-97-channel-state-api
issue42-jellyfin-musicvideos
issue46-rest-api-error-contract
dependabot/nuget/ErsatzTV.FFmpeg.Tests/multi-d307a2e06f
qsv-improvements
hdr-vulkan-cuda-test
v26.16.0
v26.15.0
v26.14.0
v26.13.0
v26.12.0
v26.11.0
v26.10.0
v26.9.0
v26.8.0
v26.7.0
blazor-final
v26.6.0
v26.5.0
v26.4.0
v26.3.1
v26.3.0
v26.2.0
v26.1.1
v26.1.0
v25.9.0
v25.8.0
v25.7.1
v25.7.0
v25.6.0
v25.5.0
v25.4.0
v25.3.1
v25.3.0
v25.2.0
v25.1.0
v0.8.8-beta
v0.8.7-beta
v0.8.6-beta
v0.8.5-beta
v0.8.4-beta
v0.8.3-beta
v0.8.2-beta
v0.8.1-beta
v0.8.0-beta
v0.7.9-beta
v0.7.8-beta
v0.7.7-beta
v0.7.6-beta
v0.7.5-beta
v0.7.4-beta
v0.7.3-beta
v0.7.2-beta
v0.7.1-beta
v0.7.0-beta
v0.6.9-beta
v0.6.8-beta
v0.6.7-beta
v0.6.6-beta
v0.6.5-beta
v0.6.4-beta
v0.6.3-beta
v0.6.2-beta
v0.6.1-beta
v0.6.0-beta
v0.5.8-beta
v0.5.7-beta
v0.5.6-beta
v0.5.5-beta
v0.5.4-beta
v0.5.3-beta
v0.5.2-beta
v0.5.1-beta
v0.5.0-beta
v0.4.5-alpha
v0.4.4-alpha
v0.4.3-alpha
v0.4.2-alpha
v0.4.1-alpha
v0.4.0-alpha
v0.3.8-alpha
v0.3.7-alpha
develop
v0.3.6-alpha
v0.3.5-alpha
v0.3.4-alpha
v0.3.3-alpha
v0.3.2-alpha
v0.3.1-alpha
v0.3.0-alpha
v0.2.5-alpha
v0.2.4-alpha
v0.2.3-alpha
v0.2.2-alpha
v0.2.1-alpha
v0.2.0-alpha
v0.1.5-alpha
v0.1.4-alpha
v0.1.3-alpha
v0.1.2-alpha
v0.1.1-alpha
v0.1.0-alpha
v0.0.62-alpha
v0.0.61-alpha
v0.0.60-alpha
v0.0.59-alpha
v0.0.58-alpha
v0.0.57-alpha
v0.0.56-alpha
v0.0.55-alpha
v0.0.54-alpha
v0.0.53-alpha
v0.0.52-alpha
v0.0.51-alpha
v0.0.50-alpha
v0.0.49-prealpha
v0.0.48-prealpha
v0.0.47-prealpha
v0.0.46-prealpha
v0.0.45-prealpha
v0.0.44-prealpha
v0.0.43-prealpha
v0.0.42-prealpha
v0.0.41-prealpha
v0.0.40-prealpha
v0.0.39-prealpha
v0.0.38-prealpha
v0.0.37-prealpha
v0.0.36-prealpha
v0.0.35-prealpha
v0.0.34-prealpha
v0.0.33-prealpha
v0.0.32-prealpha
v0.0.31-prealpha
v0.0.30-prealpha
v0.0.29-prealpha
v0.0.28-prealpha
v0.0.27-prealpha
v0.0.26-prealpha
v0.0.25-prealpha
v0.0.24-prealpha
v0.0.23-prealpha
v0.0.22-prealpha
v0.0.21-prealpha
v0.0.20-prealpha
v0.0.19-prealpha
v0.0.18-prealpha
v0.0.17-prealpha
v0.0.16-prealpha
v0.0.15-prealpha
v0.0.14-prealpha
v0.0.13-prealpha
v0.0.12-prealpha
v0.0.11-prealpha
v0.0.10-prealpha
v0.0.9-prealpha
v0.0.8-prealpha
v0.0.7-prealpha
v0.0.6-prealpha
v0.0.5-prealpha
v0.0.4-prealpha
v0.0.3-prealpha
v0.0.2-prealpha
v0.0.1-prealpha
Labels
Clear labels
ad-hoc
api
bug
ci-cd
content
dependencies
enhancement
frontend
in-progress
jellyfin
parked
priority: high
priority: low
priority: medium
review
security
One-off / ad-hoc work not tracked by a dedicated issue
REST API / HTTP endpoints
Something isn't working
Build, test, deploy pipeline
Channel content / schedules / playlists
Dependency updates (Renovate)
New feature or improvement
ChicoryTV React SPA frontend
Claimed by an active session — do not pick up
Jellyfin tuner / IPTV integration
Excluded from automatic queue pickup; work only when explicitly selected
Adversarial review finding
Security / vulnerability fix
Milestone
No items
No Milestone
Blazor removal (#91 phase b)
Projects
Clear projects
No projects
No Assignees
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: timothy/ersatztv#205
Reference in New Issue
Block a user
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Severity: SHOULD-FIX (doesn't block deletion, but is the plan's own stated safety net)
What's wrong
The gate comment asks: "can we restore Blazor from a tag if a gap surfaces post-deletion?" The only tags in the repo are release tags (
v26.6.0,v26.5.0, …). There is no dedicated pre-removal tag at the exact commit that still has Blazor, and Step 2/3 of the plan doesn't cut one.Since deletion removes both the reference implementation and the
/system/healthescape hatch (Index.razoris deleted), a post-deletion gap is expensive to recover from — you'd have to guess which release tag still matches currentmainminus Blazor and cherry-pick the difference.Required (recommended)
As the first action of the Step 2 deletion PR, cut an annotated tag (e.g.
blazor-final/pre-spa-cutover) on the pre-deletion commit and document the restore procedure (checkout tag → cherry-pick the deletedPages//Shared//startup wiring, or revert the deletion commit) in the phase-(b) notes. Cheap insurance; makes rollback a one-liner instead of an archaeology exercise.Accepted. Plan: cut an annotated
blazor-finaltag on the main commit immediately preceding the removal merge (not now — main will move before the removal PR), and document the restore path in the removal PR (checkout tag →docker build→ pin test container). Will execute as part of the removal PR merge routine.timothy referenced this issue2026-07-11 01:14:09 +02:00
Claiming — session started 2026-07-11 (evening), paired with #206. Deliverable this session: document the pre-removal rollback-tag procedure (tag name, exact
git tag -astep to run as the first action of the removal merge — not now, since main will move before the removal PR — plus the restore path) indocs/decisions.md+ the removal runbook, so the removal PR routine just executes it. No tag cut this session. Docs-only, parallel-safe vs #202/#204/#253.Resolved — rollback-tag procedure documented (PR #261, merged
7608ccce)What was done. Documented the pre-removal
blazor-finalrollback-tag procedure + restore path indocs/decisions.md, and made it step 1 of the new removal runbook (docs/blazor-route-parity.md§5), so the removal PR routine executes it deterministically.Procedure (recorded):
maincommit immediately preceding the removal (the last commit that still containsErsatzTV/Pages/**) — cutgit tag -a blazor-finaland push it. The tag name isblazor-final(notv*), so it does not trigger thev*prod-release build in.gitea/workflows/docker-build.yml(independently verified against the workflow'stags: ['v*']filter +startsWith(github.ref, 'refs/tags/v')publish guards).git checkout blazor-final→docker build -f docker/Dockerfile -t ersatztv:blazor-final .→ pin the test container to that image while the gap is fixed forward onmain; orgit revertthe single deletion merge commit.Why not cut the tag now. As agreed in the earlier comment:
mainstill carries Blazor and will advance before the removal PR, so the tag must be cut at removal time on the exact pre-deletion commit — not now. The runbook + decisions.md entry ensure it isn't forgotten.Docs updated (same PR):
docs/decisions.md(rollback-tag entry),docs/blazor-route-parity.md(§5 runbook step 1).Closing: the finding (plan had no documented rollback tag/restore) is resolved. The actual tag-cut is a scripted step of the gated removal PR.