Bump the repo-config group with 2 updates#243
Conversation
Repo Config MigrationUpdate: 0.13.8 → 0.14.0 ✅ Migration completed successfully. Migration output |
llucax
left a comment
There was a problem hiding this comment.
I'm actually blocking this from merging because the v0.14.0 migration is breaking the auto-dependabot workflow again 😬
|
@dependabot recreate |
ec452de
d9b49b0 to
ec452de
Compare
|
@dependabot recreate |
ec452de to
4b2b36e
Compare
Repo Config MigrationUpdate: 0.13.8 → 0.14.0 ✅ Migration completed successfully. Migration output |
|
@dependabot recreate |
31eb7e3
2232eea to
31eb7e3
Compare
|
@dependabot rebase |
Bumps the repo-config group with 2 updates: [frequenz-repo-config[lib]](https://github.com/frequenz-floss/frequenz-repo-config-python) and [frequenz-repo-config[extra-lint-examples]](https://github.com/frequenz-floss/frequenz-repo-config-python). Updates `frequenz-repo-config[lib]` from 0.13.8 to 0.14.0 - [Release notes](https://github.com/frequenz-floss/frequenz-repo-config-python/releases) - [Changelog](https://github.com/frequenz-floss/frequenz-repo-config-python/blob/v0.x.x/RELEASE_NOTES.md) - [Commits](frequenz-floss/frequenz-repo-config-python@v0.13.8...v0.14.0) Updates `frequenz-repo-config[extra-lint-examples]` from 0.13.8 to 0.14.0 - [Release notes](https://github.com/frequenz-floss/frequenz-repo-config-python/releases) - [Changelog](https://github.com/frequenz-floss/frequenz-repo-config-python/blob/v0.x.x/RELEASE_NOTES.md) - [Commits](frequenz-floss/frequenz-repo-config-python@v0.13.8...v0.14.0) --- updated-dependencies: - dependency-name: frequenz-repo-config[lib] dependency-version: 0.14.0 dependency-type: direct:development update-type: version-update:semver-minor dependency-group: repo-config - dependency-name: frequenz-repo-config[extra-lint-examples] dependency-version: 0.14.0 dependency-type: direct:development update-type: version-update:semver-minor dependency-group: repo-config ... Signed-off-by: dependabot[bot] <support@github.com>
31eb7e3 to
ecc7584
Compare
=== v0.14.0 ========================================================= Script URL: https://raw.githubusercontent.com/frequenz-floss/frequenz-repo-config-python/v0.14.0/cookiecutter/migrate.py ======================================================================== Creating Dependabot auto-merge workflow... Created/Updated Dependabot auto-merge workflow at .github/workflows/auto-dependabot.yaml ======================================================================== Disabling CODEOWNERS review requirement in GitHub ruleset... Failed to get default branch: Command '['gh', 'api', 'repos/:owner/:repo', '--jq', '.default_branch']' returned non-zero exit status 1. >>> Failed to get default branch. Please manually disable the CODEOWNERS review requirement in the 'Protect version branches' ruleset at: GitHub repository settings > Rules ======================================================================== Updating the mkdocs.yml for mkdocstrings-python v2 compatibility... ======================================================================== Migration script finished. Remember to follow any manual instructions. ======================================================================== The migration completed successfully.
Repo Config MigrationUpdate: 0.13.8 → 0.14.0 ✅ Migration completed successfully. Migration output |
This workflow was already updated to a newer version than the one available in repo-config v0.14.0, so the migration actually rolled-back some fixes for this workflow. Signed-off-by: Leandro Lucarella <luca-frequenz@llucax.com>
|
OK, it looks like this is finally working. It needs manual approval (from someone else) now because I pushed some changes to revert updates to the auto-dependabot workflow as it already contained some fixes we'll ship in repo-config v0.15. |
llucax
left a comment
There was a problem hiding this comment.
Approving to revert the change requests, but someone else needs to approve because I'm the last pusher.
|
I don't get it, the app does have push permissions (contents: write). It doesn't have "merge queues" permissions, maybe that's needed too for merge queues? |

Bumps the repo-config group with 2 updates: frequenz-repo-config[lib] and frequenz-repo-config[extra-lint-examples].
Updates
frequenz-repo-config[lib]from 0.13.8 to 0.14.0Release notes
Sourced from frequenz-repo-config[lib]'s releases.
... (truncated)
Changelog
Sourced from frequenz-repo-config[lib]'s changelog.
... (truncated)
Commits
a72bd53Update mypy-protobuf requirement from <4,>=3.0.0 to >=3.0.0,<5 (#489)10341d6template: Bump protobuf and grpcio to latest versionsaf44767Update mypy-protobuf requirement from <4,>=3.0.0 to >=3.0.0,<58a4e067Prepare for release v0.14.0 (#490)73dc4efPrepare for release v0.14.03d86e08Bump actions/download-artifact from 5 to 6 (#460)5894e50Bump pydoclint from 0.7.3 to 0.8.3 (#477)4a81cbbBump frequenz-floss/gh-action-nox from 1.0.1 to 1.1.0 in the compatible group...41b3a2cBump pytest from 9.0.1 to 9.0.2 in the patch group (#487)c2bbc77Bump the minor group with 7 updates (#488)Updates
frequenz-repo-config[extra-lint-examples]from 0.13.8 to 0.14.0Release notes
Sourced from frequenz-repo-config[extra-lint-examples]'s releases.
... (truncated)
Changelog
Sourced from frequenz-repo-config[extra-lint-examples]'s changelog.
... (truncated)
Commits
a72bd53Update mypy-protobuf requirement from <4,>=3.0.0 to >=3.0.0,<5 (#489)10341d6template: Bump protobuf and grpcio to latest versionsaf44767Update mypy-protobuf requirement from <4,>=3.0.0 to >=3.0.0,<58a4e067Prepare for release v0.14.0 (#490)73dc4efPrepare for release v0.14.03d86e08Bump actions/download-artifact from 5 to 6 (#460)5894e50Bump pydoclint from 0.7.3 to 0.8.3 (#477)4a81cbbBump frequenz-floss/gh-action-nox from 1.0.1 to 1.1.0 in the compatible group...41b3a2cBump pytest from 9.0.1 to 9.0.2 in the patch group (#487)c2bbc77Bump the minor group with 7 updates (#488)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 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 <dependency name> major versionwill close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself)@dependabot ignore <dependency name> minor versionwill close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself)@dependabot ignore <dependency name>will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself)@dependabot unignore <dependency name>will remove all of the ignore conditions of the specified dependency@dependabot unignore <dependency name> <ignore condition>will remove the ignore condition of the specified dependency and ignore conditions