Bump blinker from 1.7.0 to 1.9.0 in /integrations/phishing_analyzers

[dependabot]

Bumps blinker from 1.7.0 to 1.9.0.

Release notes

Sourced from blinker's releases.

1.9.0

This is the Blinker 1.9.0 feature release. A feature release may include new features, remove previously deprecated code, add new deprecations, or introduce potentially breaking changes. We encourage everyone to upgrade, and to use a tool such as pip-tools to pin all dependencies and control upgrades. Test with warnings treated as errors to be able to adapt to deprecation warnings early.

PyPI: https://pypi.org/project/blinker/1.9.0/ Changes: https://blinker.readthedocs.io/en/stable/#version-1-9-0 Milestone: https://github.com/pallets-eco/blinker/milestone/1?closed=1

• Drop support for Python 3.8. #175
• Remove previously deprecated __version__, receiver_connected, Signal.temporarily_connected_to and WeakNamespace. #172
• Skip weakref signal cleanup if the interpreter is shutting down. #173

1.8.2

This is the Blinker 1.8.2 fix release, which fixes bugs but does not otherwise change behavior and should not result in breaking changes.

PyPI: https://pypi.org/project/blinker/1.8.2/ Changes: https://blinker.readthedocs.io/en/latest/#version-1-8-2

• Simplify type for _async_wrapper and _sync_wrapper arguments. #156

1.8.1

This is the Blinker 1.8.1 fix release, which fixes bugs but does not otherwise change behavior and should not result in breaking changes.

PyPI: https://pypi.org/project/blinker/1.8.1/ Changes: https://blinker.readthedocs.io/en/latest/#version-1-8-1

• Restore identity handling for str and int senders. #148
• Fix deprecated blinker.base.WeakNamespace import. #149
• Fix deprecated blinker.base.receiver_connected import. #153
• Use types from collections.abc instead of typing. #150
• Fully specify exported types as reported by pyright. #152

1.8.0

This is the Blinker 1.8.0 feature release, which may include new features, remove previously deprecated code, or add new deprecations. The 1.8.x line is now the supported fix branch, support has ended for the 1.7.x line. We encourage everyone to upgrade, and to use a tool such as pip-tools to pin all dependencies and control upgrades. Test with warnings treated as errors to be able to adapt to deprecation warnings early.

PyPI: https://pypi.org/project/blinker/1.8.0/ Changes: https://blinker.readthedocs.io/en/latest/#version-1-8-0

• Deprecate the __version__ attribute. Use feature detection, or importlib.metadata.version("blinker"), instead. #128
• Specify that the deprecated temporarily_connected_to will be removed in the next version.
• Show a deprecation warning for the deprecated global receiver_connected signal and specify that it will be removed in the next version.
• Show a deprecation warning for the deprecated WeakNamespace and specify that it will be removed in the next version.
• Greatly simplify how the library uses weakrefs. This is a significant change internally but should not affect any public API. #144
• Expose the namespace used by signal() as default_namespace. #145

Changelog

Sourced from blinker's changelog.

Version 1.9.0

Released 2024-11-08

• Drop support for Python 3.8. :pr:175
• Remove previously deprecated __version__, receiver_connected, Signal.temporarily_connected_to and WeakNamespace. :pr:172
• Skip weakref signal cleanup if the interpreter is shutting down. :issue:173

Version 1.8.2

Released 2024-05-06

• Simplify type for _async_wrapper and _sync_wrapper arguments. :pr:156

Version 1.8.1

Released 2024-04-28

• Restore identity handling for str and int senders. :pr:148
• Fix deprecated blinker.base.WeakNamespace import. :pr:149
• Fix deprecated blinker.base.receiver_connected import. :pr:153
• Use types from collections.abc instead of typing. :pr:150
• Fully specify exported types as reported by pyright. :pr:152

Version 1.8.0

Released 2024-04-27

• Deprecate the __version__ attribute. Use feature detection, or importlib.metadata.version("blinker"), instead. :issue:128
• Specify that the deprecated temporarily_connected_to will be removed in the next version.
• Show a deprecation warning for the deprecated global receiver_connected signal and specify that it will be removed in the next version.
• Show a deprecation warning for the deprecated WeakNamespace and specify that it will be removed in the next version.
• Greatly simplify how the library uses weakrefs. This is a significant change internally but should not affect any public API. :pr:144
• Expose the namespace used by signal() as default_namespace. :pr:145

Commits

• 669f3a0 release version 1.9.0
• cfe116f try disabling attestions on test pypi
• 16e4bd7 Merge pull request #174 from projectgus/bugfix/weakref_disconnect_shutdown
• 42561fd Fix "Exception ignored" in weakref callback during interpreter shutdown.
• dcce3e9 Merge pull request #175 from pallets-eco/drop-python3.8
• efa95ea drop support for python 3.8
• 8230518 update dev dependencies
• 94f1202 update dev dependencies
• 8c983ec remove previously deprecated code (#172)
• f5915f3 set up pre-commit lite workflow
• 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 <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

Summary by Sourcery

Enhancements:

• Remove the upper bound constraint on the blinker library.

[sourcery-ai]

Reviewer's Guide by Sourcery

This pull request bumps the blinker dependency from 1.7.0 to 1.9.0 in the integrations/phishing_analyzers/requirements.txt file. This is a dependency update for the selenium-wire library.

No diagrams generated as the changes look simple and do not need a visual representation.

File-Level Changes

Change	Details	Files
Bump blinker dependency to 1.9.0	Updated blinker from 1.7.0 to 1.9.0	integrations/phishing_analyzers/requirements.txt

---

Tips and commands

Interacting with Sourcery

• Trigger a new review: Comment @sourcery-ai review on the pull request.
• Continue discussions: Reply directly to Sourcery's review comments.
• Generate a GitHub issue from a review comment: Ask Sourcery to create an
  issue from a review comment by replying to it. You can also reply to a
  review comment with @sourcery-ai issue to create an issue from it.
• Generate a pull request title: Write @sourcery-ai anywhere in the pull
  request title to generate a title at any time. You can also comment
  @sourcery-ai title on the pull request to (re-)generate the title at any time.
• Generate a pull request summary: Write @sourcery-ai summary anywhere in
  the pull request body to generate a PR summary at any time exactly where you
  want it. You can also comment @sourcery-ai summary on the pull request to
  (re-)generate the summary at any time.
• Generate reviewer's guide: Comment @sourcery-ai guide on the pull
  request to (re-)generate the reviewer's guide at any time.
• Resolve all Sourcery comments: Comment @sourcery-ai resolve on the
  pull request to resolve all Sourcery comments. Useful if you've already
  addressed all the comments and don't want to see them anymore.
• Dismiss all Sourcery reviews: Comment @sourcery-ai dismiss on the pull
  request to dismiss all existing Sourcery reviews. Especially useful if you
  want to start fresh with a new review - don't forget to comment
  @sourcery-ai review to trigger a new review!
• Generate a plan of action for an issue: Comment @sourcery-ai plan on
  an issue to generate a plan of action for it.

Customizing Your Experience

Access your dashboard to:

• Enable or disable review features such as the Sourcery-generated pull request
  summary, the reviewer's guide, and others.
• Change the review language.
• Add, remove or edit custom review instructions.
• Adjust other review settings.

Getting Help

• Contact our support team for questions or feedback.
• Visit our documentation for detailed guides and information.
• Keep in touch with the Sourcery team by following us on X/Twitter, LinkedIn or GitHub.

[coderabbitai]

Important

Review skipped

Bot user detected.

To trigger a single review, invoke the @coderabbitai review command.

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

---

Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>, please review it.
  • Generate unit testing code for this file.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai generate unit testing code for this file.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @coderabbitai read src/utils.ts and generate unit testing code.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  • @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai generate docstrings to generate docstrings for this PR. (Beta)
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.

[sourcery-ai]

We have skipped reviewing this pull request. Here's why:

• It seems to have been created by a bot (hey, dependabot[bot]!). We assume it knows what it's doing!
• We don't review packaging changes - Let us know if you'd like us to change this.

[gitworkflows]

🎉 Snyk checks have passed. No issues have been found so far.

✅ security/snyk check is complete. No issues have been found. (View Details)

[deepsource-io]

Here's the code health analysis summary for commits 5107295..d6d5299. View details on DeepSource ↗.

Analysis Summary

Analyzer	Status	Summary	Link
Python	✅ Success		View Check ↗
Docker	✅ Success		View Check ↗

---

💡 If you’re a repository administrator, you can configure the quality gates from the settings.