Skip to content

chore(deps): update fastapi requirement from <0.137,>=0.115.0 to >=0.115.0,<0.142 - #261

Merged
github-actions[bot] merged 1 commit into
mainfrom
dependabot/pip/fastapi-gte-0.115.0-and-lt-0.142
Oct 1, 2026
Merged

github-actions[bot] merged 1 commit into
mainfrom
dependabot/pip/fastapi-gte-0.115.0-and-lt-0.142

Conversation

@dependabot

@dependabot dependabot Bot commented on behalf of github Oct 1, 2026

Copy link
Copy Markdown
Contributor

Updates the requirements on fastapi to permit the latest version.

Release notes

Sourced from fastapi's releases.

0.141.1

Fixes

  • 🐛 Fix support for background tasks and headers from dependencies in app.frontend(). PR #16105 by @​tiangolo.

Docs

Commits
  • 95f8322 🔖 Release version 0.141.1 (#16106)
  • f137944 📝 Update release notes
  • d623544 🐛 Fix support for background tasks and headers from dependencies in `app.fron...
  • 1d211b9 📝 Update release notes
  • 8a1f876 📝 Document FASTAPI_ENV in FastAPI CLI guide (#16104)
  • c7e7b65 🔖 Release version 0.141.0 (#16103)
  • 6bceb84 📝 Update release notes
  • 5429fed ✨ Add app.frontend(check_dir="auto"), to make local development more conven...
  • 628663f 🔖 Release version 0.140.13 (#16096)
  • 0b54fd0 📝 Update release notes
  • Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.


Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

  • @dependabot rebase will rebase this PR
  • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
  • @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
  • @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

Updates the requirements on [fastapi](https://github.com/fastapi/fastapi) to permit the latest version.
- [Release notes](https://github.com/fastapi/fastapi/releases)
- [Commits](fastapi/fastapi@0.115.0...0.141.1)

---
updated-dependencies:
- dependency-name: fastapi
  dependency-version: 0.141.1
  dependency-type: direct:production
...

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot @github

dependabot Bot commented on behalf of github Oct 1, 2026

Copy link
Copy Markdown
Contributor Author

Labels

The following labels could not be found: dependencies. Please create it before Dependabot can add it to a pull request.

Please fix the above issues or remove invalid values from dependabot.yml.

@github-actions
github-actions Bot merged commit 62c2343 into main Oct 1, 2026
17 checks passed
@dependabot
dependabot Bot deleted the dependabot/pip/fastapi-gte-0.115.0-and-lt-0.142 branch October 1, 2026 12:50
dev-bot-fusionaize pushed a commit that referenced this pull request Oct 4, 2026
Updates the requirements on [fastapi](https://github.com/fastapi/fastapi) to permit the latest version.
- [Release notes](https://github.com/fastapi/fastapi/releases)
- [Commits](fastapi/fastapi@0.115.0...0.141.1)

---
updated-dependencies:
- dependency-name: fastapi
  dependency-version: 0.141.1
  dependency-type: direct:production
...

Signed-off-by: dependabot[bot] <support@github.com>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
dev-bot-fusionaize pushed a commit that referenced this pull request Oct 4, 2026
Adopts the provenance notice from LangeVC/ops-engine, verbatim and in the same
position - after the header block, before the first section - and repeats it in
the Repository & Contributing section at the bottom, so a reader who arrives at
either end learns which side is authoritative.

The surrounding text is corrected while doing it. It called the GitHub copy a
read-only mirror and said a pull request opened there cannot be merged. Both are
false: #259, #260 and #261 were all merged on the mirror's main by Dependabot,
and the Auto-merge workflow is active there. The real constraint is the one that
matters operationally and is now written down - the mirror's main is replaced by
whatever canonical holds, so a change that lands only on the mirror is lost at
the next release push unless it is carried over. Those three had to be carried
over by hand today.
dev-bot-fusionaize pushed a commit that referenced this pull request Oct 4, 2026
Adopts the notice from LangeVC/ops-engine at both ends of the README, and
corrects the surrounding claim that the GitHub copy is read-only and its pull
requests cannot be merged - #259, #260 and #261 were all merged there by
Dependabot with auto-merge active. What is written now is the constraint that
actually holds: the mirror's main is replaced by whatever canonical holds, so a
change landing only on the mirror is lost at the next release push.

Documentation only, no version bump and no tag.
dev-bot-fusionaize pushed a commit that referenced this pull request Oct 4, 2026
Follows Capacium/capacium, which carries the notice at both ends: a NOTE callout
after the badges and prose in the closing section. Neither names the git host or
a clone URL, which is the convention this repository was supposed to follow and
did not - the old closing section named both, and the previous commit copied that
to the top as well. Both are gone.

Two sentences are not taken over verbatim, because they are not true here.
Capacium calls its mirror read-only and says contributions are synchronized
automatically. On this mirror Dependabot opens pull requests and auto-merge is
active, so it is not read-only; and nothing syncs merges back - #259, #260 and
#261 were merged there and had to be carried upstream by hand for 2.10.1. The
closing section says that instead, since it is the part a contributor can be
caught by.

The one remaining langevc.com reference is faigate.langevc.com, a parked product
hostname explained in place, not the git origin.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants