Skip to content

chore: bump fastapi from 0.163.0 to 0.163.1 - #451

Merged
gregoryfoster merged 1 commit into
mainfrom
dependabot/uv/fastapi-0.163.1
Nov 20, 2026
Merged

gregoryfoster merged 1 commit into
mainfrom
dependabot/uv/fastapi-0.163.1

Conversation

@dependabot

@dependabot dependabot Bot commented on behalf of github Nov 20, 2026 •

Copy link
Copy Markdown
Contributor

Bumps fastapi from 0.163.0 to 0.163.1.

Release notes

Sourced from fastapi's releases.

0.163.1

FastAPI includes an official skill that helps coding agents use new features and recommended patterns for your installed version. Install it with uvx library-skills in your project. See Develop with AI.

Fixes

Commits

@dependabot dependabot Bot added dependencies Pull requests that update a dependency file python:uv Pull requests that update python:uv code labels Nov 20, 2026
@gregoryfoster

Copy link
Copy Markdown
Member

Brief: the third Dependabot uv batch, #451 #452 #453 (epic #394 coordinator, 2026-11-20)

Pre-flighted read-only against origin/main 44b9c6a7. The live build is 768b3dfd: everything since it is CI, docs and skills, with no restart. Labels: [measured] read from the PR, the lock or the code; [traced] followed through code or docs; [stated] a changelog says so.

This is the first Dependabot batch under the PR-only ruleset (#445). The landing procedure is docs/DEPENDENCIES.md → Dependabot PRs as rewritten by #446: no local merge and no push. Note anything in that recipe that didn't hold.

The three PRs [measured]

Each moves only its own pyproject.toml floor and uv.lock stanza. No co-core line appears in any diff. All three are CLEAN on base 44b9c6a7, with lint, test, integration, migrations and the audit green on their heads (#451 662e29df, #452 d7d7a342, #453 1b648914).

PR Change Release notes, against Watcher
#453 sqlalchemy 2.1.8 → 2.1.9 (floor >=2.1.9) ORM bug fixes only: post_update deletes, and_() criteria in selectinload/lazyload against aliased subqueries, and loader options under selectin_polymorphic and subqueryload on aliased entities. Watcher's models use none of those. Alembic is its only other dependent in the lock.
#452 python-ulid 4.1.0 → 4.2.0 Adds ulid.sqlalchemy.ULIDType behind a new extra. The fixes: the ULID(...) constructor now raises TypeError for a 16-character string or an int; ULID.parse reads integers differently; from_datetime/from_int raise ValueError rather than OverflowError; Pydantic validation errors change. Watcher calls only ULID() and ULID.from_str [traced: src/core/models/base.py:27,32; src/core/ulids.py; the str(ULID()) calls in fetch_commands.py and process_commands.py]. Its own src.core.models.base.ULIDType is unrelated to the new ulid.sqlalchemy.ULIDType, since nothing installs the extra. tests/core/test_ulids.py holds the canonical-uppercase contract and is green on the head.
#451 fastapi 0.163.0 → 0.163.1 One fix, OpenAPI for a response model with a nested computed field. Watcher serves only /health and /ready, with the docs endpoints off.

No migrations: none of the three is procrastinate or ships schema, so there's no pre step this time (cf. #443).

Hazards (weigh them; overrule with evidence)

  1. One PR at a time, by the recipe. For each one:

    • the co-core grep on gh pr diff <N>, which must print nothing;
    • gh pr checks <N> --watch --required;
    • gh pr merge <N> --squash;
    • on the host, git pull --ff-only, then bash scripts/co-pypi.sh uv sync --locked;
    • then the tree check against pull/<N>/head.

    After each merge, the next PR is behind. Request a rebase by commenting dependabot rebase with the @ prefix. Never use GitHub's Update branch on these: it adds a non-Dependabot commit, and Dependabot stops rebasing. Re-post after about 6 minutes of silence. Suggested order: chore: update sqlalchemy[asyncio] requirement from <3,>=2.1.8 to >=2.1.9,<3 #453, chore: bump python-ulid from 4.1.0 to 4.2.0 #452, chore: bump fastapi from 0.163.0 to 0.163.1 #451.

  2. Merge and sync in the same sitting, and restart once after the last. All three are runtime packages, so the batch needs one sudo systemctl restart watcher, with the operator's OK at the time.

    • Monday's patch reboot, 2026-11-23 01:00Z, deploys main as checked out. The unit's uv sync --locked --offline start check refuses a locked wheel that's in neither the venv nor uv's cache. So a merge left unsynced breaks that boot.
    • Land well before Monday's window, and keep clear of the quiet ranges, 03:15–03:45Z and 05:15–06:00Z.
  3. The squash title is Dependabot's PR title (chore: bump …), which already fits the repo's form. No edit is needed.

  4. Rollback for any one PR: a revert PR, squash-merged after green, then pull, sync and restart. There's no schema to undo.

Read-back

  • /health reports the final main SHA, and NRestarts=0.
  • The venv reads sqlalchemy 2.1.9, python-ulid 4.2.0 and fastapi 0.163.1, with co-core still 0.48.2 and procrastinate 3.11.0.
  • The embedded worker runs its periodic jobs (drain_pending_*, publish_pending_fetch_commands), each ending Success. That covers the ULID load path (ULIDType → ULID.from_str) on real rows.
  • The four consumers are polling, and nothing is at WARNING or higher since the restart.
  • Each PR's tree check matches, and the push runs on main are green by job.

Done when

All three are merged as squash PRs with CI green by job, synced, live after one restart, and the read-back is posted here. Each PR shows as merged.

Out of scope

Later Dependabot PRs; redis (#441's ignore); any sibling repo.

@gregoryfoster

Copy link
Copy Markdown
Member

Brief re-check before landing (2026-11-20)

Re-ran against origin/main 44b9c6a7 and each head (#453 1b648914, #452 d7d7a342, #451 662e29df).

Held [measured]: each diff is its own pyproject.toml floor plus one uv.lock version/specifier pair; the co-core grep prints nothing on all three; all three CLEAN with lint, test, integration, migrations and the audit green; live is 768b3dfd, NRestarts=0; the venv reads sqlalchemy 2.1.8, python-ulid 4.1.0, fastapi 0.163.0, co-core/co-core-aio 0.48.2, procrastinate 3.11.0. No post_update, selectinload/lazyload/subqueryload/selectin_polymorphic or computed_field anywhere in src/.

Corrections:

  1. chore: bump python-ulid from 4.1.0 to 4.2.0 #452: Watcher also calls ULID.from_int — src/core/watch_events.py:70, the process-local monotonic floor for event_id (ULID.from_int(int(_last_event_id) + 1)). 4.2.0 changes only its out-of-range error (ValueError for a value outside 0..2¹²⁸−1, was OverflowError); int(ULID)+1 can't reach that bound, and nothing in src/ catches either type. No impact [measured: 4.1.0 vs 4.2.0 wheels]. The bare ULID() path (default_generator.generate()) is unchanged between the two wheels.
  2. chore: update sqlalchemy[asyncio] requirement from <3,>=2.1.8 to >=2.1.9,<3 #453's title is chore: update sqlalchemy[asyncio] requirement from <3,>=2.1.8 to >=2.1.9,<3, not chore: bump …. Still the repo's [type]: <description> form; no edit.

Landing in the suggested order: #453, #452, #451.

@gregoryfoster

Copy link
Copy Markdown
Member

@dependabot rebase

@dependabot
dependabot Bot force-pushed the dependabot/uv/fastapi-0.163.1 branch from 662e29d to afdd106 Compare November 20, 2026 17:36
Bumps [fastapi](https://github.com/fastapi/fastapi) from 0.163.0 to 0.163.1.
- [Release notes](https://github.com/fastapi/fastapi/releases)
- [Commits](fastapi/fastapi@0.163.0...0.163.1)

---
updated-dependencies:
- dependency-name: fastapi
  dependency-version: 0.163.1
  dependency-type: direct:production
  update-type: version-update:semver-patch
...

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot
dependabot Bot force-pushed the dependabot/uv/fastapi-0.163.1 branch from afdd106 to 2cd5e76 Compare November 20, 2026 17:37
@gregoryfoster
gregoryfoster merged commit a61cf8d into main Nov 20, 2026
5 checks passed
@gregoryfoster
gregoryfoster deleted the dependabot/uv/fastapi-0.163.1 branch November 20, 2026 17:38
@gregoryfoster

Copy link
Copy Markdown
Member

Read-back: third Dependabot uv batch live (2026-11-20)

All three landed as squash PRs, one at a time, by docs/DEPENDENCIES.md → Dependabot PRs. There was no local merge and no push. The batch had one restart, with the operator's OK, at 2026-11-20T17:59:34Z. Corrections to the brief went up first (comment above).

PR Squash on main Head merged Tree check (pull/<N>/head vs HEAD) main push CI, by job
#453 sqlalchemy 2.1.9 d674ed77 1b648914 044712cc… = lint, test, integration, migrations ✅ (run 44784505147)
#452 python-ulid 4.2.0 54c8a787 dd4f3054 (rebased) efb5452b… = all four ✅ (44784892863)
#451 fastapi 0.163.1 a61cf8dc 2cd5e764 (rebased) 18703a40… = all four ✅ (44785297625)

Before each merge, the co-core grep on gh pr diff printed nothing, and the four required checks were green on the head being merged. Each landing was followed by co-pypi.sh uv sync --locked (each swapped exactly its one package) and scripts/pre-ship.sh (green). The audit push runs are green with no annotations.

Live [measured]:

  • /health → {"status":"ok","build":"a61cf8dc"}, /ready 200. NRestarts=0, active.
  • Venv: sqlalchemy 2.1.9, python-ulid 4.2.0, fastapi 0.163.1. co-core and co-core-aio are still 0.48.2, procrastinate still 3.11.0.
  • The start check printed Checked 79 packages, then: broker reachable, the four consumers started (info.registry, info.watch-check, content.blobs, content.derived), and info.registry replay complete → tailing (1003 announcements processed).
  • In the first ~3½ min, every periodic job that ran ended Success:
    • ×3 each: drain_pending_watch_events, drain_pending_archiver_sync, publish_pending_fetch_commands, publish_pending_process_commands, schedule_tick;
    • ×1 each: publish_watch_status, reap_fetch_commands, reap_process_commands, recover_stalled_jobs.
  • The ULID load path ran on real rows: publish_watch_status published 22, i.e. every WatchedItem, whose id/archiver_info_item_id are ULIDType → ULID.from_str.
  • The journal since the restart has 2122 JSON records, all INFO, and nothing at WARNING or higher.

Known limits:

  • The drains had nothing to drain. drain_pending_* and publish_pending_* each published 0, so their own row loads, and ULID.from_int in _mint_event_id (which only runs on a sub-millisecond collision), weren't exercised live. Their ULID evidence is the suite, plus publish_watch_status above.
  • "Consumers polling" rests on their start lines and the absence of errors. Only info.registry logs per message at INFO. The other three consumers saw no traffic in the window, and they don't log idle polls.
  • Recipe, didn't hold as written: a head change isn't proof a rebase request was answered. chore: update sqlalchemy[asyncio] requirement from <3,>=2.1.8 to >=2.1.9,<3 #453's merge made Dependabot rebase chore: bump fastapi from 0.163.0 to 0.163.1 #451 on its own (afdd106c, on d674ed77), unprompted. After chore: bump python-ulid from 4.1.0 to 4.2.0 #452 merged, that put chore: bump fastapi from 0.163.0 to 0.163.1 #451's head ahead of my request while the PR was still BEHIND. The answering push (2cd5e764, on 54c8a787) came about 80s after the comment. Check the new head's parent (git merge-base --is-ancestor <main> FETCH_HEAD), or mergeStateStatus = CLEAN, before gh pr checks --watch.
  • Recipe, held: both @dependabot rebase requests were answered on the first try (about 90s and 80s), with no re-posts. Strict checks blocked nothing, and Update branch was never used.
  • Recipe, gap: gh pr checks --watch --required run right after a force-push can report before the new head's checks register. I waited 15s first. With the four required checks the ruleset enforces, gh pr merge would refuse anyway, so this is cosmetic.

Epic #394 is untouched. Monday's 2026-11-23 01:00Z patch reboot deploys a61cf8dc with a matching venv.

gregoryfoster added a commit that referenced this pull request Nov 20, 2026
…h, reply rule

- Ancestry check fetches the PR ref first in one call (measured on #451: 1,
  #455: 0, bad ref: 128) and names its exit codes.
- mergeStateStatus: only CLEAN reads as on main; BLOCKED (#455, up to date
  with checks pending) defers to the ancestry form.
- The cause sentence names the uv.lock conflict that triggers the auto-rebase.
- --watch also waits for the new head's runs to be listed.
- Re-post rule: a Dependabot reply is an answer, not silence.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

dependencies Pull requests that update a dependency file python:uv Pull requests that update python:uv code

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant