search

frequenz-floss / frequenz-client-base-python

Base gRPC client
https://frequenz-floss.github.io/frequenz-client-base-python/
MIT License
0 stars 3 forks source link

Bump the required group with 10 updates #66

Closed dependabot[bot] closed 2 months ago

dependabot[bot] commented 3 months ago

Bumps the required group with 10 updates:

Package From To
pydoclint 0.5.3 0.5.6
mkdocs-material 9.5.27 9.5.30
mkdocstrings[python] 0.25.1 0.25.2
frequenz-repo-config[lib] 0.9.2 0.10.0
mypy 1.10.1 1.11.1
pylint 3.2.5 3.2.6
pytest 8.2.2 8.3.2
frequenz-repo-config[extra-lint-examples] 0.9.2 0.10.0
pytest-asyncio 0.23.7 0.23.8
hypothesis 6.104.2 6.108.5

Updates pydoclint from 0.5.3 to 0.5.6

Release notes

Sourced from pydoclint's releases.

0.5.6

What's Changed

Full Changelog: https://github.com/jsh9/pydoclint/compare/0.5.5...0.5.6

0.5.5

What's Changed

Full Changelog: https://github.com/jsh9/pydoclint/compare/0.5.4...0.5.5

0.5.4

What's Changed

Full Changelog: https://github.com/jsh9/pydoclint/compare/0.5.3...0.5.4

Changelog

Sourced from pydoclint's changelog.

[0.5.6] - 2024-07-17

[0.5.5] - 2024-07-15

[0.5.4] - 2024-07-14

  • Added

    • An option --should-document-private-class-attributes (if False, private class attributes should not appear in the docstring)
    • An option --treat-property-methods-as-class-attributes (if True, @property methods are treated like class attributes and need to be documented in the class docstring)

  • Full diff

Commits
  • 94efc5f Stop trying to check folder with names ending in .py (#155)
  • 0247ef5 Improve class attr comparison logic (#154)
  • 0b750d5 Add option to treat property methods as class attributes (#153)
  • 3c39d2e Add an option for private class attributes (#149)
  • See full diff in compare view


Updates mkdocs-material from 9.5.27 to 9.5.30

Release notes

Sourced from mkdocs-material's releases.

mkdocs-material-9.5.30

  • Fixed #7380: Navigation icons disappearing on hover in Safari
  • Fixed #7367: Blog readtime computation includes SVG text content

Thanks go to @​sisp for their contributions

mkdocs-material-9.5.29

  • Updated Galician translations
  • Fixed #7362: Annotations in figure captions rendering incorrectly

Thanks go to @​mmontes11 for their contributions

mkdocs-material-9.5.28

  • Fixed #7313: Improved tooltips mounted in sidebar when feature is disabled
Changelog

Sourced from mkdocs-material's changelog.

mkdocs-material-9.5.30 (2024-07-23)

  • Fixed #7380: Navigation icons disappearing on hover in Safari
  • Fixed #7367: Blog readtime computation includes SVG text content

mkdocs-material-9.5.29 (2024-07-14)

  • Updated Galician translations
  • Fixed #7362: Annotations in figure captions rendering incorrectly

mkdocs-material-9.5.28 (2024-07-02)

  • Fixed #7313: Improved tooltips mounted in sidebar when feature is disabled

mkdocs-material-9.5.27 (2024-06-16)

  • Updated Estonian translations

mkdocs-material-9.5.26 (2024-06-06)

  • Fixed #7232: Tab switches on scroll when linking tabs (9.5.19 regression)
  • Fixed #7230: Blog author avatar broken when referring to local file

mkdocs-material-9.5.25+insiders-4.53.11 (2024-05-27)

  • Fixed projects plugin crashing when serving before building subprojects

mkdocs-material-9.5.25 (2024-05-27)

  • Fixed #7209: Tags plugin crashing on numeric tags

mkdocs-material-9.5.24+insiders-4.53.10 (2024-05-20)

  • Fixed projects plugin crashing in serve mode when disabled
  • Fixed projects plugin crashing when building nested projects

mkdocs-material-9.5.24+insiders-4.53.9 (2024-05-20)

  • Fixed #7191: Tags listings not rendering when toc_depth is changed

mkdocs-material-9.5.24 (2024-05-20)

  • Fixed #7187: Version selector title rendering issue

mkdocs-material-9.5.23 (2024-05-15)

  • Fixed #7183: Edge case in anchor navigation when using instant navigation
  • Fixed #6436: Version selector not showing version alias

mkdocs-material-9.5.22 (2024-05-12)

... (truncated)

Commits


Updates mkdocstrings[python] from 0.25.1 to 0.25.2

Release notes

Sourced from mkdocstrings[python]'s releases.

0.25.2

0.25.2 - 2024-07-25

Compare with 0.25.1

Code Refactoring

  • Give precedence to Markdown heading level (##) (2e5f89e by Timothée Mazzucotelli).
Changelog

Sourced from mkdocstrings[python]'s changelog.

0.25.2 - 2024-07-25

Compare with 0.25.1

Code Refactoring

  • Give precedence to Markdown heading level (##) (2e5f89e by Timothée Mazzucotelli).
Commits
  • afb2a2f chore: Prepare release 0.25.2
  • e7c8abd tests: Ignore deprecation warnings for now
  • 924ecd8 chore: Template upgrade
  • da216b0 ci: Ignore unused arg
  • 80ab498 chore: Clean up pytest warning filters
  • 2e5f89e refactor: Give precedence to Markdown heading level (##)
  • fb194d8 chore: Clean up get_anchors
  • 64c5ff6 chore: Improve code comments
  • 8013be4 chore: Clean up unused condition
  • See full diff in compare view


Updates frequenz-repo-config[lib] from 0.9.2 to 0.10.0

Release notes

Sourced from frequenz-repo-config[lib]'s releases.

v0.10.0

Frequenz Repository Configuration Release Notes

Summary

This release includes quite a few enhancements and bug fixes for the cookiecutter template, but most importantly a new script for migrating to new templates, generating the templates is no longer needed for upgrading.

Upgrading

Cookiecutter template

  • A new script for migrating to new templates (instead of regenerating all files) is provided. It can't handle the upgrade 100% automatically, but should make the migration process much easier and less error prone.

    To run it, the simplest way is to fetch it from GitHub and run it directly:

    curl -sSL https://raw.githubusercontent.com/frequenz-floss/frequenz-repo-config-python/v0.10.0/cookiecutter/migrate.sh | sh

    Make sure the version you want to migrate to is correct in the URL.

    For jumping multiple versions you should run the script multiple times, once for each version.

    And remember to follow any manual instructions for each run.

New Features

  • A new GitHub ruleset is provided to configure the merge queue, so branch protection rules are not needed anymore.

Enhancements

  • The generated docs now show the symbol type in the table of contents.

Cookiecutter template

  • The Markdown dependency was bumped so we don't need to add a type: ignore due to incorrect type hints.
  • The generated docs now show the symbol type in the table of contents.
  • The dependecies were updated to the latest versions.
  • Disabled some pylint checks that are already checked by other tools.
  • The generated documentation now uses symlinks for aliases, which allows deep linking when using aliases too.

Bug Fixes

  • The code example extractor relied on a bug in the upstream sybil project that was recently fixed, thus our code also needed to be fixed.

Cookiecutter template

  • Fixed a bug where the pip cache post action fails in the CI workflow because of permissions issues.
  • Make the nox-cross-arch-all job fail if any nox-cross-arch matrix job fails.
  • Fix credentials not being passed to the test-installation job in the CI workflow.

... (truncated)

Changelog

Sourced from frequenz-repo-config[lib]'s changelog.

Frequenz Repository Configuration Release Notes

Summary

This release includes quite a few enhancements and bug fixes for the cookiecutter template, but most importantly a new script for migrating to new templates, generating the templates is no longer needed for upgrading.

Upgrading

Cookiecutter template

  • A new script for migrating to new templates (instead of regenerating all files) is provided. It can't handle the upgrade 100% automatically, but should make the migration process much easier and less error prone.

    To run it, the simplest way is to fetch it from GitHub and run it directly:

    curl -sSL https://raw.githubusercontent.com/frequenz-floss/frequenz-repo-config-python/v0.10.0/cookiecutter/migrate.sh | sh

    Make sure the version you want to migrate to is correct in the URL.

    For jumping multiple versions you should run the script multiple times, once for each version.

    And remember to follow any manual instructions for each run.

New Features

  • A new GitHub ruleset is provided to configure the merge queue, so branch protection rules are not needed anymore.

Enhancements

  • The generated docs now show the symbol type in the table of contents.

Cookiecutter template

  • The Markdown dependency was bumped so we don't need to add a type: ignore due to incorrect type hints.
  • The generated docs now show the symbol type in the table of contents.
  • The dependecies were updated to the latest versions.
  • Disabled some pylint checks that are already checked by other tools.
  • The generated documentation now uses symlinks for aliases, which allows deep linking when using aliases too.

Bug Fixes

  • The code example extractor relied on a bug in the upstream sybil project that was recently fixed, thus our code also needed to be fixed.

Cookiecutter template

  • Fixed a bug where the pip cache post action fails in the CI workflow because of permissions issues.
  • Make the nox-cross-arch-all job fail if any nox-cross-arch matrix job fails.
  • Fix credentials not being passed to the test-installation job in the CI workflow.
  • Make sure credentials are configured for all jobs that check out the repository in the CI workflow.

... (truncated)

Commits
  • bfd45a8 Add pull-requests read permission to the release-notes-check workflow (#289)
  • 6aa6bc0 Prepare for the v0.10.0 release (#290)
  • 297b184 Update version in the template pyproject.toml
  • 632283d Prepare the release notes for v0.10.0 release
  • 1778ff8 Add pull-requests read permission to the release-notes-check workflow
  • 2ac253a Disable the new check-class-attributes check in pydoclint 0.5.3 (#288)
  • 1660756 Disable the new check-class-attributes check in pydoclint 0.5.3
  • 327879b Fix credentials not passed or configured the CI workflow (#286)
  • 6195bc7 Update release notes
  • bef233c Remove the TODOs from the migration
  • Additional commits viewable in compare view


Updates mypy from 1.10.1 to 1.11.1

Changelog

Sourced from mypy's changelog.

Mypy Release Notes

Next release

Mypy 1.11

We’ve just uploaded mypy 1.11 to the Python Package Index (PyPI). Mypy is a static type checker for Python. This release includes new features, performance improvements and bug fixes. You can install it as follows:

python3 -m pip install -U mypy

You can read the full documentation for this release on Read the Docs.

Support Python 3.12 Syntax for Generics (PEP 695)

Mypy now supports the new type parameter syntax introduced in Python 3.12 (PEP 695). This feature is still experimental and must be enabled with the --enable-incomplete-feature=NewGenericSyntax flag, or with enable_incomplete_feature = NewGenericSyntax in the mypy configuration file. We plan to enable this by default in the next mypy feature release.

This example demonstrates the new syntax:

# Generic function
def f[T](https://github.com/python/mypy/blob/master/x: T) -> T: ...

reveal_type(f(1))  # Revealed type is 'int'


Generic class


class C[T]:
def init(self, x: T) -> None:
self.x = x


c = C('a')
reveal_type(c.x)  # Revealed type is 'str'


Type alias


type A[T] = C[list[T]]

This feature was contributed by Jukka Lehtosalo.

Support for functools.partial

Mypy now type checks uses of functools.partial. Previously mypy would accept arbitrary arguments.

This example will now produce an error:

from functools import partial
</tr></table>

... (truncated)

Commits


Updates pylint from 3.2.5 to 3.2.6

Commits


Updates pytest from 8.2.2 to 8.3.2

Release notes

Sourced from pytest's releases.

8.3.2

pytest 8.3.2 (2024-07-24)

Bug fixes

  • #12652: Resolve regression [conda]{.title-ref} environments where no longer being automatically detected.

    -- by RonnyPfannschmidt{.interpreted-text role="user"}

8.3.1

pytest 8.3.1 (2024-07-20)

The 8.3.0 release failed to include the change notes and docs for the release. This patch release remedies this. There are no other changes.

8.3.0

pytest 8.3.0 (2024-07-20)

New features

  • #12231: Added [--xfail-tb]{.title-ref} flag, which turns on traceback output for XFAIL results.

    • If the [--xfail-tb]{.title-ref} flag is not given, tracebacks for XFAIL results are NOT shown.
    • The style of traceback for XFAIL is set with [--tb]{.title-ref}, and can be [auto|long|short|line|native|no]{.title-ref}.
    • Note: Even if you have [--xfail-tb]{.title-ref} set, you won't see them if [--tb=no]{.title-ref}.

    Some history:

    With pytest 8.0, [-rx]{.title-ref} or [-ra]{.title-ref} would not only turn on summary reports for xfail, but also report the tracebacks for xfail results. This caused issues with some projects that utilize xfail, but don't want to see all of the xfail tracebacks.

    This change detaches xfail tracebacks from [-rx]{.title-ref}, and now we turn on xfail tracebacks with [--xfail-tb]{.title-ref}. With this, the default [-rx]{.title-ref}/ [-ra]{.title-ref} behavior is identical to pre-8.0 with respect to xfail tracebacks. While this is a behavior change, it brings default behavior back to pre-8.0.0 behavior, which ultimately was considered the better course of action.

  • #12281: Added support for keyword matching in marker expressions.

    Now tests can be selected by marker keyword arguments. Supported values are int{.interpreted-text role="class"}, (unescaped) str{.interpreted-text role="class"}, bool{.interpreted-text role="class"} & None{.interpreted-text role="data"}.

    See marker examples <marker_keyword_expression_example>{.interpreted-text role="ref"} for more information.

    -- by lovetheguitar{.interpreted-text role="user"}

  • #12567: Added --no-fold-skipped command line option.

    If this option is set, then skipped tests in short summary are no longer grouped by reason but all tests are printed individually with their nodeid in the same way as other statuses.

    -- by pbrezina{.interpreted-text role="user"}

... (truncated)

Commits
  • bbcec9c Prepare release version 8.3.2
  • 78fe8b6 Merge pull request #12657 from pytest-dev/patchback/backports/8.3.x/6c806b499...
  • 238bad2 Merge pull request #12656 from RonnyPfannschmidt/fix-12652-detect-conda-env
  • ae6034a Merge pull request #12641 from pytest-dev/patchback/backports/8.3.x/c03989cee...
  • 31337ab Merge pull request #12640 from pytest-dev/update-user
  • ca3070b Merge pull request #12637 from pytest-dev/release-8.3.1
  • de98446 Prepare release version 8.3.1
  • bd0a042 Merge pull request #12636 from pytest-dev/update-release-notes
  • 664325b doc/changelog: update 8.3.0 notes
  • 19d225d Merge pull request #12635 from pytest-dev/release-8.3.0
  • Additional commits viewable in compare view


Updates frequenz-repo-config[extra-lint-examples] from 0.9.2 to 0.10.0

Release notes

Sourced from frequenz-repo-config[extra-lint-examples]'s releases.

v0.10.0

Frequenz Repository Configuration Release Notes

Summary

This release includes quite a few enhancements and bug fixes for the cookiecutter template, but most importantly a new script for migrating to new templates, generating the templates is no longer needed for upgrading.

Upgrading

Cookiecutter template

  • A new script for migrating to new templates (instead of regenerating all files) is provided. It can't handle the upgrade 100% automatically, but should make the migration process much easier and less error prone.

    To run it, the simplest way is to fetch it from GitHub and run it directly:

    curl -sSL https://raw.githubusercontent.com/frequenz-floss/frequenz-repo-config-python/v0.10.0/cookiecutter/migrate.sh | sh

    Make sure the version you want to migrate to is correct in the URL.

    For jumping multiple versions you should run the script multiple times, once for each version.

    And remember to follow any manual instructions for each run.

New Features

  • A new GitHub ruleset is provided to configure the merge queue, so branch protection rules are not needed anymore.

Enhancements

  • The generated docs now show the symbol type in the table of contents.

Cookiecutter template

  • The Markdown dependency was bumped so we don't need to add a type: ignore due to incorrect type hints.
  • The generated docs now show the symbol type in the table of contents.
  • The dependecies were updated to the latest versions.
  • Disabled some pylint checks that are already checked by other tools.
  • The generated documentation now uses symlinks for aliases, which allows deep linking when using aliases too.

Bug Fixes

  • The code example extractor relied on a bug in the upstream sybil project that was recently fixed, thus our code also needed to be fixed.

Cookiecutter template

  • Fixed a bug where the pip cache post action fails in the CI workflow because of permissions issues.
  • Make the nox-cross-arch-all job fail if any nox-cross-arch matrix job fails.
  • Fix credentials not being passed to the test-installation job in the CI workflow.

... (truncated)

Changelog

Sourced from frequenz-repo-config[extra-lint-examples]'s changelog.

Frequenz Repository Configuration Release Notes

Summary

This release includes quite a few enhancements and bug fixes for the cookiecutter template, but most importantly a new script for migrating to new templates, generating the templates is no longer needed for upgrading.

Upgrading

Cookiecutter template

  • A new script for migrating to new templates (instead of regenerating all files) is provided. It can't handle the upgrade 100% automatically, but should make the migration process much easier and less error prone.

    To run it, the simplest way is to fetch it from GitHub and run it directly:

    curl -sSL https://raw.githubusercontent.com/frequenz-floss/frequenz-repo-config-python/v0.10.0/cookiecutter/migrate.sh | sh

    Make sure the version you want to migrate to is correct in the URL.

    For jumping multiple versions you should run the script multiple times, once for each version.

    And remember to follow any manual instructions for each run.

New Features

  • A new GitHub ruleset is provided to configure the merge queue, so branch protection rules are not needed anymore.

Enhancements

  • The generated docs now show the symbol type in the table of contents.

Cookiecutter template

  • The Markdown dependency was bumped so we don't need to add a type: ignore due to incorrect type hints.
  • The generated docs now show the symbol type in the table of contents.
  • The dependecies were updated to the latest versions.
  • Disabled some pylint checks that are already checked by other tools.
  • The generated documentation now uses symlinks for aliases, which allows deep linking when using aliases too.

Bug Fixes

  • The code example extractor relied on a bug in the upstream sybil project that was recently fixed, thus our code also needed to be fixed.

Cookiecutter template

  • Fixed a bug where the pip cache post action fails in the CI workflow because of permissions issues.
  • Make the nox-cross-arch-all job fail if any nox-cross-arch matrix job fails.
  • Fix credentials not being passed to the test-installation job in the CI workflow.
  • Make sure credentials are configured for all jobs that check out the repository in the CI workflow.

... (truncated)

Commits
  • bfd45a8 Add pull-requests read permission to the release-notes-check workflow (#289)
  • 6aa6bc0 Prepare for the v0.10.0 release (#290)
  • 297b184 Update version in the template pyproject.toml
  • 632283d Prepare the release notes for v0.10.0 release
  • 1778ff8 Add pull-requests read permission to the release-notes-check workflow
  • 2ac253a Disable the new check-class-attributes check in pydoclint 0.5.3 (#288)
  • 1660756 Disable the new check-class-attributes check in pydoclint 0.5.3
  • 327879b Fix credentials not passed or configured the CI workflow (#286)
  • 6195bc7 Update release notes
  • bef233c Remove the TODOs from the migration
  • Additional commits viewable in compare view


Updates pytest-asyncio from 0.23.7 to 0.23.8

Release notes

Sourced from pytest-asyncio's releases.

pytest-asyncio 0.23.8

0.23.8 (2024-07-17)

  • Fixes a bug that caused duplicate markers in async tests #813

Known issues

As of v0.23, pytest-asyncio attaches an asyncio event loop to each item of the test suite (i.e. session, packages, modules, classes, functions) and allows tests to be run in those loops when marked accordingly. Pytest-asyncio currently assumes that async fixture scope is correlated with the new event loop scope. This prevents fixtures from being evaluated independently from the event loop scope and breaks some existing test suites (see #706). For example, a test suite may require all fixtures and tests to run in the same event loop, but have async fixtures that are set up and torn down for each module. If you're affected by this issue, please continue using the v0.21 release, until it is resolved.

Commits
  • 4be86a5 docs: Prepare release of v0.23.8.
  • 74b3a0a Build(deps): Bump exceptiongroup in /dependencies/default
  • b0009ca [build] Declare support for Python 3.13.
  • c747c7d Build(deps): Bump coverage from 7.5.4 to 7.6.0 in /dependencies/default
  • 5c40a1c Build(deps): Bump hypothesis in /dependencies/default
  • b735e8a build: Remove development dependency on Docker.
  • 91171b4 ci: Test with CPython 3.13.
  • d572138 Build(deps): Bump hypothesis in /dependencies/default
  • a89e4d7 Build(deps): Bump certifi in /dependencies/docs
  • b646cc1 [fix] Fixed a bug that causes markers to be duplicated for async test functions.
  • Additional commits viewable in compare view


Updates hypothesis from 6.104.2 to 6.108.5

Commits
  • ba21999 Bump hypothesis-python version to 6.108.5 and update changelog
  • b861d8f Merge pull request #4059 from tybug/fix-semibounded-all-children
  • cd3742b fix semi-bounded all children computation
  • 4e5a249 Bump hypothesis-python version to 6.108.4 and update changelog
  • 1c4b7e3 remove flaky part of test
  • a967e75 Merge pull request #4057 from jobh/gc-import-perfcounter
  • a442a0c Store reference to time.perf_counter for gc accounting
  • dc6b315 Bump hypothesis-python version to 6.108.3 and update changelog
  • a322908 Merge pull request #4056 from Zac-HD/misc-cleanup-again
  • b8a1e1f We only ever report strings now
  • 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 merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot show ignore conditions` will show all of the ignore conditions of the specified dependency - `@dependabot ignore major version` will 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 minor version` will 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 ` 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 ` will remove all of the ignore conditions of the specified dependency - `@dependabot unignore ` will remove the ignore condition of the specified dependency and ignore conditions
dependabot[bot] commented 2 months ago

Looks like these dependencies are updatable in another way, so this is no longer needed.