Bump frequenz-repo-config from 0.18.0 to 0.19.0 in the repo-config group across 1 directory

[dependabot]

Bumps the repo-config group with 1 update in the / directory: frequenz-repo-config.

Updates frequenz-repo-config from 0.18.0 to 0.19.0

Release notes

Sourced from frequenz-repo-config's releases.

v0.19.0

Frequenz Repository Configuration Release Notes

Summary

This release removes the now unnecessary DCO dummy workflow for the merge queue, enables debug mode for pytest-asyncio and exhaustive matching in mypy, makes pytest less verbose, improves the contributing guide's release steps, and brings the cookiecutter template up to date with the latest dependencies and GitHub Actions.

Upgrading

Cookiecutter template

All upgrading should be done via the migration script or regenerating the templates.

curl -sSLf https://raw.githubusercontent.com/frequenz-floss/frequenz-repo-config-python/<tag>/cookiecutter/migrate.py | python3 -I

But you might still need to adapt your code:

• Generated API projects now build their Python bindings with protobuf 7.x (grpcio-tools 1.83.0 requires it), so the runtime requirement was raised to protobuf >= 7.35.1, < 9. Consumers of the generated bindings need to be able to install protobuf 7.x.

New Features

Cookiecutter template

• Generated pyproject.toml no longer sets addopts = "-vv" under [tool.pytest.ini_options] as this is too verbose for a default.
• Generated projects enable mypy's exhaustive-match error code.
• Generated non-API projects enable asyncio debug mode during tests to provide extra runtime checks.
• Removed the dummy DCO workflow for the merge queue, as the DCO GitHub App now runs on merge_group events. The DCO required status check in the "Protect version branches" ruleset is now pinned to the DCO GitHub App; the migration script removes the workflow and updates the ruleset (via the gh CLI) for existing repositories.

Enhancements

• Improved the docstring documentation and cross-references across the frequenz.repo.config package.

Cookiecutter template

• The Releasing section of CONTRIBUTING.md now covers the milestone handling, explains that the release notes are read from the RELEASE_NOTES.md committed at the tagged commit (so they can't be cleaned up after tagging), and that the tag signature is required by the Protect released tags ruleset, which also makes released tags immutable. The migration script updates existing repositories.
• All pinned dependencies were updated to their latest versions, most notably setuptools to 84.0.0, mypy to 2.3.0, pytest to 9.1.1, pylint to 4.0.7, nox to 2026.8.10, pydoclint to 0.9.1, pytest-asyncio to 1.4.0 and flake8-datetimez to 26.8.1 (its first release in almost 6 years).
• The frequenz-sdk requirement was bumped to 1.0.0rc2211 and, for API projects, frequenz-api-common to 0.8.11, protobuf to 7.35.1 and grpcio/grpcio-tools to 1.83.0.
• All GitHub Actions used by the generated workflows were updated to their latest releases, including the major bumps of actions/checkout to v7 and actions/labeler to v7 (no configuration changes are needed for either).
• API projects now run protolint 0.56.4 in CI (up from 0.53.0), which may report new issues in existing .proto files.

Bug Fixes

• Fixed several typos and broken code examples in the docstrings.
• Fixed the building of distribution packages, which was failing with setuptools-scm was unable to detect version. When building a wheel from a source distribution there is no git repository to get the version from, so setuptools-scm 10.0.x reads it from PKG-INFO using an entry point provided by vcs-versioning, but it doesn't declare any upper bound for it. vcs-versioning 2.x dropped that entry point and moved the fallback to setuptools-scm itself, so builds started failing as soon as vcs-versioning 2.x was picked up. setuptools-scm was updated to 10.2.1, which provides the fallback again and bounds vcs-versioning to the 2.x series (backport from v0.18.2).

Cookiecutter template

• The frequenz-repo-config version pinned by the template is bumped to the version being released again. It was left pointing at 0.17.0 in the v0.18.x series, so generated projects installed an outdated frequenz-repo-config.

... (truncated)

Commits

• 14d76da Prepare for release v0.19.0 (#627)
• 4c26e2c Prepare release notes for v0.19.0
• 5e6651b Document the extra release steps of this repository
• bdc1d11 template: Bump version to the upcoming v0.19.0
• 7374efb Update template dependencies (#626)
• 450b1d8 Update release notes
• 194dad3 template: Update protolint to 0.56.4
• a5c0b21 migrate: Bump the pinned setuptools build dependency
• 4201002 template: Update GitHub Actions
• e90f2f7 template: Bump dependencies
• Additional commits viewable in compare view

[github-actions]

Repo Config Migration

Update: 0.18.0 → 0.19.0

✅ Migration completed successfully.

Migration output

=== v0.19.0 =========================================================
Script URL: https://raw.githubusercontent.com/frequenz-floss/frequenz-repo-config-python/v0.19.0/cookiecutter/migrate.py

========================================================================
Enabling exhaustive match checks for mypy...
  Updated pyproject.toml: enabled exhaustive-match
========================================================================

========================================================================
Removing default `-vv` from pytest addopts...
  Updated pyproject.toml: removed default `-vv` from [tool.pytest.ini_options]
========================================================================
Removing the dummy DCO merge-queue workflow...
  Removed .github/workflows/dco-merge-queue.yml
========================================================================
Pinning the DCO check in the 'Protect version branches' ruleset...
  Updated ruleset 'Protect version branches': pin 'DCO' status check to the DCO app
========================================================================

========================================================================
Updating pinned build dependencies...
  Updated pyproject.toml: bumped setuptools to 84.0.0, setuptools_scm[toml] to 10.2.1
========================================================================

========================================================================
Enabling asyncio debug mode for pytest...
  Updated pyproject.toml: enabled asyncio debug mode under [tool.pytest.ini_options]
========================================================================

========================================================================
Updating the release instructions in CONTRIBUTING.md...
  Updated CONTRIBUTING.md: refreshed the release instructions
========================================================================

       ✅ Migration script finished successfully ✅

Next step

Migration changes were committed and auto-merge-on-changes is disabled. Please review, approve, and merge this PR manually.

Note

If this PR needs rebasing later, comment @dependabot recreate on the PR.
This discards any current PR changes. Dependabot will regenerate the PR from the current base, and this action will detect that the migration commit is gone and re-run the migration on the recreated commit.

---

📋 Full migration logs

[llucax]

@dependabot recreate

[github-actions]

Repo Config Migration

Update: 0.18.0 → 0.19.0

✅ Migration completed successfully.

Migration output

=== v0.19.0 =========================================================
Script URL: https://raw.githubusercontent.com/frequenz-floss/frequenz-repo-config-python/v0.19.0/cookiecutter/migrate.py

========================================================================
Enabling exhaustive match checks for mypy...
  Updated pyproject.toml: enabled exhaustive-match
========================================================================

========================================================================
Removing default `-vv` from pytest addopts...
  Updated pyproject.toml: removed default `-vv` from [tool.pytest.ini_options]
========================================================================
Removing the dummy DCO merge-queue workflow...
  Removed .github/workflows/dco-merge-queue.yml
========================================================================
Pinning the DCO check in the 'Protect version branches' ruleset...
  Ruleset 'Protect version branches' is already up to date
========================================================================

========================================================================
Updating pinned build dependencies...
  Skipped pyproject.toml: build dependencies already up to date
========================================================================

========================================================================
Enabling asyncio debug mode for pytest...
  Updated pyproject.toml: enabled asyncio debug mode under [tool.pytest.ini_options]
========================================================================

========================================================================
Updating the release instructions in CONTRIBUTING.md...
  Updated CONTRIBUTING.md: refreshed the release instructions
========================================================================

       ✅ Migration script finished successfully ✅

Next step

Migration changes were committed and auto-merge-on-changes is disabled. Please review, approve, and merge this PR manually.

Note

If this PR needs rebasing later, comment @dependabot recreate on the PR.
This discards any current PR changes. Dependabot will regenerate the PR from the current base, and this action will detect that the migration commit is gone and re-run the migration on the recreated commit.

---

📋 Full migration logs

[llucax]

Failing because of the new exhaustive-match in mypy. Need some manual review and fixing.

[llucax]

Depends on #1455 now.

[llucax]

@dependabot recreate

[github-actions]

Repo Config Migration

Update: 0.18.0 → 0.19.0

✅ Migration completed successfully.

Migration output

=== v0.19.0 =========================================================
Script URL: https://raw.githubusercontent.com/frequenz-floss/frequenz-repo-config-python/v0.19.0/cookiecutter/migrate.py

========================================================================
Enabling exhaustive match checks for mypy...
  Updated pyproject.toml: enabled exhaustive-match
========================================================================

========================================================================
Removing default `-vv` from pytest addopts...
  Updated pyproject.toml: removed default `-vv` from [tool.pytest.ini_options]
========================================================================
Removing the dummy DCO merge-queue workflow...
  Removed .github/workflows/dco-merge-queue.yml
========================================================================
Pinning the DCO check in the 'Protect version branches' ruleset...
  Ruleset 'Protect version branches' is already up to date
========================================================================

========================================================================
Updating pinned build dependencies...
  Skipped pyproject.toml: build dependencies already up to date
========================================================================

========================================================================
Enabling asyncio debug mode for pytest...
  Updated pyproject.toml: enabled asyncio debug mode under [tool.pytest.ini_options]
========================================================================

========================================================================
Updating the release instructions in CONTRIBUTING.md...
  Updated CONTRIBUTING.md: refreshed the release instructions
========================================================================

       ✅ Migration script finished successfully ✅

Next step

Migration changes were committed and auto-merge-on-changes is disabled. Please review, approve, and merge this PR manually.

Note

If this PR needs rebasing later, comment @dependabot recreate on the PR.
This discards any current PR changes. Dependabot will regenerate the PR from the current base, and this action will detect that the migration commit is gone and re-run the migration on the recreated commit.

---

📋 Full migration logs