[Infra] Use strict patch versions for internal podspec dependencies #15049
Conversation
This change updates all internal podspec dependencies to use strict versioning, pinned to the patch version. - Dependencies using optimistic versioning (`~>`) are changed to strict versions (e.g., `~> 12.0.0` to `12.0.0`). - Dependencies already using exact versions pinned to the minor (e.g., `12.0`) are changed to pin to the patch version (e.g., `12.0` to `12.0.0`). This ensures that the build process uses exact versions of internal dependencies, preventing potential compatibility issues and providing more precise version control.
Using Gemini Code AssistThe 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 in your pull request via creating an issue comment (i.e. comment on the pull request page) using either
Customization To customize 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 Limitations & Feedback Gemini Code Assist is currently in preview and may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments to provide feedback. |
ncooke3
changed the title
google-oss-bot
added
api: abtesting
api: analytics
api: appcheck
api: appdistribution
api: auth
api: core
api: crashlytics
api: database
api: firebaseai
api: firestore
api: functions
api: inappmessaging
This change updates all internal podspec dependencies to float to the patch version (e.g., `~> X.Y.Z`). This allows for more flexibility in patch releases while maintaining stability for minor and major versions, as discussed in the PR feedback. - Strict versions (e.g., `X.Y.Z`) are changed to `~> X.Y.Z`. - Minor-pinned versions (e.g., `X.Y` or `~> X.Y`) are changed to `~> X.Y.0`. - Patch-pinned optimistic versions (e.g., `~> X.Y.Z`) remain unchanged.
|
@paulb777 , sorry, just happened to re-request your review right as you posted it. |
|
Merged. No CocoaPods related failures. |
This change updates all internal podspec dependencies to use strict versioning, pinned to the patch version.
~>) are changed to strict versions (e.g.,~> 12.0.0to12.0.0).12.0) are changed to pin to the patch version (e.g.,12.0to12.0.0).This ensures that the build process uses exact versions of internal dependencies, preventing potential compatibility issues and providing more precise version control.
Release tooling should handle this without further changes.