pip (deps-dev): bump black from 26.3.0 to 26.3.1#321
Open
dependabot[bot] wants to merge 1 commit into
Open
Conversation
Bumps [black](https://github.com/psf/black) from 26.3.0 to 26.3.1. - [Release notes](https://github.com/psf/black/releases) - [Changelog](https://github.com/psf/black/blob/main/CHANGES.md) - [Commits](psf/black@26.3.0...26.3.1) --- updated-dependencies: - dependency-name: black dependency-version: 26.3.1 dependency-type: direct:development ... Signed-off-by: dependabot[bot] <support@github.com>
dependabot
Bot
added
dependencies
ellie-bound1-NHSD
pushed a commit
that referenced
this pull request
May 18, 2026
…e-api repo (#349) # Pull Request ## 🧾 Ticket Link https://nhsd-jira.digital.nhs.uk/browse/NPA-6978 --- ## 📄 Description/Summary of Changes There are 14 Dependabot branches/PRs up to 14/05/2026. Most of these are small package updates. Analysis: -----8<-----8<-----8<-----8<-----8<----- The 14 Dependabot branches break down into three categories: pyproject.toml + lock file (direct dep bumps, 3 PRs): - #320 — black 26.3.1 in pyproject.toml - #321 — black 26.3.1 in pyproject.toml - #332 — pytest 9.0.3 in pyproject.toml Lock file only (transitive dep bumps, 10 PRs): - poetry.lock: requests, cryptography, python-dotenv, lxml, urllib3, authlib - poetry.lock: requests - poetry.lock: (implied by sandbox pytest) - package-lock.json: follow-redirects, basic-ftp, fast-uri GitHub Actions YAML only (1 PR): - #345 — workflows changes, no lock files So the practical plan is: apply the 3 pyproject.toml edits, regenerate all lock files fresh (which picks up all transitive updates in one shot), cherry-pick #345, then commit and push. -----8<-----8<-----8<-----8<-----8<----- Steps: 1. Made the required bumps to `pyproject.toml` and `sandbox/pyproject.toml` 2. Updated lock files: -- poetry lock -- cd sandbox && poetry lock && cd .. -- cd scripts && poetry lock && cd .. -- npm update follow-redirects basic-ftp fast-uri 3. cherry-pick #345 -- git cherry-pick origin/dependabot/github_actions/github-dependencies-0645f932cc 4. Noted vulnerability in `pytest-nhsd-apim`: upgraded from `^5.0.0` to `^6.0.0` Outcome is 'better than Dependabot': Package | Dependabot suggested | Now in lock black (root + sandbox) | 26.3.1 | 26.3.1 ✅ pytest (sandbox) | 9.0.3 | 9.0.3 ✅ python-dotenv | 1.2.2 | 1.2.2 ✅ lxml | 6.1.0 | 6.1.0 ✅ urllib3 | 2.7.0 | 2.7.0 ✅ requests | 2.33.0 | 2.34.2 ⬆️ newer authlib | 1.6.12 | 1.7.2 ⬆️ newer cryptography | 46.0.7 | 48.0.0 ⬆️ newer follow-redirects | 1.16.0 | 1.16.0 ✅ basic-ftp | 5.3.1 | 5.3.1 ✅ fast-uri | 3.1.2 | 3.1.2 ✅ --- ## 🧪 Developer Testing Carried Out <!-- Describe what tests (automated/unit/manual etc.) have been done for the ticket. Include: --> <!-- - Any tests added/updated --> <!-- - Evidence that each acceptance criterion from the Jira ticket is met --> <!-- - Evidence of tests running eg. link to github workflow with tests passing or screenshot of tests running locally --> - `make schema-all`: All tests pass ✅ - `make generate-postman-collection` regenerates `postman/validated_relationship_service.sandbox.postman_collection.json` with only the UUIDs changed. ✅ - `make test-postman-collection SANDBOX_BASE_URL=https://sandbox.api.service.nhs.uk/validated-relationships/FHIR/R4`: All tests pass ✅ --- ## 📋 PR Principles <!-- Principles we as a team follow when conducting a PR --> - Keep PRs Small and Focused: Ensure the PR addresses a single task or feature to make it easier to review. - Multiple PRs for one Ticket: When splitting work into multiple PRs, clearly describe what this PR addresses and outline the remaining work to complete the ticket. - Ensure Tests Are Included: Add or update unit, integration, or end-to-end tests to cover the changes made. - Follow Coding Standards: Ensure the code adheres to the team's coding guidelines and best practices. - Resolve Comments Promptly: If you raise a comment, ensure you follow up and resolve it before approving the PR to maintain clarity and ensure comments are addressed. - Foster Learning: PR reviews are an opportunity to share knowledge, provide constructive feedback, and encourage a collaborative environment. ## 🏷️ Naming Conventions Reminder Please ensure the following naming conventions are followed: - PR title follows the format: `NPA-XXXX: <short-description>` - Branch name follows the convention: `<type>/NPA-XXXX/<short-description>` - Commit messages follow the template: `NPA-XXXX: <short-description>` --------- Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
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
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 black from 26.3.0 to 26.3.1.
Release notes
Sourced from black's releases.
Changelog
Sourced from black's changelog.
Commits
c6755bbPrepare release 26.3.1 (#5046)69973fdHarden blackd browser-facing request handling (#5039)4937fe6Fix some shenanigans with the cache file and IPython (#5038)2e641d1docs: remove outdated Black Playground references (#5044)c014b22Remove unused internal code (#5041)0dae20bAdd new changelog (#5036)c5c1cbdMinor release patches (#5035)7e5a828docs: clarify relationship between Black style and PEP 8 (#5025)69705dedocs: add clearer pyproject configuration guidance (#5026)You can trigger a rebase of this PR by commenting
@dependabot rebase.Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
@dependabot rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@dependabot ignore this major versionwill 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 versionwill 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 dependencywill close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)You can disable automated security fix PRs for this repo from the Security Alerts page.