[tino097]

Fixes #353

Proposed fixes:

Every fresh install since 2026-10-20 fails on import prefect:

TypeError: Body() got an unexpected keyword argument 'min_items'
  prefect/server/api/concurrency_limits_v2.py:305

Prefect 3.7 only requires fastapi<1.0, and FastAPI 0.155.0 removed the deprecated min_items argument Prefect still passes. This takes down the unit suite, prefect server start, and the integration CI. Main is red for this reason, and so are #356, #357 and the recent Dependabot PRs.

The first version of this PR pinned fastapi<0.155. The integration run on that commit got past the import and the server start, then ckan datapusher_plus prefect-deploy failed with a second FastAPI change: 0.144 to 0.154 no longer treat a JSON null as "missing" for Body(None) on an int parameter, so the Prefect client's workers/filter request (limit: null, offset: null) is rejected:

422 Unprocessable Entity ... {'type': 'int_type', 'loc': ['body', 'limit'], 'msg': 'Input should be a valid integer', 'input': None}

This PR therefore pins fastapi<0.144. 0.143.x is what main's last green CI run (2026-10-16) installed; the whole 0.144 to 0.162 range was released between 2026-10-18 and 23.

Check	Observed result
pip install --dry-run --ignore-installed -r requirements.txt	fastapi 0.143.5 with prefect 3.7.8
Local Prefect 3.7.8 server, POST workers/filter with limit: null	422 on fastapi 0.154.0; 404 (pool lookup, expected) on 0.143.5
PrefectClient.read_workers_for_work_pool against that server on 0.143.5	succeeds
Unit suite (pytest tests --ignore=tests/integration --ignore=tests/js, with --ckan-ini)	342 passed, 1 skipped on 0.143.5; 15 failed on 0.162.0 before any pin
CI on the <0.155 commit	unit suite passed, integration failed at prefect-deploy with the 422 above

• Pin rather than Prefect bump. prefect>=3.7,<3.8 stays; a Prefect release that works on current FastAPI is the real fix and this pin should go with it.
• No code change. Only requirements.txt and the changelog.

🤖 Generated with Claude Code

[codacy-production]

Up to standards ✅

🟢 Issues 0 issues

Results:
0 new issues

View in Codacy

🟢 Metrics 0 complexity · 0 duplication

Metric	Results
Complexity	0
Duplication	0

View in Codacy

AI Reviewer: first review requested successfully. AI can make mistakes. Always validate suggestions.

_{TIP This summary will be updated as you push new changes.}

[codacy-production]

Pull Request Overview

✅ No blocking issues noticed

No blocking implementation findings were identified. The dependency and Prefect compatibility criteria remain unverified by automated tests, including resolution, import, worker filtering, and deployment workflow coverage.

About this PR

• Consider adding automated dependency-resolution and Prefect smoke/integration coverage so the compatibility pin cannot be accidentally weakened or removed without detection.

Test suggestions

• Verify dependency resolution selects FastAPI below 0.144 while satisfying the Prefect constraint.
• Import Prefect successfully using the pinned dependency set.
• Exercise Prefect worker filtering with null limit and offset values.
• Run the Prefect deployment workflow against the pinned FastAPI version.

Prompt proposal for missing tests

Consider implementing these tests if applicable:
1. Verify dependency resolution selects FastAPI below 0.144 while satisfying the Prefect constraint.
2. Import Prefect successfully using the pinned dependency set.
3. Exercise Prefect worker filtering with null limit and offset values.
4. Run the Prefect deployment workflow against the pinned FastAPI version.

_{TIP Improve review quality by adding custom instructions
TIP How was this review? Give us feedback}