Skip to content

Add getLivePlayStoreVersion Fastlane lane#7156

Merged
AmyLGalles merged 2 commits into
mainfrom
agalles/add-get-live-play-store-version-lane
Jul 10, 2026
Merged

Add getLivePlayStoreVersion Fastlane lane#7156
AmyLGalles merged 2 commits into
mainfrom
agalles/add-get-live-play-store-version-lane

Conversation

@AmyLGalles

Copy link
Copy Markdown
Contributor

Summary

Add a new Fastlane lane getLivePlayStoreVersion that checks for actually published (status 'completed') versions on Google Play rather than just approved versions.

Background

With managed publishing enabled in Google Play, versions can be approved but not yet published to users. The existing getLatestPlayStoreVersion lane returns any version on the specified track, regardless of whether it's actually live.

Changes

  • Add getLivePlayStoreVersion lane to fastlane/Fastfile
  • Uses Google Play Supply API to check release status
  • Returns only versions with status "completed" (actually published to users)
  • Maintains same output format as getLatestPlayStoreVersion for compatibility

Related PRs

  • deploy: [TBD]

Testing

Tested by verifying the lane checks for status == "completed" in the Google Play release data.

Type of change

  • Bug fix
  • New feature development
  • Tech debt (refactoring, code cleanup, dependency upgrades, etc)
  • Build/deploy pipeline (DevOps)
  • Other

@AmyLGalles AmyLGalles requested review from a team and david-livefront as code owners July 10, 2026 16:29
@github-actions

github-actions Bot commented Jul 10, 2026

Copy link
Copy Markdown
Contributor

🤖 Bitwarden Claude Code Review

Overall Assessment: APPROVE

Reviewed the new getLivePlayStoreVersion Fastlane lane in fastlane/Fastfile, which uses the Google Play Supply client to return only releases with status "completed" (actually live to users) under managed publishing. The two prior review findings (incorrect track_version_codes usage and parallel-array indexing) are genuinely resolved by commit bc893fc97: the lane now reads a Track object via client.tracks(track).first and pulls name and version_codes from the same TrackRelease. This matches the established API contract in fastlane/patches/supply_custom_promote.rb, and reading materialized track data after abort_current_edit is safe.

Code Review Details

No blocking findings. The lane follows the credentials-selection and Supply-client patterns already present in the codebase.

@codecov

codecov Bot commented Jul 10, 2026

Copy link
Copy Markdown

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 85.89%. Comparing base (36c892e) to head (bc893fc).

Additional details and impacted files
@@           Coverage Diff           @@
##             main    #7156   +/-   ##
=======================================
  Coverage   85.89%   85.89%           
=======================================
  Files         927      927           
  Lines       66232    66232           
  Branches     9640     9640           
=======================================
  Hits        56892    56892           
  Misses       5887     5887           
  Partials     3453     3453           
Flag Coverage Δ
app-data 17.30% <ø> (ø)
app-ui-auth-tools 18.66% <ø> (ø)
app-ui-platform 16.83% <ø> (ø)
app-ui-vault 28.06% <ø> (ø)
authenticator 6.14% <ø> (ø)
lib-core-network-bridge 4.05% <ø> (ø)
lib-data-ui 1.12% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Harness.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
  • 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

Comment thread fastlane/Fastfile Outdated
Comment thread fastlane/Fastfile Outdated
@mpbw2 mpbw2 added the t:ci Change Type - Updates to automated workflows label Jul 10, 2026
@AmyLGalles AmyLGalles marked this pull request as draft July 10, 2026 17:45
This lane checks for actually published (status 'completed') versions on Google Play rather than just approved versions. With managed publishing enabled, versions can be approved but not yet published to users.
@AmyLGalles AmyLGalles force-pushed the agalles/add-get-live-play-store-version-lane branch from ceb23e2 to e0fd578 Compare July 10, 2026 17:57
The previous implementation incorrectly called client.track_version_codes which returns an Array, not a Track object with .releases.

Changes:
- Use client.tracks(track) to get Track objects
- Wrap in begin_edit/abort_current_edit as required by Supply client
- Access releases directly from track_obj.releases
- Get version name directly from completed_release.name instead of parallel array lookup

This fixes the NoMethodError that would occur at runtime when trying to call .releases on an Array.
@AmyLGalles AmyLGalles marked this pull request as ready for review July 10, 2026 18:23
@AmyLGalles AmyLGalles added this pull request to the merge queue Jul 10, 2026
Merged via the queue into main with commit 23a93d7 Jul 10, 2026
26 checks passed
@AmyLGalles AmyLGalles deleted the agalles/add-get-live-play-store-version-lane branch July 10, 2026 20:52
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

t:ci Change Type - Updates to automated workflows

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants