search

he0119 / nonebot-plugin-wordcloud

适用于 NoneBot2 的词云插件
https://pypi.org/project/nonebot-plugin-wordcloud/
MIT License
86 stars 7 forks source link

chore(deps-dev): bump the development-dependencies group with 5 updates #265

Closed dependabot[bot] closed 6 months ago

dependabot[bot] commented 6 months ago

Bumps the development-dependencies group with 5 updates:

Package From To
nonebug 0.3.5 0.3.6
nonebot-adapter-onebot 2.4.1 2.4.3
pytest-asyncio 0.21.1 0.23.5.post1
httpx 0.25.2 0.27.0
gevent 23.9.1 24.2.1

Updates nonebug from 0.3.5 to 0.3.6

Release notes

Sourced from nonebug's releases.

Release 0.3.6

What's Changed

Full Changelog: https://github.com/nonebot/nonebug/compare/v0.3.5...v0.3.6

Commits
  • 20f70a4 :bookmark: bump version 0.3.6
  • 1cec9ad :sparkles: Feature: 适配 Pydantic V2 并放宽 pytest 限制 (#22)
  • 80cce51 :arrow_up: auto update by pre-commit hooks (#21)
  • 552518d :arrow_up: auto update by pre-commit hooks (#20)
  • 48d8c54 :arrow_up: auto update by pre-commit hooks (#19)
  • 0eb2ed6 :arrow_up: auto update by pre-commit hooks (#18)
  • 866166d :arrow_up: auto update by pre-commit hooks (#17)
  • 6345a32 :arrow_up: auto update by pre-commit hooks (#16)
  • 3229fb6 :construction_worker: use trusted publisher
  • See full diff in compare view


Updates nonebot-adapter-onebot from 2.4.1 to 2.4.3

Release notes

Sourced from nonebot-adapter-onebot's releases.

Release 2.4.3

What's Changed

Full Changelog: https://github.com/nonebot/adapter-onebot/compare/v2.4.2...v2.4.3

Release 2.4.2

What's Changed

Full Changelog: https://github.com/nonebot/adapter-onebot/compare/v2.4.1...v2.4.2

Commits
  • ffd17aa :bookmark: bump version 2.4.3
  • b2d9011 :arrow_up: Bump nwtgck/actions-netlify from 2 to 3 (#101)
  • a59e68b :bug: fix rich highlight error when no params
  • a438b8b :bug: Fix: 加群/添加好友请求的 comment 可能为 None (#98)
  • 8d7e6af :bookmark: bump version 2.4.2
  • f7cf515 :bug: Fix: 消息段数据采用 str 存储 (#97)
  • 8151707 :bug: Fix: 配置项无法使用字段名填写 (#96)
  • See full diff in compare view


Updates pytest-asyncio from 0.21.1 to 0.23.5.post1

Release notes

Sourced from pytest-asyncio's releases.

pytest-asyncio 0.23.5.post1

0.23.5 (2024-02-09)

  • Declare compatibility with pytest 8 #737
  • Fix typing errors with recent versions of mypy #769
  • Prevent DeprecationWarning about internal use of asyncio.get_event_loop() from affecting test cases #757

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.

pytest-asyncio 0.23.5

0.23.5 (2024-02-09)

  • Declare compatibility with pytest 8 #737
  • Fix typing errors with recent versions of mypy #769
  • Prevent DeprecationWarning about internal use of asyncio.get_event_loop() from affecting test cases #757

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.

pytest-asyncio 0.23.5a0

0.23.5 (UNRELEASED)

  • Declare compatibility with pytest 8 #737
  • Fix typing errors with recent versions of mypy #769

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.

pytest-asyncio 0.23.4

0.23.4 (2024-01-28)

  • pytest-asyncio no longer imports additional, unrelated packages during test collection #729
  • Addresses further issues that caused an internal pytest error during test collection
  • Declares incompatibility with pytest 8 #737

pytest-asyncio 0.23.4a2

0.23.4 (UNRELEASED)

  • pytest-asyncio no longer imports additional, unrelated packages during test collection #729
  • Addresses further issues that caused an internal pytest error during test collection

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.

pytest-asyncio 0.23.4a1

0.23.4 (UNRELEASED)

  • pytest-asyncio no longer imports additional, unrelated packages during test collection #729

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.

pytest-asyncio 0.23.4a0

... (truncated)

Commits
  • b22d84e [docs] Fixes the example showing how to run all tests in a session-scoped loop.
  • f1de446 Build(deps): Bump hypothesis in /dependencies/default
  • b60649a Build(deps): Bump urllib3 from 2.2.0 to 2.2.1 in /dependencies/docs
  • 4baec47 Build(deps): Bump typing-extensions in /dependencies/default
  • d44e3ac Build(deps): Bump pytest from 8.0.0 to 8.0.2 in /dependencies/default
  • cefa62e Build(deps): Bump coverage from 7.4.1 to 7.4.3 in /dependencies/default
  • 2908860 Build(deps): Bump hypothesis in /dependencies/default
  • 20bd7d8 Build(deps): Bump pypa/gh-action-pypi-publish from 1.8.11 to 1.8.12
  • 3aef605 [build] Update actions/upload-artifact and actions/download-artifact to v4.
  • 4b1908d [fix] Prevent DeprecationWarning from bubbling to user code.
  • Additional commits viewable in compare view


Updates httpx from 0.25.2 to 0.27.0

Release notes

Sourced from httpx's releases.

Version 0.27.0

0.27.0 (21st February, 2024)

Deprecated

  • The app=... shortcut has been deprecated. Use the explicit style of transport=httpx.WSGITransport() or transport=httpx.ASGITransport() instead.

Fixed

  • Respect the http1 argument while configuring proxy transports. (#3023)
  • Fix RFC 2069 mode digest authentication. (#3045)

Version 0.26.0

0.26.0 (20th December, 2023)

Added

  • The proxy argument was added. You should use the proxy argument instead of the deprecated proxies, or use mounts= for more complex configurations. (#2879)

Deprecated

  • The proxies argument is now deprecated. It will still continue to work, but it will be removed in the future. (#2879)

Fixed

  • Fix cases of double escaping of URL path components. Allow / as a safe character in the query portion. (#2990)
  • Handle NO_PROXY envvar cases when a fully qualified URL is supplied as the value. (#2741)
  • Allow URLs where username or password contains unescaped '@'. (#2986)
  • Ensure ASGI raw_path does not include URL query component. (#2999)
  • Ensure Response.iter_text() cannot yield empty strings. (#2998)
Changelog

Sourced from httpx's changelog.

0.27.0 (21st February, 2024)

Deprecated

  • The app=... shortcut has been deprecated. Use the explicit style of transport=httpx.WSGITransport() or transport=httpx.ASGITransport() instead.

Fixed

  • Respect the http1 argument while configuring proxy transports. (#3023)
  • Fix RFC 2069 mode digest authentication. (#3045)

0.26.0 (20th December, 2023)

Added

  • The proxy argument was added. You should use the proxy argument instead of the deprecated proxies, or use mounts= for more complex configurations. (#2879)

Deprecated

  • The proxies argument is now deprecated. It will still continue to work, but it will be removed in the future. (#2879)

Fixed

  • Fix cases of double escaping of URL path components. Allow / as a safe character in the query portion. (#2990)
  • Handle NO_PROXY envvar cases when a fully qualified URL is supplied as the value. (#2741)
  • Allow URLs where username or password contains unescaped '@'. (#2986)
  • Ensure ASGI raw_path does not include URL query component. (#2999)
  • Ensure Response.iter_text() cannot yield empty strings. (#2998)
Commits


Updates gevent from 23.9.1 to 24.2.1

Commits
  • 2db2fa1 Preparing release 24.2.1
  • 60b55d0 typo.
  • e0d9705 Make cross-thread locks use native blocking and timeouts instead of spinning.
  • 31ebe75 typo
  • 989c2c0 Now that I enabled c-ares tests on all Linux builds, there is one getaddrinfo...
  • a0b3caf Update c-ares from 1.19.1 to 1.26.0
  • b00b4fb Debugging why ccache isn't being saved.
  • 90be38c Debugging why ccache isn't being saved.
  • 6764687 Debugging why ccache isn't being saved.
  • 50fc24d Updating GHA action versions; another skipped test for Appveyor.
  • 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 6 months ago

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