Migrate Starlette TemplateResponse call sites to the new signature #4
Labels
No labels
area:ai
area:ci-cd
area:notifications
area:observability
area:public-pages
backlog
bug
duplicate
enhancement
help wanted
invalid
question
type:decision
type:feature
type:infra
type:maintenance
type:security
v1.0.1
v1.1.0
v1.2.0
v1.3.0
v2.0.0
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
rbrooks/WeatherBot#4
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?
Target release: v1.0.1
Update all
TemplateResponse(...)call sites to the currentTemplateResponse(request, name, context)signature to clear Starlette templating deprecation warnings.Why now: this is a prerequisite for adopting the Renovate Starlette 1.x major bump — the old signature is removed in newer Starlette.
Source:
SECURITY_AUDIT_REMEDIATION_PLAN.md→ "Remaining non-blocking follow-up".Verified on
main(8dc5b3f): all 13TemplateResponsecall sites already use the new request-first signatureTemplateResponse(request, name, context)— acrossapp/main.py,app/api/auth.py,channels.py,locations.py,location_subs.py,public.py, andspc_impacts.py. A search for the deprecated string-first formTemplateResponse("name", ...)returns no matches.The migration was already done during earlier work (the note in
SECURITY_AUDIT_REMEDIATION_PLAN.mdpredated it). No code change required, so there is nothing blocking the Renovate Starlette 1.x major bump on this front.Closing as already complete.