Bump black from 25.1.0 to 26.1.0

[dependabot]

Bumps black from 25.1.0 to 26.1.0.

Release notes

Sourced from black's releases.

26.1.0

Highlights

Introduces the 2026 stable style (#4892), stabilizing the following changes:

• always_one_newline_after_import: Always force one blank line after import statements, except when the line after the import is a comment or an import statement (#4489)
• fix_fmt_skip_in_one_liners: Fix # fmt: skip behavior on one-liner declarations, such as def foo(): return "mock" # fmt: skip, where previously the declaration would have been incorrectly collapsed (#4800)
• fix_module_docstring_detection: Fix module docstrings being treated as normal strings if preceded by comments (#4764)
• fix_type_expansion_split: Fix type expansions split in generic functions (#4777)
• multiline_string_handling: Make expressions involving multiline strings more compact (#1879)
• normalize_cr_newlines: Add \r style newlines to the potential newlines to normalize file newlines both from and to (#4710)
• remove_parens_around_except_types: Remove parentheses around multiple exception types in except and except* without as (#4720)
• remove_parens_from_assignment_lhs: Remove unnecessary parentheses from the left-hand side of assignments while preserving magic trailing commas and intentional multiline formatting (#4865)
• standardize_type_comments: Format type comments which have zero or more spaces between # and type: or between type: and value to # type: (value) (#4645)

The following change was not in any previous stable release:

• Regenerated the _width_table.py and added tests for the Khmer language (#4253)

This release alo bumps pathspec to v1 and fixes inconsistencies with Git's .gitignore logic (#4958). Now, files will be ignored if a pattern matches them, even if the parent directory is directly unignored. For example, Black would previously format exclude/not_this/foo.py with this .gitignore:

exclude/
!exclude/not_this/

Now, exclude/not_this/foo.py will remain ignored. To ensure exclude/not_this/ and all of it's children are included in formatting (and in Git), use this .gitignore:

*/exclude/*
!*/exclude/not_this/

This new behavior matches Git. The leading */ are only necessary if you wish to ignore matching subdirectories (like the previous behavior did), and not just matching root

... (truncated)

Changelog

Sourced from black's changelog.

26.1.0

Highlights

Introduces the 2026 stable style (#4892), stabilizing the following changes:

• always_one_newline_after_import: Always force one blank line after import statements, except when the line after the import is a comment or an import statement (#4489)
• fix_fmt_skip_in_one_liners: Fix # fmt: skip behavior on one-liner declarations, such as def foo(): return "mock" # fmt: skip, where previously the declaration would have been incorrectly collapsed (#4800)
• fix_module_docstring_detection: Fix module docstrings being treated as normal strings if preceded by comments (#4764)
• fix_type_expansion_split: Fix type expansions split in generic functions (#4777)
• multiline_string_handling: Make expressions involving multiline strings more compact (#1879)
• normalize_cr_newlines: Add \r style newlines to the potential newlines to normalize file newlines both from and to (#4710)
• remove_parens_around_except_types: Remove parentheses around multiple exception types in except and except* without as (#4720)
• remove_parens_from_assignment_lhs: Remove unnecessary parentheses from the left-hand side of assignments while preserving magic trailing commas and intentional multiline formatting (#4865)
• standardize_type_comments: Format type comments which have zero or more spaces between # and type: or between type: and value to # type: (value) (#4645)

The following change was not in any previous stable release:

• Regenerated the _width_table.py and added tests for the Khmer language (#4253)

This release alo bumps pathspec to v1 and fixes inconsistencies with Git's .gitignore logic (#4958). Now, files will be ignored if a pattern matches them, even if the parent directory is directly unignored. For example, Black would previously format exclude/not_this/foo.py with this .gitignore:

exclude/
!exclude/not_this/

Now, exclude/not_this/foo.py will remain ignored. To ensure exclude/not_this/ and all of it's children are included in formatting (and in Git), use this .gitignore:

*/exclude/*
!*/exclude/not_this/

This new behavior matches Git. The leading */ are only necessary if you wish to ignore

... (truncated)

Commits

• 6305bf1 Prepare 2026.1.0 release (#4892)
• e71305b Bump pypa/cibuildwheel from 3.3.0 to 3.3.1 (#4961)
• 21a2a8c Fix Shutdown multiprocessing Manager in schedule_formatting (#4952)
• e3146ce Bump docker/setup-buildx-action from 3.11.1 to 3.12.0 (#4919)
• fe1fbc4 Bump actions/upload-artifact from 5.0.0 to 6.0.0 (#4923)
• 2b4b7fc Bump actions/download-artifact from 6.0.0 to 7.0.0 (#4922)
• d745be6 docs: document --force-exclude for pre-commit workflows (#4957)
• b41acd6 Various CI and doc refactors (#4928)
• 6f43612 Handle pathspec v1 changes (#4958)
• 200c550 Bump furo from 2025.9.25 to 2025.12.19 in /docs (#4933)
• 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)

---

Resolves #4892
Resolves #4489
Resolves #4800
Resolves #4764
Resolves #4777
Resolves #1879
Resolves #4710
Resolves #4720
Resolves #4865
Resolves #4645
Resolves #4253
Resolves #4958
Resolves #4961
Resolves #4952
Resolves #4919
Resolves #4923
Resolves #4922
Resolves #4957
Resolves #4928
Resolves #4933

[github-actions]

🤖 Claude Code Review

Code Review - Dependency Update: black 25.1.0 → 26.1.0

Summary

This PR updates the black code formatter from version 25.1.0 to 26.1.0 in development-requirements.txt.

---

Review Against Checklist

Code Quality

• ✅ Code follows style guide - This is a simple dependency version update. No code changes to evaluate.
• ✅ No commented-out code - N/A, no code changes
• ✅ Meaningful variable names - N/A, no code changes
• ✅ DRY principle followed - N/A, no code changes
• ✅ Identify Defects - No defects identified. This is a standard dependency update for a development tool.

Testing

• ✅ Unit tests for new functions - N/A, no new functionality
• ✅ Integration tests for new endpoints - N/A, no new endpoints
• ✅ Edge cases covered - N/A, dependency update only
• ⚠️ Test coverage > 80% - Cannot verify from this diff alone. Recommend running test suite to ensure black 26.1.0 doesn't introduce formatting changes that break tests.

Recommendation: Run the test suite and black formatter to verify:

black --check .
pytest

Documentation

• ✅ Readme updated if needed - N/A, development dependency updates typically don't require README changes
• ✅ API docs updated - N/A, no API changes
• ✅ Inline comments for complex logic - N/A, no code changes
• ⚠️ CHANGELOG.md updated - Should verify if CHANGELOG.md exists and whether dependency updates are tracked there. Minor version bumps of dev dependencies may not require CHANGELOG entries depending on project conventions.
• ✅ Markdown formatting - N/A, no markdown files changed

Security

• ✅ No hardcoded credentials - N/A
• ✅ Input validation implemented - N/A
• ✅ Proper error handling - N/A
• ✅ No sensitive data in logs - N/A
• ✅ No license files with AQAAAD strings - N/A

---

Final Assessment

APPROVED ✅

This is a straightforward dependency update for a development tool (black code formatter). The change is minimal and low-risk.

Action Items:

1. ⚠️ Verify CHANGELOG.md exists and check if dependency updates should be documented (development-requirements.txt:2)
2. ⚠️ Run black --check . to ensure the new version doesn't introduce unexpected formatting changes
3. ⚠️ Run the full test suite to ensure compatibility

The PR is safe to merge once the above verification steps are completed.

Automated code review analyzing defects and coding standards

[github-actions]

🤖 Claude Code Review

I'll perform the code review on this pull request diff. Let me analyze the changes against the checklist.

Code Review Analysis

Pull Request Summary

This PR updates the black dependency from version 25.1.0 to 26.1.0 in development-requirements.txt.

---

Code Quality

✅ Code follows style guide - This is a dependency version update in a requirements file, which doesn't involve code changes.

✅ No commented-out code - No commented code present.

✅ Meaningful variable names - N/A for dependency file.

✅ DRY principle followed - N/A for dependency file.

✅ Identify Defects - No bugs or logic errors. This is a straightforward dependency version bump for the black code formatter. Black follows semantic versioning, and a major version bump (25→26) may include breaking changes, but since this is a development dependency used for code formatting, the risk is low. The formatting rules may have changed, which could affect CI/CD pipelines if they check for formatting compliance.

✅ Project memory consideration - No .claude/CLAUDE.md file found to consider.

---

Testing

⚠️ Unit tests for new functions - N/A for dependency update, but recommendation: After merging, run the full test suite to ensure black 26.1.0 doesn't introduce any issues with the development workflow.

⚠️ Integration tests - N/A, but the black formatter should be run against the codebase to verify compatibility.

⚠️ Edge cases covered - N/A for dependency update.

❓ Test coverage > 80% - Cannot determine from this diff alone; no test files modified.

---

Documentation

✅ Readme updated if needed - Not needed for a development dependency version bump.

✅ API docs updated - Not needed; black is a development tool.

✅ Inline comments - N/A for requirements file.

❌ CHANGELOG.md updated - development-requirements.txt:2 - The CHANGELOG should be updated to reflect this dependency version change. While it's a development dependency, major version bumps of tooling should be documented.

✅ Markdown formatting - No markdown files were modified in this PR.

---

Security

✅ No hardcoded credentials - None present.

✅ Input validation - N/A for dependency file.

✅ Proper error handling - N/A for dependency file.

✅ No sensitive data in logs - N/A for dependency file.

✅ No license files (.lic) or AQAAAD strings - None detected.

---

Summary & Recommendations

Issues Found:

1. Missing CHANGELOG.md entry ❌ - Document this black version upgrade

Recommendations:

1. After merging, run black . on the codebase to ensure version 26.1.0 doesn't reformat code unexpectedly
2. Check if any CI/CD pipelines need updates for black 26.1.0 compatibility
3. Review black 26.1.0 release notes for breaking changes: https://github.com/psf/black/releases

Overall Assessment:

Approval Status: ✅ APPROVED with minor documentation request

This is a low-risk change updating a development dependency. The only required action is updating the CHANGELOG.md to document this tooling update.

Automated code review analyzing defects and coding standards

[github-actions]

🤖 Claude Code Review

Code Review Analysis

Code Quality

✅ Code follows style guide

The change is a simple dependency version bump in a requirements file. No code style issues present.

File: development-requirements.txt:2

✅ No commented-out code

No commented code in this change.

✅ Meaningful variable names

N/A - This is a dependency specification file, not code.

✅ DRY principle followed

N/A - Single line change in requirements file.

✅ Identify Defects

No defects identified. This is a straightforward dependency version update from black 25.1.0 to 26.1.0. The version bump appears to be a major version update of the black code formatter.

Recommendation: Verify that black 26.1.0 doesn't introduce breaking changes in formatting rules that might affect the codebase. Consider running black across the codebase after merging to ensure consistency.

✅ Project memory configuration

No ./.claude/CLAUDE.md file was found in the repository to consider for this review.

Testing

⚠️ Unit tests for new functions

N/A - This is a development dependency update, not functional code. However, it would be prudent to ensure CI/CD passes with the new version.

⚠️ Integration tests for new endpoints

N/A - No new endpoints added.

⚠️ Edge cases covered

N/A - Dependency update only.

⚠️ Test coverage > 80%

Cannot determine from this diff. This change shouldn't affect test coverage as it's only updating a development tool version.

Documentation

✅ Readme updated if needed

N/A - Development dependency updates typically don't require README updates unless there are breaking changes requiring developer action.

✅ API docs updated

N/A - No API changes.

✅ Inline comments for complex logic

N/A - No code logic changed.

⚠️ CHANGELOG.md updated

Not visible in this diff. For a major version bump of a development dependency (25.x → 26.x), consider adding an entry to CHANGELOG.md if it's significant enough or if there are formatting changes that result from this update.

✅ Markdown files formatting

N/A - No markdown files modified in this PR.

Security

✅ No hardcoded credentials

No credentials present.

✅ Input validation implemented

N/A - No input handling code changed.

✅ Proper error handling

N/A - No error handling code changed.

✅ No sensitive data in logs

N/A - No logging code changed.

✅ No license files checked in

No .lic files or AQAAAD strings detected in the diff.

---

Summary

Overall Assessment: ✅ APPROVED with minor recommendations

This is a clean dependency update PR that bumps the black code formatter from version 25.1.0 to 26.1.0. The change is minimal and low-risk.

Recommendations:

1. Ensure CI/CD pipeline passes with the new black version
2. Consider running black across the codebase after merging to catch any formatting rule changes
3. If this major version bump introduces notable formatting changes, consider documenting in CHANGELOG.md

No blocking issues identified.

Automated code review analyzing defects and coding standards

[github-actions]

🤖 Claude Code Review

Code Review Results

Overview

This PR updates the black code formatter from version 25.1.0 to 26.1.0 in the development dependencies.

Detailed Analysis

Code Quality ✅

• Style guide compliance: ✅ This is a dependency version update, no code changes
• No commented-out code: ✅ Not applicable (dependency file)
• Meaningful variable names: ✅ Not applicable
• DRY principle: ✅ Not applicable
• Defects: ✅ No defects identified - this is a straightforward dependency version bump
• Project memory (.claude/CLAUDE.md): ✅ Not applicable to dependency updates

Testing ⚠️

• Unit tests for new functions: ⚠️ No tests added, but this is a development dependency update
• Integration tests for new endpoints: ⚠️ Not applicable
• Edge cases covered: ⚠️ Not applicable
• Test coverage > 80%: ⚠️ Cannot determine from diff - recommend running coverage check

Recommendation: Since black is a code formatter, it's worth running the test suite to ensure the new version doesn't cause any unexpected issues, though this is unlikely.

Documentation ⚠️

• Readme updated if needed: ⚠️ No README changes - typically not needed for dev dependency updates
• API docs updated: ✅ Not applicable
• Inline comments for complex logic: ✅ Not applicable
• CHANGELOG.md updated: ❌ CHANGELOG.md should be updated to document this dependency version change
• Markdown formatting: ✅ Not applicable to this change

Action Required: Update CHANGELOG.md to document the black version bump.

Security ✅

• No hardcoded credentials: ✅ Not applicable
• Input validation: ✅ Not applicable
• Proper error handling: ✅ Not applicable
• No sensitive data in logs: ✅ Not applicable
• No license files (.lic) or AQAAAD strings: ✅ None detected

Summary

Overall Assessment: ✅ APPROVED with minor recommendation

This is a clean dependency update for a development tool. The change is low-risk since black is only used during development for code formatting.

Required Actions:

1. ❌ Update CHANGELOG.md to document the dependency version change (development-requirements.txt:2)

Recommended Actions:

1. Run the test suite to verify compatibility with black 26.1.0
2. Run black on the codebase to ensure it formats correctly with the new version
3. Consider reviewing black's release notes for version 26.1.0 to understand any breaking changes or new features: https://github.com/psf/black/releases

Risk Level: Low - This is a development dependency that only affects code formatting during development.

Automated code review analyzing defects and coding standards

[github-actions]

🤖 Claude Code Review

---

✅ Code Review: Black Version Bump (25.1.0 → 26.1.0)

This is a straightforward dependency update for the Python code formatter black in the development requirements file.

Code Quality

• ✅ Code follows style guide: This change updates a development dependency version. No code style issues.
• ✅ No commented-out code: None present in the diff.
• ✅ Meaningful variable names: N/A - this is a dependency version update.
• ✅ DRY principle followed: N/A - this is a dependency version update.
• ✅ Identify Defects: No bugs, logic errors, or vulnerabilities introduced. This is a minor version bump of a development-only formatter tool.
• ✅ Project memory configuration: No .claude/CLAUDE.md file exists in this project.

File: development-requirements.txt:2

Testing

• ✅ Unit tests for new functions: N/A - dependency update only.
• ✅ Integration tests: N/A - black is a development tool, not production code.
• ✅ Edge cases covered: N/A
• ✅ Test coverage > 80%: N/A - this change doesn't affect test coverage.

Documentation

• ⚠️ README updated if needed: README doesn't need updates for development dependency changes.

• ⚠️ API docs updated: N/A - black is a development tool.

• ⚠️ Inline comments: N/A

• ❌ CHANGELOG.md updated: The CHANGELOG.md file at lines 9-12 shows "Unreleased" section with placeholder items ("Thing 5", "Thing 4"). This dependency update should be documented in the CHANGELOG under the "Unreleased" section or appropriate version section.

  Recommendation: Add an entry like:

  ### Changed in Unreleased
  - Updated black from 25.1.0 to 26.1.0

• ✅ Markdown files formatted: The existing README.md and CHANGELOG.md appear properly formatted with no extra whitespace issues.

Security

• ✅ No hardcoded credentials: None present.
• ✅ Input validation implemented: N/A - dependency update only.
• ✅ Proper error handling: N/A
• ✅ No sensitive data in logs: N/A
• ✅ No .lic files with AQAAAD strings: Confirmed no sensitive license credential files are checked in.

---

Summary

This is a low-risk change that updates the Black code formatter from version 25.1.0 to 26.1.0. The only issue is the missing CHANGELOG entry.

Required Action:

• ❌ Update CHANGELOG.md to document this dependency update

Notes:

• Black version 26.1.0 was released recently (January 2025) and includes minor improvements and bug fixes
• This is a development dependency, so it doesn't affect production runtime
• The change is automatically generated by Dependabot, which is a good security practice for keeping dependencies up to date

---

Automated code review analyzing defects and coding standards

[github-actions]

🤖 Claude Code Review

Code Review Results

Summary

This PR updates Python version support (removes 3.9, adds 3.13) and upgrades the black formatter from 25.1.0 to 26.1.0. This is a dependency maintenance change with minimal risk.

---

Code Quality

✅ Code follows style guide

• The changes are configuration-only (YAML and requirements.txt)
• No actual Python code is modified, so style guide compliance is not applicable
• Configuration files follow standard formatting practices

✅ No commented-out code

• No commented-out code present in the changes

✅ Meaningful variable names

• Not applicable - no new variables introduced

✅ DRY principle followed

• Not applicable - configuration changes only

✅ Identify Defects

• No defects found
• The Python version matrix update is appropriate (3.9 reached EOL in October 2025, 3.13 is the current stable release)
• Black version upgrade from 25.1.0 to 26.1.0 is a minor version bump, should be compatible
• The change is consistent with the commit message "Fix linting issue"

✅ Project memory configuration

• No .claude/CLAUDE.md file exists in this project, so this check is not applicable

---

Testing

⚠️ Unit tests for new functions

• Not applicable - No new functions added, only dependency updates
• Note: The pylint workflow will run against Python 3.10, 3.11, 3.12, and 3.13 to verify compatibility

⚠️ Integration tests for new endpoints

• Not applicable - No new endpoints added

⚠️ Edge cases covered

• Not applicable - Configuration changes only

⚠️ Test coverage > 80%

• Not applicable - No code changes affecting coverage

---

Documentation

⚠️ Readme updated if needed

• Not applicable - This change doesn't require README updates
• Python version support changes are typically documented in setup.py or pyproject.toml, not in README

⚠️ API docs updated

• Not applicable - No API changes

⚠️ Inline comments for complex logic

• Not applicable - No complex logic added

❌ CHANGELOG.md updated

• Missing: CHANGELOG.md at line 9-12 shows generic placeholder entries ("Thing 5", "Thing 4") in the Unreleased section
• Recommendation: Add an entry documenting:
  • Removed support for Python 3.9 (EOL)
  • Added support for Python 3.13
  • Updated black formatter to 26.1.0
• File: /home/runner/work/mapper-npi/mapper-npi/CHANGELOG.md:9-12

✅ Markdown files formatted with prettier

• No markdown files modified in this PR

---

Security

✅ No hardcoded credentials

• No credentials present

✅ Input validation implemented

• Not applicable - no input handling code

✅ Proper error handling

• Not applicable - no error handling code

✅ No sensitive data in logs

• Not applicable - no logging code

✅ No license files (.lic) or AQAAAD strings

• No .lic files found in the repository
• No AQAAAD strings found in tracked files (only in documentation/prompts explaining what to check for)

---

Overall Assessment

Status: ✅ APPROVED with minor recommendation

This is a clean, well-scoped maintenance PR that:

• Drops support for EOL Python 3.9
• Adds support for Python 3.13
• Updates the black formatter to the latest version

Action Items:

1. Minor: Update CHANGELOG.md to document these dependency changes (currently shows placeholder entries)

The changes are safe to merge and will be validated by the CI pipeline running pylint against all supported Python versions.

Automated code review analyzing defects and coding standards

[github-actions]

Super-linter summary

Language	Validation result
CHECKOV	Pass ✅
GITHUB_ACTIONS	Pass ✅
GITHUB_ACTIONS_ZIZMOR	Pass ✅
GITLEAKS	Pass ✅
GIT_MERGE_CONFLICT_MARKERS	Pass ✅
JSCPD	Pass ✅
PRE_COMMIT	Pass ✅
SPELL_CODESPELL	Pass ✅
TRIVY	Pass ✅
YAML	Pass ✅
YAML_PRETTIER	Pass ✅

All files and directories linted successfully

For more information, see the GitHub Actions workflow run

Powered by Super-linter

[github-actions]

🤖 Claude Code Review

I'll perform an automated code review of this pull request now.

Code Review Analysis

Code Quality

✅ Code follows style guide - The changes are minimal configuration updates to CI/CD and dependency files. No code style issues present.

✅ No commented-out code - No commented-out code in the diff.

✅ Meaningful variable names - N/A for this diff (configuration changes only).

✅ DRY principle followed - N/A for this diff (configuration changes only).

✅ Identify Defects - No bugs, logic errors, or security vulnerabilities detected. The changes are:

• .github/workflows/pylint.yaml:16 - Dropping Python 3.9 support and adding Python 3.13
• development-requirements.txt:2 - Bumping black from 25.1.0 to 26.1.0

Both changes appear intentional and safe.

Testing

⚠️ Unit tests for new functions - N/A (no new functions added)

⚠️ Integration tests for new endpoints - N/A (no new endpoints)

⚠️ Edge cases covered - N/A (no new logic)

⚠️ Test coverage > 80% - Cannot determine from diff alone, but the addition of Python 3.13 to the test matrix is positive.

Documentation

❌ README updated if needed - Dropping Python 3.9 support is a breaking change that should be documented. The README should be updated to reflect the minimum supported Python version is now 3.10.

❌ CHANGELOG.md updated - This change should be documented in CHANGELOG.md:

• Dropped support for Python 3.9
• Added support for Python 3.13
• Updated black dependency to 26.1.0

⚠️ API docs updated - N/A (no API changes)

⚠️ Inline comments for complex logic - N/A (no complex logic added)

⚠️ Markdown files follow CommonMark - No markdown files modified in this diff.

Security

✅ No hardcoded credentials - None present.

✅ Input validation implemented - N/A (no new inputs)

✅ Proper error handling - N/A (no new code)

✅ No sensitive data in logs - N/A (no logging changes)

✅ No license files (.lic) or AQAAAD strings - None detected.

---

Summary

Overall Assessment: The technical changes are sound, but documentation is incomplete.

Required Actions:

1. Update README to document minimum Python version is now 3.10 (breaking change)
2. Add entry to CHANGELOG.md documenting:
   • Dropped Python 3.9 support
   • Added Python 3.13 support
   • Bumped black to 26.1.0

Recommendations:

• Consider if dropping Python 3.9 aligns with your support policy (Python 3.9 EOL is October 2025, so this is reasonable)
• Verify that all dependencies are compatible with Python 3.13

---

Automated code review analyzing defects and coding standards

[github-actions]

Super-linter summary

Language	Validation result
CHECKOV	Pass ✅
GITHUB_ACTIONS	Pass ✅
GITHUB_ACTIONS_ZIZMOR	Pass ✅
GITLEAKS	Pass ✅
GIT_MERGE_CONFLICT_MARKERS	Pass ✅
JSCPD	Pass ✅
PRE_COMMIT	Pass ✅
SPELL_CODESPELL	Pass ✅
TRIVY	Pass ✅
YAML	Pass ✅
YAML_PRETTIER	Pass ✅

All files and directories linted successfully

For more information, see the GitHub Actions workflow run

Powered by Super-linter