Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

⬆️ Update apprise to v1.8.0 #179

Merged
merged 1 commit into from
May 12, 2024
Merged

⬆️ Update apprise to v1.8.0 #179

merged 1 commit into from
May 12, 2024

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented May 11, 2024

Mend Renovate

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
apprise ==1.7.6 -> ==1.8.0 age adoption passing confidence

Release Notes

caronc/apprise (apprise)

v1.8.0

Compare 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 import calls 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:

### For example:
from apprise.plugins.NotifyEmail import NotifyEmail

### This has changed to :
from apprise.plugins.email import NotifyEmail

### All other object functionality has not changed at all

Documented imports still work perfectly (both before and after this major refactor) such as:

from apprise import Apprise
from apprise import AppriseAsset

### etc...
📣 New Notification Services:

n/a

💡 Features
  • Custom Plugin Attachment Support Enforced + Added Testing in https://github.com/caronc/apprise/pull/1115
  • Do not sanitize http:// attachment URLs (#​1122)
    • This allows the successful fetching of very complicated http based Attachment URL's where the case sensitivity of the keys matter.
    • The side effect of this change, is built in switches like cache= become case sensitive too (e.g Cache= will no longer be parsed).
❤️ Life-Cycle Support
🐛 Bugfixes

Installation

Apprise is available on PyPI through pip:

### Install Apprise v1.8.0 rom PyPI
pip install apprise==1.8.0

New Contributors


Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Enabled.

Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.


  • If you want to rebase/retry this PR, check this box

This PR has been generated by Mend Renovate. View repository job log here.

@renovate renovate bot added dependencies Upgrade or downgrade of project dependencies. no-stale This issue or PR is exempted from the stable bot. python labels May 11, 2024
@renovate renovate bot merged commit b475cfa into main May 12, 2024
24 checks passed
@renovate renovate bot deleted the renovate/apprise-1.x branch May 12, 2024 02:08
@github-actions github-actions bot locked and limited conversation to collaborators May 13, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
dependencies Upgrade or downgrade of project dependencies. no-stale This issue or PR is exempted from the stable bot.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

0 participants