Skip to content

Rebase main#18249

Closed
jamesblasco wants to merge 17 commits intofirebase:mainfrom
Sparkli-AI:sparkli-main
Closed

Rebase main#18249
jamesblasco wants to merge 17 commits intofirebase:mainfrom
Sparkli-AI:sparkli-main

Conversation

@jamesblasco
Copy link
Copy Markdown
Contributor

@jamesblasco jamesblasco commented May 5, 2026

Description

Replace this paragraph with a description of what this PR is doing. If you're modifying existing behavior, describe the existing behavior, how this PR is changing it, and what motivated the change.

Related Issues

Replace this paragraph with a list of issues related to this PR from the issue database. Indicate, which of these issues are resolved or fixed by this PR. Note that you'll have to prefix the issue numbers with flutter/flutter#.

Checklist

Before you create this PR confirm that it meets all requirements listed below by checking the relevant checkboxes ([x]).
This will ensure a smooth and quick review process. Updating the pubspec.yaml and changelogs is not required.

  • I read the Contributor Guide and followed the process outlined there for submitting PRs.
  • My PR includes unit or integration tests for all changed/updated/fixed behaviors (See Contributor Guide).
  • All existing and new tests are passing.
  • I updated/added relevant documentation (doc comments with ///).
  • The analyzer (melos run analyze) does not report any problems on my PR.
  • I read and followed the Flutter Style Guide.
  • I signed the CLA.
  • I am willing to follow-up on review comments in a timely manner.

Breaking Change

Does your PR require plugin users to manually update their apps to accommodate your change?

  • Yes, this is a breaking change.
  • No, this is not a breaking change.

jamesblasco and others added 17 commits September 2, 2025 18:50
@jamesblasco
feat: allow transcriptions
6ab68d2
@jamesblasco
feat: input transcription
20e6702
@jamesblasco
feat: gcs images
fbb4a27
@jamesblasco
Merge branch 'firebase:main' into sparkli-main
0f4a8bc
@jamesblasco
Merge branch 'firebase:main' into sparkli-main
9b7ecf1
@jamesblasco
chore: export setup complete
987591e
@jamesblasco
Merge pull request #2 from Sparkli-AI/chore/export_setup_complete
b895ae2 
chore: export setup complete
@jamesblasco
feat: allow no automatic detection
a7a6f58
@jamesblasco
feat: allow no automatic detection (#3)
cab5da0 
## Description

_Replace this paragraph with a description of what this PR is doing. If you're modifying existing behavior, describe the existing behavior, how this PR is changing it, and what motivated the change._

## Related Issues

_Replace this paragraph with a list of issues related to this PR from the_ [_issue database](https://github.com/flutter/flutter/issues). Indicate, which of these issues are resolved or fixed by this PR. Note that you'll have to prefix the issue numbers with flutter/flutter#._

## Checklist

Before you create this PR confirm that it meets all requirements listed below by checking the relevant checkboxes (`[x]`).
This will ensure a smooth and quick review process. Updating the `pubspec.yaml` and changelogs is not required.

- [ ] I read the [Contributor Guide](https://github.com/firebase/flutterfire/blob/main/CONTRIBUTING.md) and followed the process outlined there for submitting PRs.
- [ ] My PR includes unit or integration tests for _all_ changed/updated/fixed behaviors (See [Contributor Guide](https://github.com/firebase/flutterfire/blob/main/CONTRIBUTING.md)).
- [ ] All existing and new tests are passing.
- [ ] I updated/added relevant documentation (doc comments with `///`).
- [ ] The analyzer (`melos run analyze`) does not report any problems on my PR.
- [ ] I read and followed the [Flutter Style Guide](https://github.com/flutter/flutter/wiki/Style-guide-for-Flutter-repo).
- [ ] I signed the [CLA](https://cla.developers.google.com/).
- [ ] I am willing to follow-up on review comments in a timely manner.

## Breaking Change

Does your PR require plugin users to manually update their apps to accommodate your change?

- [ ] Yes, this is a breaking change.
- [ ] No, this is _not_ a breaking change.

<!-- Links -->

<!-- This is an auto-generated comment: release notes by coderabbit.ai -->

## Summary by CodeRabbit

- New Features
    - Send mixed real-time inputs (audio, video, text) in a single request.
    - Optional activity start/end markers supported in real-time payloads.
    - Optional flag to signal end of an audio stream.
    - Real-time payloads now include activity metadata when provided.
- Documentation
    - Updated guidance covering new real-time input options, activity markers, and audio stream end behavior.

<!-- end of auto-generated comment: release notes by coderabbit.ai -->
@jamesblasco
fix: export activity
96366b2
@jamesblasco
Merge pull request #4 from Sparkli-AI/feat/export_ativity
24fe10f 
chore: export_ativity
@jamesblasco
feat: add from json
268abc8
@luciemdx
Merge branch 'main' into sparkli-main
b7c3564
@jamesblasco
feat: add metadata for live api
0a3f12f
@jamesblasco
Merge pull request #9 from Sparkli-AI/feat/add_metadata_live_api
a242fdb 
feat: add metadata for live api
@jamesblasco
Merge branch 'firebase:main' into sparkli-main
0e66698
@jamesblasco
chore: export ModalityTokenCount
a4ace8d
@gemini-code-assist
Copy link
Copy Markdown
Contributor

gemini-code-assist Bot commented May 5, 2026

Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature Command Description
Code Review /gemini review Performs a code review for the current pull request in its current state.
Pull Request Summary /gemini summary Provides a summary of the current pull request in its current state.
Comment @gemini-code-assist Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help /gemini help Displays a list of available commands.

Customization

To customize the Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counterproductive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for GitHub and other Google products, sign up here.

@jamesblasco jamesblasco closed this May 5, 2026
@google-cla
Copy link
Copy Markdown

google-cla Bot commented May 5, 2026

Thanks for your pull request! It looks like this may be your first contribution to a Google open source project. Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).

View this failed invocation of the CLA check for more information.

For the most up to date status, view the checks section at the bottom of the pull request.

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

Reviewers

No reviews

Assignees

No one assigned

Labels

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

2 participants

@jamesblasco @luciemdx