dataconnect(change): merge "X-Client-Platform" header into "X-Client-Version"

[dconeybe]

This PR updates the gRPC metadata in firebase-dataconnect by merging the X-Client-Platform header into the X-Client-Version header (formatting as android/<version>) and removing the standalone X-Client-Platform header.

This is an update to PR #8486 which was merged yesterday and added both of these headers. This update was made to accommodate the firebase-js-sdk because the "X-Client-Platform" header causes the CORS OPTIONS preflight request to fail with a 403 "Permission Denied" error due to that header being absent from Google's list of whitelisted CORS headers. See firebase/firebase-js-sdk#10217 for a few more details, if interested.

Highlights

• Header Consolidation: Merged the platform identifier into the X-Client-Version header (e.g. android/<version>) and removed the separate X-Client-Platform (x-client-platform) header.
• Test Updates: Updated integration and unit test suites to verify the new X-Client-Version header value format.

Changelog

• CHANGELOG.md
  • Updated the gRPC header entry to reference PR dataconnect(change): merge "X-Client-Platform" header into "X-Client-Version" #8495 and reflect the updated header structure.
• DataConnectGrpcMetadata.kt
  • Removed the x-client-platform header definition and updated x-client-version to format as android/$dataConnectSdkVersion.
• GrpcMetadataIntegrationTest.kt
  • Removed test assertions for x-client-platform and updated x-client-version assertions to expect android/${BuildConfig.VERSION_NAME}.
• DataConnectGrpcMetadataUnitTest.kt
  • Removed x-client-platform test cases and updated x-client-version test cases to verify the new header format.
• DataConnectGrpcRPCsUnitTest.kt
  • Removed test cases for x-client-platform and updated x-client-version assertions for executeQuery, executeMutation, and connect.

[gemini-code-assist]

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.

[github-actions]

📝 PRs merging into main branch

Our main branch should always be in a releasable state. If you are working on a larger change, or if you don't want this change to see the light of the day just yet, consider using a feature branch first, and only merge into the main branch when the code complete and ready to be released.