Bump apprise from 1.5.0 to 1.6.0

[dependabot[bot]]

Bumps apprise from 1.5.0 to 1.6.0.

Release notes

Sourced from apprise's releases.

Release v1.6.0

Details

:mega: New Notification Services:

• Notifiarr Support added. (#953)

:bulb: Features

• mqtt:// added log entry on successful transmission for both consistency and to align with other plugins (#946)

• Refactored URLBase() object to prepare for API Webhook support in the Apprise API (#973)

• A global change to handles user= directive a better and auto-solves ambiguous situations where the URL looks like this: schema://username@hostname?user=username2 (#947).

  In the past the username would get lost and be trumped with username2. This is fine, but to may Apprise more versatile, Now in these circumstances Apprise will interpret it as: schema://password@hostname?user=username. This change does not disrupt other common formatting such as:

  • schema://username:password@hostname
  • schema://username@hostname
  • schema://hostname?user=username&password=password

• Default Attachment maximum attachment size changed from 5MB to 1GB (be3baed7e3d33bae973f1714df4ebbf65aa33f85). This just makes it easier to use the API and CLI without issues. It lets the upstream service complain if the attachment is too large instead of Apprise restricting you.

• xml:// custom URL parsing better handles customized XML elements (inserted, renamed and deleted); (#945).

• Configuration now supports Groups. You can now assign pre-defined tags to groups and trigger your notifications off of them. (#967)

  • Groups are processed at the end, so there is no requirement to define it at the front or end of your configuration files.

  • Group definitions stack as well (so defining the same group again with append any entries to what was already assigned.

  • You can assign more groups to groups

  • You can assign multiple groups in one single declaration

  • Here is a simple TEXT example:

    # assign "tag1" and "tag2" to the group "group"
    group = tag1, tag2
    Group assigned to a group plus another tag
    groupA = group, tag3
    Support multi-assignments (also stackable)
    both groupB and groupC would acquire tag1 and tag4
    groupB, groupC = tag1, tag4
    Append another tag into a group already defined
    group = tag4
    Just some URLs defined as examples
    tag1 = mailto://credentials
    tag2 = mailto://credentials
    tag3 = mailto://credentials
    tag4 = mailto://credentials
    

    If you were to send your notification to the tag group it would in fact trigger both tag1, tag2, and tag4:

    apprise -g 'group' -b "Test Message!"
    

  • Here is a simple YAML example:

... (truncated)

Commits

• 0c0d5da bumped version to v1.6.0
• bd28bf9 Notifiarr footer and icon attributes set (#977)
• 97c7af4 Matrix login URL updated to accommodate newer API (#970)
• f6b53ac Nextcloud and Nextcloud Talk url_prefix support (#975)
• 34e52e5 Switch License to BSDv2 (from v3) as it's less restrictive (#976)
• 8e54bba updated handling of parse_url secure flag check
• 480d0e0 URLBase() supports calls to url() for generic responses (#973)
• 902f39c Twitter supports x:// to align with it's new re-branding (#971)
• ae0c412 Notifiarr Support (#953)
• be73b03 type-o fixed in LICENSE
• 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 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)