chore: Prepare for Capacitor 8 stable version#23
Merged
Conversation
Since they would be invalid until we can install Cap 8 dependencies
Not using ^8.0.0 straight away so that CI can still pass even if v8 of plugins have not been released yet.
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
2 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.
Description
Update dependencies to Capacitor 8 stable. The one exception is other plugin dependencies on example app, for which I set
^7.0.0 || ^8.0.0, so that the app can build without having other Capacitor 8 plugins in stable version - just requiring Framework. The package lock files were deleted, but I will run npm install and cap sync after Capacitor Framework v8 stable is released.PR is draft. It should only be merged after the updates mentioned in the paragraph above are done AND CI passes.
Context
https://outsystemsrd.atlassian.net/browse/RMET-4465