Skip to content

feat!: align plugin baselines with core - #162

Open
jcesarmobile wants to merge 9 commits into
nextfrom
RMET-4723-RMET-4747
Open

feat!: align plugin baselines with core#162
jcesarmobile wants to merge 9 commits into
nextfrom
RMET-4723-RMET-4747

Conversation

@jcesarmobile

Copy link
Copy Markdown
Member

No description provided.

@changeset-bot

changeset-bot Bot commented Jul 21, 2026

Copy link
Copy Markdown

🦋 Changeset detected

Latest commit: 18d94c5

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 3 packages
Name Type
@capacitor/background-runner Major
example-app-spm Patch
example-app Patch

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

@jcesarmobile jcesarmobile changed the title chore!: Align plugin baselines with core feat!: Align plugin baselines with core Jul 23, 2026
@jcesarmobile
jcesarmobile marked this pull request as draft July 24, 2026 14:53
@OS-pedrogustavobilro OS-pedrogustavobilro self-assigned this Jul 27, 2026
@jcesarmobile
jcesarmobile changed the base branch from main to next August 27, 2026 13:33
@jcesarmobile

Copy link
Copy Markdown
Member Author

@OS-pedrogustavobilro can you remove the CI commits, those should be done on #165 (if any ot them is still missing or incorrect there)

Also the js-android-engine commits, that should be a separate PR, this PR is for updating the plugin and example apps only, the js-engine is a separate package and I left it untouched on purpose since, at least for other plugins, there were separate tickets for updating the native libraries the plugins use.

@OS-pedrogustavobilro OS-pedrogustavobilro changed the title feat!: Align plugin baselines with core feat!: align plugin baselines with core Aug 27, 2026
@OS-pedrogustavobilro

Copy link
Copy Markdown
Contributor

Ok @jcesarmobile I think everything should be good now, had to add a few commits for conflict resolution and to re-trigger CI (seems like unit-test-ios could be flaky, but well it passed this time xD and not a fault in this PR)

As for the changes to js-android-engine, I'll be opening a separate PR soon.

If all's good on your end this PR can be undrafted?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants