Repository navigation
chore(deps): bump flask from 3.1.2 to 3.1.3 in /src - #1
Merged
Merged
Conversation
dependabot
Bot
added
dependencies
Contributor
AI AnalysisType: pull_request This pull_request requires review. Please check the full description for details. This summary was automatically generated by AI to help with triage and may not be 100% accurate. |
Contributor
|
@dependabot recreate |
Bumps [flask](https://github.com/pallets/flask) from 3.1.2 to 3.1.3. - [Release notes](https://github.com/pallets/flask/releases) - [Changelog](https://github.com/pallets/flask/blob/main/CHANGES.rst) - [Commits](pallets/flask@3.1.2...3.1.3) --- updated-dependencies: - dependency-name: flask dependency-version: 3.1.3 dependency-type: direct:production ... Signed-off-by: dependabot[bot] <support@github.com>
dependabot
Bot
force-pushed
the
dependabot/pip/src/flask-3.1.3
branch
from
October 9, 2026 18:36
f2c78f6 to
e323cd6
Compare
karlspace
added a commit
that referenced
this pull request
Oct 10, 2026
The caller only started for src/Dockerfile and tools/Dockerfile, so a Dependabot PR of any other ecosystem never reached the auto-merge module: no job, no annotation, the PR just stayed open. The pip security update for src/requirements.txt (#1) is such a PR. Without the filter every Dependabot PR gets an explicit decision: * docker (src/Dockerfile) and pip (src/requirements.txt): merged only as patch updates and only after docker-release.yml ran on the PR head and passed. Its pull_request paths (src/**) already cover both files, and the image build ADDs requirements.txt and installs it, so the required workflow really exercises the update. * github-actions and any change under .github/: left open by the module's own CI guard, now with a visible notice. * any other file: left open as "not tested", because docker-release.yml does not start for it. Permissions, secrets, merge settings and required-workflows are unchanged; docker-release.yml needed no wider paths.
Contributor
|
🎉 This PR is included in version 0.6.4 🎉 The release is available on GitHub release Your semantic-release bot 📦🚀 |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Bumps flask from 3.1.2 to 3.1.3.
Release notes
Sourced from flask's releases.
Changelog
Sourced from flask's changelog.
Commits
22d9247release version 3.1.3089cb86Merge commit from forkc17f379request context tracks session access27be933start version 3.1.34e652d3Abort if the instance folder cannot be created (#5903)3d03098Abort if the instance folder cannot be created407eb76document using gevent for async (#5900)ac5664ddocument using gevent for async4f79d5bIncrease required flit_core version to 3.11 (#5865)fe3b215Increase required flit_core version to 3.11