alexlebens/infrastructure
1
0
Fork 0
Code Issues 1 Pull Requests 1 Actions 6 Activity

Update caronc/apprise Docker tag to v1.3.0 #2511

Merged
alexlebens merged 1 commits from renovate/caronc-apprise-1.x into main 2025-12-14 21:11:44 +00:00
Conversation 0 Commits 1 Files Changed 3 +3 -3
renovate-bot commented 2025-12-14 20:03:16 +00:00
Collaborator
Copy Link

This PR contains the following updates:

Package Update Change
caronc/apprise minor 1.2.6 -> 1.3.0

Release Notes

caronc/apprise-api (caronc/apprise)

v1.3.0: Apprise API Release v1.3.0

Compare Source

Overview

This is a signifigant release that refactors almost the entire website giving it a much more polished/improved look.

  • Improved instructional text and layout in the configuration template.
  • Minor template clean-up and formatting alignment for the help content.
  • Updated the configuration list view to support API based calls so it can return JSON when requested,
    instead of always rendering the template.
    • This enables programmatic consumption of configuration IDs/keys.
  • The API version is now exposed in headers in addition to the Apprise library
    version, reducing confusion about the relationship between the two packages.
  • /cfg/<key> now accepts POST in addition to the previous retrieval approach acting exactly how /get/<key> POST works. /get/ would return the users configuration when it was posted to. It makes sense to use /cfg/<key> as well for users who copy/paste URL's from their Apprise API instance directly (from the browser URL). Basically /cfg/<key> is now an alias of /get/<key>
    • /get/<key> remains supported for backwards compatibility. No plans on removing this either.
  • Expanded swagger.yaml substantially to better document the service.

    • Added a dedicated docker-compose.swagger.yml to launch Swagger UI pointing
      at the repository swagger.yaml without altering Apprise-API runtime.

      docker compose -f docker-compose.swagger.yml up -d
# Browse:
#   http://localhost:8001
  • improvements to README.md
  • heath checks are now live when viewing the website
  • heavy changes to workflow:
    • development environment is now just tox -e runserver
    • improvements to linting and formatting
💡 Features
❤️ Life Cycle

Full Changelog: https://github.com/caronc/apprise-api/compare/v1.2.6...v.1.3.0

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 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 Renovate Bot.

This PR contains the following updates: | Package | Update | Change | |---|---|---| | [caronc/apprise](https://github.com/caronc/apprise-api) | minor | `1.2.6` -> `1.3.0` | --- ### Release Notes <details> <summary>caronc/apprise-api (caronc/apprise)</summary> ### [`v1.3.0`](https://github.com/caronc/apprise-api/releases/tag/v1.3.0): Apprise API Release v1.3.0 [Compare Source](https://github.com/caronc/apprise-api/compare/v1.2.6...v1.3.0) ##### Overview This is a signifigant release that refactors almost the entire website giving it a much more polished/improved look. - Improved instructional text and layout in the configuration template. - Minor template clean-up and formatting alignment for the help content. - Updated the configuration list view to support API based calls so it can return JSON when requested, instead of always rendering the template. - This enables programmatic consumption of configuration IDs/keys. - The API version is now exposed in headers in addition to the Apprise library version, reducing confusion about the relationship between the two packages. - `/cfg/<key>` now accepts `POST` in addition to the previous retrieval approach acting exactly how `/get/<key>` POST works. `/get/` would return the users configuration when it was posted to. It makes sense to use `/cfg/<key>` as well for users who copy/paste URL's from their Apprise API instance directly (from the browser URL). Basically `/cfg/<key>` is now an alias of `/get/<key>` - `/get/<key>` remains supported for backwards compatibility. No plans on removing this either. - Expanded `swagger.yaml` substantially to better document the service. - Added a dedicated `docker-compose.swagger.yml` to launch Swagger UI pointing at the repository `swagger.yaml` without altering Apprise-API runtime. ```bash docker compose -f docker-compose.swagger.yml up -d # Browse: # http://localhost:8001 ``` - improvements to README.md - heath checks are now live when viewing the website - heavy changes to workflow: - development environment is now just `tox -e runserver` - improvements to linting and formatting ##### :bulb: Features - Support HTTP\_PORT as Docker environment variable by [@&#8203;caronc](https://github.com/caronc) in [#&#8203;280](https://github.com/caronc/apprise-api/pull/280) - Massive Application Refactor by [@&#8203;caronc](https://github.com/caronc) in [#&#8203;283](https://github.com/caronc/apprise-api/pull/283) ##### :heart: Life Cycle - Bump actions/checkout from 5 to 6 in the actions group by [@&#8203;dependabot](https://github.com/dependabot)\[bot] in [#&#8203;281](https://github.com/caronc/apprise-api/pull/281) **Full Changelog**: <https://github.com/caronc/apprise-api/compare/v1.2.6...v.1.3.0> </details> --- ### 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 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. --- - [ ] <!-- rebase-check -->If you want to rebase/retry this PR, check this box --- This PR has been generated by [Renovate Bot](https://github.com/renovatebot/renovate). <!--renovate-debug:eyJjcmVhdGVkSW5WZXIiOiI0Mi4zOS4xIiwidXBkYXRlZEluVmVyIjoiNDIuMzkuMSIsInRhcmdldEJyYW5jaCI6Im1haW4iLCJsYWJlbHMiOlsiaW1hZ2UiXX0=-->
renovate-bot added the image label 2025-12-14 20:03:16 +00:00
renovate-bot force-pushed renovate/caronc-apprise-1.x from b67db75207 to e1946d4f0c 2025-12-14 20:36:12 +00:00 Compare
renovate-bot force-pushed renovate/caronc-apprise-1.x from e1946d4f0c to 318402996d 2025-12-14 21:10:49 +00:00 Compare
alexlebens merged commit 0a0de68fb2 into main 2025-12-14 21:11:44 +00:00
alexlebens deleted branch renovate/caronc-apprise-1.x 2025-12-14 21:11:47 +00:00
Sign in to join this conversation.
Reviewers
No Reviewers
Labels
Clear labels
Renovate
Issue generated by Renovate.
 automerge
This PR will be automerged by Renovate.
 chart
Chart update generated by Renovate.
 image
Image update generated by Renovate.
 stale
PR or Issue that has not been updated recently.
No Label image
Milestone
No items
No Milestone
Assignees
Clear assignees
gitea-bot renovate-bot alexlebens
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: alexlebens/infrastructure#2511
Delete Branch "renovate/caronc-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?