feat: Capacitor 8 support#51
Merged
Merged
Conversation
BREAKING CHANGE: Capacitor major version update requires major version update on the plugin.
Closed
7 tasks
alexgerardojacinto
approved these changes
Sep 8, 2025
To fix the error below when using pnpm v10 (error on v10, warning on v9 and below) ERR_PNPM_INVALID_PEER_DEPENDENCY_SPECIFICATION The peerDependencies field named '@capacitor/core' of package '@capacitor/geolocation' has an invalid value: 'next' The values in peerDependencies should be either a valid semver range, a `workspace:` spec, or a `catalog:` spec
OS-ruimoreiramendes
approved these changes
Sep 9, 2025
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
BREAKING CHANGE: Capacitor major version update requires major version update on the plugin.
PR should be rebased for
semantic-releasetrigger 8.0.0 based onBREAKING CHANGEinside commit footer. Either that or include the "BREAKING CHANGE" in the squash message.