search

frequenz-floss / frequenz-api-dispatch

gRPC+protobuf specification and Python bindings for the Frequenz Dispatch API
https://frequenz-floss.github.io/frequenz-api-dispatch/
MIT License
1 stars 6 forks source link

Bump the optional group with 7 updates #155

Closed dependabot[bot] closed 6 months ago

dependabot[bot] commented 6 months ago

Updates the requirements on frequenz-api-common, black, markdown, mkdocs-material, mypy, types-markdown and pytest to permit the latest version. Updates frequenz-api-common to 0.6.0

Release notes

Sourced from frequenz-api-common's releases.

v0.6.0

Frequenz Common API Release Notes

Summary

  • Removed dependency on googleapis-common-protos in favor of internal frequenz.api.common.v1.types.Decimal, advising updates to dependencies for users previously relying on Google's types.
  • Renamed voltage and current metrics for clarity and introduced new metrics, including line-to-line voltages and Total Harmonic Distortion (THD) metrics, with updated naming conventions for simplicity and precision.

Upgrading

  • The dependency on googleapis-common-protos / googleapis/googleapis was removed, now the built-in frequenz.api.common.v1.types.Decimal is used internally instead. This is compatible with Google's type, but if you depended indirectly on Google's submodule or python packages, you may need to update your dependencies.

    Nevertheless it is strongly recommended to remove the dependency on Google repos and use the built-in frequenz.api.common.v1.types.Decimal instead if your project only uses the Decimal type from it too.

  • Voltage metrics have been renamed from METRIC_VOLTAGE_PHASE_[1|2|3] to METRIC_VOLTAGE_PHASE_[1|2|3]_N.

  • The variants in the enum Metric have been renumberd due to the addition of line-to-line voltages.

  • Current metrics have been renamed: METRIC_AC_APPARENT_CURRENT -> METRIC_AC_CURRENT METRIC_AC_APPARENT_CURRENT_PHASE_[1|2|3] -> METRIC_AC_CURRENT_PHASE_[1|2|3]

  • Metrics for Total Harmonic Distortion have been un-abbreviated: METRIC_AC_THD_CURRENT -> METRIC_AC_TOTAL_HARMONIC_DISTORTION_CURRENT METRIC_AC_THD_CURRENT_PHASE_[1|2|3] -> METRIC_AC_TOTAL_HARMONIC_DISTORTION_CURRENT_PHASE_[1|2|3]

  • Renamed SimpleMetricSample to SimpleMetricValue, because it does not contain a timestamp, so it does not represent a sample but a value.

  • Renamed AggregatedMetricSample to AggregatedMetricValue, because it does not contain a timestamp, so it does not represent a sample but a value.

  • Renamed MetricSampleVariant to MetricValueVariant.

  • Rename MetricSample.sample to MetricSample.value.

  • Rename SensorMetricSample.sample to SensorMetricSample.value.

... (truncated)

Commits
  • 08538ce Cleanup release notes for release v0.6.0 (#212)
  • 4978931 Cleanup release notes for release v0.6.0
  • af97c70 Rename [Simple|Aggregated]MetricSample to [Simple|Aggregated]MetricValue ...
  • 9ccb5b6 Rename SensorMetricSample.sample to SensorMetricSample.value
  • 5c0214d Rename MetricSample.sample to MetricSample.value
  • fbcc68b Rename MetricSampleVariant to MetricValueVariant
  • cb6cc75 Rename AggregatedMetricSample to AggregatedMetricValue
  • 56ed231 Rename SimpleMetricSample to SimpleMetricValue
  • 3a396c0 Unabbreviate THD in the Metric enum (#209)
  • 8f06c7b Unabbreviate THD in the Metric enum
  • Additional commits viewable in compare view


Updates black from 24.2.0 to 24.3.0

Release notes

Sourced from black's releases.

24.3.0

Highlights

This release is a milestone: it fixes Black's first CVE security vulnerability. If you run Black on untrusted input, or if you habitually put thousands of leading tab characters in your docstrings, you are strongly encouraged to upgrade immediately to fix CVE-2024-21503.

This release also fixes a bug in Black's AST safety check that allowed Black to make incorrect changes to certain f-strings that are valid in Python 3.12 and higher.

Stable style

  • Don't move comments along with delimiters, which could cause crashes (#4248)
  • Strengthen AST safety check to catch more unsafe changes to strings. Previous versions of Black would incorrectly format the contents of certain unusual f-strings containing nested strings with the same quote type. Now, Black will crash on such strings until support for the new f-string syntax is implemented. (#4270)
  • Fix a bug where line-ranges exceeding the last code line would not work as expected (#4273)

Performance

  • Fix catastrophic performance on docstrings that contain large numbers of leading tab characters. This fixes CVE-2024-21503. (#4278)

Documentation

  • Note what happens when --check is used with --quiet (#4236)
Changelog

Sourced from black's changelog.

24.3.0

Highlights

This release is a milestone: it fixes Black's first CVE security vulnerability. If you run Black on untrusted input, or if you habitually put thousands of leading tab characters in your docstrings, you are strongly encouraged to upgrade immediately to fix CVE-2024-21503.

This release also fixes a bug in Black's AST safety check that allowed Black to make incorrect changes to certain f-strings that are valid in Python 3.12 and higher.

Stable style

  • Don't move comments along with delimiters, which could cause crashes (#4248)
  • Strengthen AST safety check to catch more unsafe changes to strings. Previous versions of Black would incorrectly format the contents of certain unusual f-strings containing nested strings with the same quote type. Now, Black will crash on such strings until support for the new f-string syntax is implemented. (#4270)
  • Fix a bug where line-ranges exceeding the last code line would not work as expected (#4273)

Performance

  • Fix catastrophic performance on docstrings that contain large numbers of leading tab characters. This fixes CVE-2024-21503. (#4278)

Documentation

  • Note what happens when --check is used with --quiet (#4236)
Commits


Updates markdown from 3.5.2 to 3.6

Release notes

Sourced from markdown's releases.

Release 3.6

Changed

Refactor TOC Sanitation

  • All postprocessors are now run on heading content.
  • Footnote references are now stripped from heading content. Fixes #660.
  • A more robust striptags is provided to convert headings to plain text. Unlike, the markupsafe implementation, HTML entities are not unescaped.
  • The plain text name, rich html, and unescaped raw data-toc-label are saved to toc_tokens, allowing users to access the full rich text content of the headings directly from toc_tokens.
  • The value of data-toc-label is sanitized separate from heading content before being written to name. This fixes a bug which allowed markup through in certain circumstances. To access the raw unsanitized data, retrieve the value from token['data-toc-label'] directly.
  • An html.unescape call is made just prior to calling slugify so that slugify only operates on Unicode characters. Note that html.unescape is not run on name, html, or data-toc-label.
  • The functions get_name and stashedHTML2text defined in the toc extension are both deprecated. Instead, third party extensions should use some combination of the new functions run_postprocessors, render_inner_html and striptags.

Fixed

  • Include scripts/*.py in the generated source tarballs (#1430).
  • Ensure lines after heading in loose list are properly detabbed (#1443).
  • Give smarty tree processor higher priority than toc (#1440).
  • Permit carets (^) and square brackets (]) but explicitly exclude backslashes (\) from abbreviations (#1444).
  • In attribute lists (attr_list, fenced_code), quoted attribute values are now allowed to contain curly braces (}) (#1414).
Changelog

Sourced from markdown's changelog.

[3.6] -- 2024-03-14

Changed

Refactor TOC Sanitation

  • All postprocessors are now run on heading content.
  • Footnote references are now stripped from heading content. Fixes #660.
  • A more robust striptags is provided to convert headings to plain text. Unlike, the markupsafe implementation, HTML entities are not unescaped.
  • The plain text name, rich html, and unescaped raw data-toc-label are saved to toc_tokens, allowing users to access the full rich text content of the headings directly from toc_tokens.
  • The value of data-toc-label is sanitized separate from heading content before being written to name. This fixes a bug which allowed markup through in certain circumstances. To access the raw unsanitized data, retrieve the value from token['data-toc-label'] directly.
  • An html.unescape call is made just prior to calling slugify so that slugify only operates on Unicode characters. Note that html.unescape is not run on name, html, or data-toc-label.
  • The functions get_name and stashedHTML2text defined in the toc extension are both deprecated. Instead, third party extensions should use some combination of the new functions run_postprocessors, render_inner_html and striptags.

Fixed

  • Include scripts/*.py in the generated source tarballs (#1430).
  • Ensure lines after heading in loose list are properly detabbed (#1443).
  • Give smarty tree processor higher priority than toc (#1440).
  • Permit carets (^) and square brackets (]) but explicitly exclude backslashes (\) from abbreviations (#1444).
  • In attribute lists (attr_list, fenced_code), quoted attribute values are now allowed to contain curly braces (}) (#1414).
Commits
  • e524b8f Bump version to 3.6
  • 3d8afc6 Allow attr_list quoted values to contain curly braces
  • 9edba85 Refactor abbr escaping
  • e4ab4a6 Refactor TOC sanitation
  • a18765c Explicitly omit carot and backslash from abbr
  • 421f1e8 Give smarty tree processor higher priority than toc
  • c334a3e Ensure lines after heading in loose list are properly detabbed
  • ea92856 Update the license template so GitHub can detect it
  • a2effd6 Disable mkdocstrings show_symbol_type_toc option to work around searching iss...
  • 91f9a12 Restore Attribute symbol type in mkdocstrings template
  • Additional commits viewable in compare view


Updates mkdocs-material from 9.5.12 to 9.5.17

Release notes

Sourced from mkdocs-material's releases.

mkdocs-material-9.5.17

  • Updated Serbian translations
  • Fixed #7003: Confusing keyboard interaction for palette toggle
  • Fixed #7001: Blog posts now show time by default (9.5.16 regression)
  • Fixed edge case in backport of social plugin font loading logic

mkdocs-material-9.5.16

  • Updated Russian translations
  • Improved error handling and reporting in social plugin
  • Improved error handling and reporting in privacy plugin
  • Fixed blog plugin not allowing to use time in format strings
  • Fixed #6983: Social plugin crashes because of Google Fonts API change

Thanks to @​kamilkrzyskow, @​Guts, @​szg-alex-payne and @​natakazakova for their contributions

mkdocs-material-9.5.15

  • Reverted fix for transparent iframes (9.5.14)
  • Fixed #6929: Interference of social plugin and auto dark mode
  • Fixed #6938: Giscus shows dark background in light mode (9.5.14 regression)

mkdocs-material-9.5.14

  • Added support for hiding versions from selector when using mike
  • Added init system to improve signal handling in Docker image
  • Fixed edge cases in exclusion logic of info plugin
  • Fixed inability to reset pipeline in search plugin
  • Fixed syntax error in Finnish translations
  • Fixed #6917: UTF-8 encoding problems in blog plugin on Windows
  • Fixed #6889: Transparent iframes get background color

Thanks to @​kamilkrzyskow, @​yubiuser and @​todeveni for their contributions

mkdocs-material-9.5.13

  • Updated Slovak translations
  • Improved info plugin interop with projects plugin
  • Improved info plugin inclusion/exclusion logic
  • Fixed info plugin not gathering files recursively
  • Fixed #6750: Ensure info plugin packs up all necessary files

Thanks to @​kamilkrzyskow and @​scepka for their contributions

Changelog

Sourced from mkdocs-material's changelog.

mkdocs-material-9.5.17+insiders-4.53.5 (2024-04-02)

  • Fixed social plugin crashing when no colors are specified in palettes

mkdocs-material-9.5.17 (2024-04-02)

  • Updated Serbian translations
  • Fixed #7003: Confusing keyboard interaction for palette toggle
  • Fixed #7001: Blog posts now show time by default (9.5.16 regression)
  • Fixed edge case in backport of social plugin font loading logic

mkdocs-material-9.5.16+insiders-4.53.4 (2024-03-31)

  • Fixed #6973: Escaping issue in tags extra files deprecation helper

mkdocs-material-9.5.16 (2024-03-31)

  • Updated Russian translations
  • Improved error handling and reporting in social plugin
  • Improved error handling and reporting in privacy plugin
  • Fixed blog plugin not allowing to use time in format strings
  • Fixed #6983: Social plugin crashes because of Google Fonts API change

mkdocs-material-9.5.15+insiders-4.53.3 (2024-03-23)

  • Added support for font variants in social plugin
  • Improved resilience of font resolution in social plugin
  • Fixed tag listing sometimes not being auto-populated
  • Fixed tag listing scope not being correctly resolved
  • Fixed #6941: Meta plugin adding duplicate entries
  • Fixed #6928: Social plugin crashes for some fonts

mkdocs-material-9.5.15 (2024-03-23)

  • Reverted fix for transparent iframes (9.5.14)
  • Fixed #6929: Interference of social plugin and auto dark mode
  • Fixed #6938: Giscus shows dark background in light mode (9.5.14 regression)

mkdocs-material-9.5.14+insiders-4.53.2 (2024-03-18)

  • Fixed abort on first non-matching configuration in preview extension
  • Fixed #6914: Meta files take precedence over front matter

mkdocs-material-9.5.14 (2024-03-18)

  • Added support for hiding versions from selector when using mike
  • Added init system to improve signal handling in Docker image
  • Fixed edge cases in exclusion logic of info plugin
  • Fixed inability to reset pipeline in search plugin
  • Fixed syntax error in Finnish translations

... (truncated)

Commits
  • 570161a Prepare 9.5.17 release
  • 78e93ac Improved keyboard interactions for palette toggle
  • a3655e8 Updated Serbian translations
  • 1041766 Fixed time sneaking into default post format string
  • e741f80 Documentation
  • 7e13ae6 Fix typos
  • 7d6d8d7 Updated slugify documentation
  • e71f00b Fixed backporting of social plugin font loading logic
  • 8956524 Updated Insiders changelog
  • 0db4e66 Updated changelog
  • Additional commits viewable in compare view


Updates mypy from 1.8.0 to 1.9.0

Changelog

Sourced from mypy's changelog.

Mypy Release Notes

Mypy 1.9

We’ve just uploaded mypy 1.9 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.

Breaking Changes

Because the version of typeshed we use in mypy 1.9 doesn't support 3.7, neither does mypy 1.9. (Jared Hance, PR 16883)

We are planning to enable local partial types (enabled via the --local-partial-types flag) later this year by default. This change was announced years ago, but now it's finally happening. This is a major backward-incompatible change, so we'll probably include it as part of the upcoming mypy 2.0 release. This makes daemon and non-daemon mypy runs have the same behavior by default.

Local partial types can also be enabled in the mypy config file:

local_partial_types = True

We are looking at providing a tool to make it easier to migrate projects to use --local-partial-types, but it's not yet clear whether this is practical. The migration usually involves adding some explicit type annotations to module-level and class-level variables.

Basic Support for Type Parameter Defaults (PEP 696)

This release contains new experimental support for type parameter defaults (PEP 696). Please try it out! This feature was contributed by Marc Mueller.

Since this feature will be officially introduced in the next Python feature release (3.13), you will need to import TypeVar, ParamSpec or TypeVarTuple from typing_extensions to use defaults for now.

This example adapted from the PEP defines a default for BotT:

from typing import Generic
from typing_extensions import TypeVar

class Bot: ...


BotT = TypeVar("BotT", bound=Bot, default=Bot)
</tr></table>

... (truncated)

Commits


Updates types-markdown from 3.5.0.20240129 to 3.6.0.20240316

Commits


Updates pytest from 8.0.2 to 8.1.1

Release notes

Sourced from pytest's releases.

8.1.1

pytest 8.1.1 (2024-03-08)

::: {.note} ::: {.title} Note :::

This release is not a usual bug fix release -- it contains features and improvements, being a follow up to 8.1.0, which has been yanked from PyPI. :::

Features

  • #11475: Added the new consider_namespace_packages{.interpreted-text role="confval"} configuration option, defaulting to False.

    If set to True, pytest will attempt to identify modules that are part of namespace packages when importing modules.

  • #11653: Added the new verbosity_test_cases{.interpreted-text role="confval"} configuration option for fine-grained control of test execution verbosity. See Fine-grained verbosity <pytest.fine_grained_verbosity>{.interpreted-text role="ref"} for more details.

Improvements

  • #10865: pytest.warns{.interpreted-text role="func"} now validates that warnings.warn{.interpreted-text role="func"} was called with a [str]{.title-ref} or a [Warning]{.title-ref}. Currently in Python it is possible to use other types, however this causes an exception when warnings.filterwarnings{.interpreted-text role="func"} is used to filter those warnings (see [CPython #103577](python/cpython#103577) for a discussion). While this can be considered a bug in CPython, we decided to put guards in pytest as the error message produced without this check in place is confusing.

  • #11311: When using --override-ini for paths in invocations without a configuration file defined, the current working directory is used as the relative directory.

    Previoulsy this would raise an AssertionError{.interpreted-text role="class"}.

  • #11475: --import-mode=importlib <import-mode-importlib>{.interpreted-text role="ref"} now tries to import modules using the standard import mechanism (but still without changing :pysys.path{.interpreted-text role="data"}), falling back to importing modules directly only if that fails.

    This means that installed packages will be imported under their canonical name if possible first, for example app.core.models, instead of having the module name always be derived from their path (for example .env310.lib.site_packages.app.core.models).

  • #11801: Added the iter_parents() <_pytest.nodes.Node.iter_parents>{.interpreted-text role="func"} helper method on nodes. It is similar to listchain <_pytest.nodes.Node.listchain>{.interpreted-text role="func"}, but goes from bottom to top, and returns an iterator, not a list.

  • #11850: Added support for sys.last_exc{.interpreted-text role="data"} for post-mortem debugging on Python>=3.12.

  • #11962: In case no other suitable candidates for configuration file are found, a pyproject.toml (even without a [tool.pytest.ini_options] table) will be considered as the configuration file and define the rootdir.

  • #11978: Add --log-file-mode option to the logging plugin, enabling appending to log-files. This option accepts either "w" or "a" and defaults to "w".

    Previously, the mode was hard-coded to be "w" which truncates the file before logging.

... (truncated)

Commits
  • 81653ee Adjust changelog manually for 8.1.1
  • e60b4b9 Prepare release version 8.1.1
  • 15fbe57 [8.1.x] Revert legacy path removals (#12093)
  • 86c3aab [8.1.x] Do not import duplicated modules with --importmode=importlib (#12077)
  • 5b82b0c [8.1.x] Yank version 8.1.0 (#12076)
  • 0a53681 Merge pull request #12054 from pytest-dev/release-8.1.0
  • b9a167f Prepare release version 8.1.0
  • 00043f7 Merge pull request #12038 from bluetech/fixtures-rm-arg2index
  • f4e1025 Merge pull request #12048 from bluetech/fixture-teardown-excgroup
  • 43492f5 Merge pull request #12051 from jakkdl/test_debugging_pythonbreakpoint
  • 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
Marenz commented 6 months ago

@dependabot rebase

dependabot[bot] commented 6 months ago

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