The running image (~2 weeks old) happened to carry greenlet; the rebuild for this deploy was the FIRST fresh pip install . in weeks and resolved SQLAlchemy without greenlet. This exposes an unpinned dependency that any fresh build would hit.
Changes
Changed sqlalchemy>=2.0.0 to sqlalchemy[asyncio]>=2.0.0 in pyproject.toml
Added explicit greenlet>=3.0 pin
Why
The [asyncio] extra ensures SQLAlchemy pulls in greenlet for async support. The explicit pin makes the dependency visible and prevents future breaks on fresh builds.
Context
The running image was 2 weeks old and this was the first fresh build, so the drift was latent. This fix makes the async dependency explicit so a fresh build can never break this again.
## Summary
The running image (~2 weeks old) happened to carry greenlet; the rebuild for this deploy was the FIRST fresh `pip install .` in weeks and resolved SQLAlchemy without greenlet. This exposes an unpinned dependency that any fresh build would hit.
## Changes
- Changed `sqlalchemy>=2.0.0` to `sqlalchemy[asyncio]>=2.0.0` in pyproject.toml
- Added explicit `greenlet>=3.0` pin
## Why
The `[asyncio]` extra ensures SQLAlchemy pulls in greenlet for async support. The explicit pin makes the dependency visible and prevents future breaks on fresh builds.
## Context
The running image was 2 weeks old and this was the first fresh build, so the drift was latent. This fix makes the async dependency explicit so a fresh build can never break this again.
The running image (~2 weeks old) happened to carry greenlet; the rebuild
for this deploy was the first fresh in weeks and resolved
SQLAlchemy without greenlet. This exposes an unpinned dependency that any
fresh build would hit.
Add the [asyncio] extra to sqlalchemy and pin greenlet>=3.0 to prevent
future breaks on fresh builds.
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.
Summary
The running image (~2 weeks old) happened to carry greenlet; the rebuild for this deploy was the FIRST fresh
pip install .in weeks and resolved SQLAlchemy without greenlet. This exposes an unpinned dependency that any fresh build would hit.Changes
sqlalchemy>=2.0.0tosqlalchemy[asyncio]>=2.0.0in pyproject.tomlgreenlet>=3.0pinWhy
The
[asyncio]extra ensures SQLAlchemy pulls in greenlet for async support. The explicit pin makes the dependency visible and prevents future breaks on fresh builds.Context
The running image was 2 weeks old and this was the first fresh build, so the drift was latent. This fix makes the async dependency explicit so a fresh build can never break this again.