Skip to content

Update Black formatter image to version 25.11.0 in CI workflows - #877

Merged
ll7 merged 1 commit into
mainfrom
ll7/fix-black-ci
Dec 8, 2025
Merged

Update Black formatter image to version 25.11.0 in CI workflows#877
ll7 merged 1 commit into
mainfrom
ll7/fix-black-ci

Conversation

@ll7

@ll7 ll7 commented Dec 8, 2025

Copy link
Copy Markdown
Member

Description

Update the Black formatter image in CI workflows to version 25.11.0 to ensure compatibility and take advantage of the latest features and fixes.

Fixes # (issue)

Type of change

  • New feature (non-breaking change which adds functionality)

Does this PR introduce a breaking change?

No, old functionality remains usable.

Most important changes

The updates to the Docker image for the Black formatter in the CI workflows are the key changes. Reviewers should focus on the changes in the CI configuration files.

Checklist:

  • My code follows the style guidelines of this project
  • I have performed a self-review of my own code
  • I have commented my code, particularly in hard-to-understand areas
  • I have made corresponding changes to the documentation
  • My changes generate no new warnings
  • I have added tests that prove my fix is effective or that my feature works (might be obsolete with CI later on)
  • New and existing unit tests pass locally with my changes (might be obsolete with CI later on)

Summary by CodeRabbit

  • Chores
    • Updated Docker image versions for development tooling to ensure consistent code formatting practices across the CI/CD pipeline.

✏️ Tip: You can customize this high-level summary in your review settings.

@ll7 ll7 self-assigned this Dec 8, 2025
@coderabbitai

coderabbitai Bot commented Dec 8, 2025

Copy link
Copy Markdown
Contributor

Walkthrough

The pull request updates Docker image tags for the Black Python formatter across CI/CD and local development configurations. Both the GitHub Actions workflow and Docker Compose file now pin the image to version 25.11.0 for consistency and reproducibility.

Changes

Cohort / File(s) Summary
Black formatter image pinning
.github/workflows/format.yml, build/docker-compose.linter.yaml
Updated Docker image tags from pyfound/black to pyfound/black:25.11.0 to pin a specific formatter version; added trailing newline to YAML file

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

  • Both files are configuration-only changes with straightforward image tag updates
  • No logic or functionality modifications
  • Changes are consistent and repetitive across files

Poem

🐰 Versions locked in time so true,
Black 25.11.0, fresh and new!
From workflow to compose we go,
Consistency blooms wherever we hop!

Pre-merge checks and finishing touches

✅ Passed checks (3 passed)
Check name Status Explanation
Title check ✅ Passed The title accurately summarizes the main change: updating the Black formatter Docker image to version 25.11.0 across CI workflows.
Description check ✅ Passed The description includes most required sections (summary, type of change, breaking change statement, important changes, checklist) and explains the purpose of the update.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
✨ Finishing touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Post copyable unit tests in a comment
  • Commit unit tests in branch ll7/fix-black-ci

📜 Recent review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 7e25364 and 9d78d8e.

📒 Files selected for processing (2)
  • .github/workflows/format.yml (1 hunks)
  • build/docker-compose.linter.yaml (2 hunks)
⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (1)
  • GitHub Check: Build and push image
🔇 Additional comments (2)
.github/workflows/format.yml (1)

24-24: Consistency with local development environment.

The image tag update is aligned with the change in build/docker-compose.linter.yaml, ensuring that CI and local development use the same Black formatter version. This is good practice.

Please verify the image version validity using the same checks suggested for the docker-compose file, as both files must use a secure, existing image tag.

build/docker-compose.linter.yaml (1)

9-9: Pinning to pyfound/black:25.11.0 is correct.

The image tag exists on the official PyFoundation Docker registry, is actively maintained (last pushed November 10, 2025), and has no known security vulnerabilities. Black 25.11.0 is beyond the range of CVE-2024-21503 (which affected versions before 24.3.0), so this choice is secure and reproducible.


Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands and usage tips.

@ll7

ll7 commented Dec 8, 2025

Copy link
Copy Markdown
Member Author

CI format job suddenly failed with new black version. Use a fixed black version now.

https://github.com/una-auxme/paf/actions/runs/20031799145/job/57448542117

@ll7
ll7 merged commit f2ea5ac into main Dec 8, 2025
4 checks passed
@ll7
ll7 deleted the ll7/fix-black-ci branch December 8, 2025 15:51
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.

1 participant