chore(deps): update dependency apprise to v1.8.0 #23
Loading…
Reference in New Issue
No description provided.
Delete Branch "renovate/apprise-1.x"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
This PR contains the following updates:
==1.3.0->==1.8.0Release Notes
caronc/apprise (apprise)
v1.8.0Compare Source
Details
☝️ Attention Developers: there is a potential Breaking Change in this release. CLI users will not be impacted.
🛠️ Potential Breaking Change
PR #1119 involved the refactoring of all the internal file/module structure of the Apprise library. The hope is I didn't break anything in your source code 🙏 . The change was required in order to remain compatible with Python v3.11+ in conjunction with library importing and how it works under the hood. More details on the specific issue can be found here demonstrating it. The Python Issue I opened in reguards to this made it clear I needed to adapt the fix on my side and conform to a better file based structure.
The side effect of this massive change developers may see (if any at all) is just the way your
importcalls are made. If you always followed the examples provided on this GitHub project, you'll have no issues at all. However, if you got clever and leveraged some of the under-the-hood compontents Apprise is built upon, then you may have an issue. The good news is the ONLY thing impacted is the way you imported your libraries (they just slightly moved around). An example of this is someone who may have had:Documented imports still work perfectly (both before and after this major refactor) such as:
📣 New Notification Services:
n/a
💡 Features
http://attachment URLs (#1122)cache=become case sensitive too (e.gCache=will no longer be parsed).❤️ Life-Cycle Support
ClassName.pyto not include aclass ClassNameinside. Python has issues withimportandunittestreferences when this is done.unittestsbreak completely in Python v3.11 using this method making this massive refactoring essential.🐛 Bugfixes
clicksend://authentication bugfix in https://github.com/caronc/apprise/pull/1121apprise//) token length by @isometimescode in https://github.com/caronc/apprise/pull/1120Installation
Apprise is available on PyPI through pip:
New Contributors
v1.7.6Compare Source
Details
📣 New Notification Services:
💡 Features
delay=switch to aprs:// plugin (#1107)❤️ Life-Cycle Support
🐛 Bugfixes
hostparsed from user login (if present) for Emails in https://github.com/caronc/apprise/pull/1095Installation
Apprise is available on PyPI through pip:
New Contributors
v1.7.5Compare Source
Details
📣 New Notification Services:
💡 Features
❤️ Life-Cycle Support
🐛 Bugfixes
Installation
Apprise is available on PyPI through pip:
v1.7.4Compare Source
Details
📣 New Notification Services:
💡 Features
.confconfiguration file support added to CLI. This PR also resolved some documentation ambiguity in https://github.com/caronc/apprise/pull/1080❤️ Life-Cycle Support
🐛 Bugfixes
Apprise is available on PyPI through pip:
v1.7.3Compare Source
Details
Another minor release to push some outstanding bug-fixes that have accumulated and patched over the past month
📣 New Notification Services:
💡 Features
mailto://comcast.net email template added (#1059)mailto://improved custom email server handling (5ae212f)to=andfrom_addr=are no longer required in most circumstances and can be automatically determined based on basic information provided.ntfy://markdown support added (#1056)?format=markdownto format the content accordingly❤️ Life-Cycle Support
paho-mqttv2.0 was released and it's documentation for v1.6.1 was completely incompatible with it. For the stability of themqtt://plugin,paho-mqtthas been pinned to the stable v1.x release (#1065)🐛 Bugfixes
yamlfiles (#1069) - Thank you @samueltardieu.ymland.yamlfiles by default (#1073)macosx://- Update terminal-notifier notify_paths (#1052) - Thank you @joergschultzelutterApprise is available on PyPI through pip:
v1.7.2Compare Source
Details
This was just a second small release add some improvements and bug fixes
See the release notes for Apprise v1.7.0 to see all of the bells and whistles now available!
💡 Features
overflowfeaturessplitandtruncate(#1035 & #1038)❤️ Life-Cycle Support
🐛 Bugfixes
Installation Instructions
Apprise is available on PyPI through pip:
v1.7.1Compare Source
Details
This was just a small release to patch a small bug (#1032) preventing Apprise v1.7.0 from being compatible with the Apprise API.
See the release notes for Apprise v1.7.0 to see all of the bells and whistles now available!
🐛 Bugfixes
Installation Instructions
Apprise is available on PyPI through pip:
v1.7.0Compare Source
Details
📣 New Notification Services:
💡 Features
:slightly_smiling_face:(as an example) in your apprise message body and have it swap to 🙂emojis=yesand they will be ran against that service only:The below would run the title and body through the emoji engine to produce their unicode
emoji equivalent..
🚀 would become 🚀 and 👍 would become 👍
again ... 🚀 would become 🚀 and 👍 would become 👍
if set to True:
Emoji Engine is enabled by default (but can be over-ridden on a per-url base ?emojis=no
if set to False:
Emoji Engine is never enabled (regardless of URL definition)
if set to None (Default):
Emoji Engine is enabled on demand (per URL definition only)
The below will be passed through the emoji engine because the asset enabled it
by default
The below will never use the emoji engine, regardless if it is enabled or not:
tgram://) supports topics inline per target specified (#1028)tgram://{bot_token}/tgram://{bot_token}/{chat_id}/tgram://{bot_token}/{chat_id1}/{chat_id2}/{chat_id3}/tgram://{bot_token}/{chat_id}:{topic}/tgram://{bot_token}/{chat_id1}:topic1}/{chat_id2}:{topic2}/{chat_id3}:{topic3}/tgram://{bot_token}/{chat_id1}/{chat_id2}:{topic2}/{chat_id3}/discord://) support foruserandroleping support (#1004).<@​123><@​&456>@everyone❤️ Life-Cycle Support
🐛 Bugfixes
Installation Instructions
Apprise is available on PyPI through pip:
v1.6.0Compare Source
Details
📣 New Notification Services:
💡 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
usernamewould get lost and be trumped withusername2. 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@hostnameschema://username@hostnameschema://hostname?user=username&password=passwordDefault Attachment maximum attachment size changed from 5MB to 1GB (
be3baed). 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)
assign "tag1" and "tag2" to the group "group"
Group assigned to a group plus another tag
Support multi-assignments (also stackable)
both groupB and groupC would acquire tag1 and tag4
Append another tag into a group already defined
Just some URLs defined as examples
You must define a groups section
Support multi assignments:
Another way you can define your groups:
You can also just list them:
Define your tags as usual here:
❤️ Life-Cycle Support
x://in addition totweet://andtwitter://to align with re-branding (#971)?v=2to your Apprise URL to use the older API for now. (#970)🐛 Bugfixes
Installation Instructions
Apprise is available on PyPI through pip:
v1.5.0Compare Source
Details
📣 New Notification Services:
rsyslog://split from the originalsyslog://Service💡 Features
href=variable that can be set on the Apprise URL which allows you to leverage theembedpart of the API and turn yourtitleinto a hyperlink to the specified location. You can also useurl=(as an alias tohref=) (#927)bodyif at least 1attachmentwas provided. This expands the use of Apprise to not constrict you to always include abodywhen the only intent you had was to post an attachment.For the CLI you are still required to set the
--bodyto "", but this no longergenerates an error
Apprise.details()improvementsattachment_supportvariable added (#916)as an example ...
import apprise
import pickle
Instantiate our object
apobj = apprise.Apprise()
Add our URLs
apobj.add("json://localhost")
apobj.add("xml://localhost")
apobj.add("form://localhost")
apobj.add("mailto://user:pass@localhost")
Now serialize our object for any purpose
serialized = pickle.dumps(apobj)
do what you will; write this to disk, send it to a remote
server, etc.
We can re-load our serialized content and turn it back into
and object like so:
apobj_n2 = pickle.loads(serialized)
v1.4.5Compare Source
Details
📣 New Notification Services:
💡 Features
pover://) (#843)ntfy://) now correctly displays attached images inline (#892)❤️ Life-Cycle Support
🐛 Bugfixes
matrix://) bugfix with the internal URL generation when aportis not provided. (#900)tgram://) correctly places attachments in thread when specified (#893)Installation Instructions
Apprise is available on PyPI through pip:
v1.4.0Compare Source
Details
💡 Features
apprise://attachment support added! 🚀 . (#873 and #877):value=keyand add data into the payload of the custom supported Apprise endpoints (JSON, FORM and XML). But now you can change the mapping of the fixed ones that were always present. Hence:message=bodywould cause the payload to no longer put themessagepassed by apprise in the hard-codedmessagefield. In this example, the payload would appear under a new tag calledbody.You can also set the values to be empty if you want to strip them from the payload. For example
:version=would eliminate theversion(previously hard-coded) payload element from the response.-
/etc/appriseamong other paths added to the default search for configuration files when theappriseCLI tool is used.tgram://Topic ID Support Added (#854)slack://Channel Support (#856)<!channel|desc>&<!channel>❤️ Life-Cycle Support
len(Service)calls #874asyncre-factoring improvements; the overhead of creating a thread-pool is now bypassed if it is detected that only one (1) notification is required to be sent. (#846)🐛 Bugfixes
.pyfiles hand-written) handling improvements. No longer is every file found interpreted. It must be a.pyfile (#853)Installation Instructions
Apprise is available on PyPI through pip:
Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR has been generated by Renovate Bot.
1d364c1ab4to06a009ca5bchore(deps): update dependency apprise to v1.4.5to chore(deps): update dependency apprise to v1.5.006a009ca5bto60a2a252a3chore(deps): update dependency apprise to v1.5.0to chore(deps): update dependency apprise to v1.6.060a2a252a3to4693694912chore(deps): update dependency apprise to v1.6.0to chore(deps): update dependency apprise to v1.7.0chore(deps): update dependency apprise to v1.7.0to chore(deps): update dependency apprise to v1.7.14693694912to8ca02fcb868ca02fcb86tobb37cd9270chore(deps): update dependency apprise to v1.7.1to chore(deps): update dependency apprise to v1.7.2bb37cd9270to009a4fb1dcchore(deps): update dependency apprise to v1.7.2to chore(deps): update dependency apprise to v1.7.3009a4fb1dctoefa5092caachore(deps): update dependency apprise to v1.7.3to chore(deps): update dependency apprise to v1.7.4efa5092caatobf863d312cchore(deps): update dependency apprise to v1.7.4to chore(deps): update dependency apprise to v1.7.5bf863d312ctoa73ea6c7c8chore(deps): update dependency apprise to v1.7.5to chore(deps): update dependency apprise to v1.7.6chore(deps): update dependency apprise to v1.7.6to chore(deps): update dependency apprise to v1.8.0a73ea6c7c8to765554d8ccStep 1:
From your project repository, check out a new branch and test the changes.Step 2:
Merge the changes and update on Gitea.