Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

chore(release): publish #702

Merged
merged 1 commit into from
Oct 21, 2024
Merged

chore(release): publish #702

merged 1 commit into from
Oct 21, 2024

Conversation

github-actions[bot]
Copy link
Contributor

@github-actions github-actions bot commented Aug 20, 2024

This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to main, this PR will be updated.

Releases

@capacitor-firebase/firestore@6.2.0

Minor Changes

  • fd2ee14 (#705): feat: include metadata property on snapshot

Patch Changes

  • a780009 (#737): chore(ios): update Firebase pods to version 11.0

@capacitor-firebase/remote-config@6.2.0

Minor Changes

Patch Changes

  • a780009 (#737): chore(ios): update Firebase pods to version 11.0

@capacitor-firebase/analytics@6.2.0

Patch Changes

  • a780009 (#737): chore(ios): update Firebase pods to version 11.0

  • 3781386 (#704): fix(web): set correct consent settings property name

@capacitor-firebase/app@6.2.0

Patch Changes

  • a780009 (#737): chore(ios): update Firebase pods to version 11.0

@capacitor-firebase/app-check@6.2.0

Patch Changes

  • a780009 (#737): chore(ios): update Firebase pods to version 11.0

@capacitor-firebase/authentication@6.2.0

Patch Changes

  • 38fd57c (#723): chore(ios): update GoogleSignIn pod to version 7.1.0

  • 5729328 (#726): fix(android): explicitly request Google auth token with provided scopes

  • a780009 (#737): chore(ios): update Firebase pods to version 11.0

@capacitor-firebase/crashlytics@6.2.0

Patch Changes

  • a780009 (#737): chore(ios): update Firebase pods to version 11.0

  • 8b190d1 (#721): fix(ios): crash(...) method now respects message option

@capacitor-firebase/functions@6.2.0

Patch Changes

  • a780009 (#737): chore(ios): update Firebase pods to version 11.0

@capacitor-firebase/messaging@6.2.0

Patch Changes

  • a780009 (#737): chore(ios): update Firebase pods to version 11.0

@capacitor-firebase/performance@6.2.0

Patch Changes

  • a780009 (#737): chore(ios): update Firebase pods to version 11.0

@capacitor-firebase/storage@6.2.0

Patch Changes

  • a780009 (#737): chore(ios): update Firebase pods to version 11.0

@github-actions github-actions bot force-pushed the changeset-release/main branch 2 times, most recently from b9491fc to 58c5458 Compare August 30, 2024 09:16
@github-actions github-actions bot force-pushed the changeset-release/main branch 3 times, most recently from 18be5c4 to 4a23d41 Compare September 24, 2024 04:21
@NinuzIBZ
Copy link

NinuzIBZ commented Oct 8, 2024

Hey there, can this be merged?

@robingenz
Copy link
Member

@NinuzIBZ Not yet, but you can just install the pre release (e.g. https://github.com/capawesome-team/capacitor-firebase/runs/30562646330).

@NinuzIBZ
Copy link

NinuzIBZ commented Oct 8, 2024

Thank you!

@luisbytes
Copy link

Hi there, under what criteria are these changes considered ready for merging? Additionally, what are the conditions for triggering a new release? Is the release process handled for all packages simultaneously, or is it done individually?

@robingenz
Copy link
Member

@luisbytes As soon as I have the feeling that enough changes have been collected, I trigger a release. There are no specific conditions here. Since all packages are released together (to keep the version number the same), I would like to wait until nearly every package has also received changes. But as I said, with the pre releases this is not really a problem and you have the option of installing every single commit. I use them myself in production.

@github-actions github-actions bot force-pushed the changeset-release/main branch from 4a23d41 to f9a3ccb Compare October 17, 2024 06:34
@robingenz robingenz merged commit 2665fa9 into main Oct 21, 2024
@robingenz robingenz deleted the changeset-release/main branch October 21, 2024 11:56
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