Skip to content

fix(deps): update dependency @havesource/cordova-plugin-push to v7#1476

Open
renovate[bot] wants to merge 1 commit intomainfrom
renovate/havesource-cordova-plugin-push-7.x
Open

fix(deps): update dependency @havesource/cordova-plugin-push to v7#1476
renovate[bot] wants to merge 1 commit intomainfrom
renovate/havesource-cordova-plugin-push-7.x

Conversation

@renovate
Copy link
Contributor

@renovate renovate bot commented Jan 6, 2026

This PR contains the following updates:

Package Change Age Confidence
@havesource/cordova-plugin-push 6.0.17.0.0 age confidence

Release Notes

havesource/cordova-plugin-push (@​havesource/cordova-plugin-push)

v7.0.0

Compare Source

Breaking Changes:

  • feat(android)!: bump library versions (#​355)

    • androidx.core:core:1.16.0
    • com.google.firebase:firebase-messaging:24.1.0
  • feat(ios)!: bump pod Firebase/Messaging@11.8.0 (#​356)

    Note: If you are using the Cordova-iOS platform version 7.x or lower, the deployment-target config preference must be set to at least 13.0 to work with Firebase/Messaging@11.8.0.

    Example config.xml:

    <platform name="ios">
      <preference name="deployment-target" value="13.0" />
    </platform>
  • fix(android)!: also clear notifications when clearBadge is true (#​358)

    This fix ensures that notifications in the message center are also cleared when the clearBadge flag is set to true.

    Previously, the flag was only documented to clear the badge counter (or dots, in Android’s case). However, it was not possible to clear only the badge on Android. The badge counter/dot is not fully independent of notifications—attempting to clear the badge may fail if the associated notification is not also cleared. The behavior can also vary depending on the Android version or device.

    Additionally, there was an inconsistency between iOS and Android: iOS cleared both the badge and the notification, while Android attempted to clear only the badge.

    This update aligns the behavior across platforms, making it more consistent.

  • chore!: update dependencies (#​360)

    While this commit is marked as a breaking change, it primarily affects plugin development, as it increases the required Node.js engine version. This should not impact plugin usage directly, but it is still recommended to use the latest supported Node.js release, preferably the Long-Term Support (LTS) release.

Chores, CI, & Docs:

  • chore: update package-lock.json (#​361)
  • chore: move token higher and cleanup exception block (#​359)
  • ci: update workflow (#​362)
  • doc: clean & update

Configuration

📅 Schedule: Branch creation - Between 12:00 AM and 03:59 AM, only on Monday ( * 0-3 * * 1 ) in timezone America/Toronto, 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.


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

This PR was generated by Mend Renovate. View the repository job log.

@renovate renovate bot added the dependencies label Jan 6, 2026
@renovate renovate bot force-pushed the renovate/havesource-cordova-plugin-push-7.x branch from c0071ee to 746d4ad Compare January 8, 2026 19:35
@renovate renovate bot force-pushed the renovate/havesource-cordova-plugin-push-7.x branch 2 times, most recently from af00d0f to 3da5757 Compare January 23, 2026 19:16
@renovate renovate bot force-pushed the renovate/havesource-cordova-plugin-push-7.x branch from 3da5757 to 8413595 Compare February 2, 2026 17:14
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant