[GH-ISSUE #309] How to handle version name and version code in Android #4467

New Issue

GiteaMirror · 2026-06-13T12:33:04-05:00

GiteaMirror commented

2026-06-13 12:33:04 -05:00

Originally created by @srbhakta on GitHub (Jun 2, 2016).
Original GitHub issue: https://github.com/semver/semver/issues/309

How to handle version name and version code in Android

Originally created by @srbhakta on GitHub (Jun 2, 2016). Original GitHub issue: https://github.com/semver/semver/issues/309 How to handle version name and version code in Android

GiteaMirror closed this issue

2026-06-13 12:33:04 -05:00

GiteaMirror commented

2026-06-13 12:33:05 -05:00

@tdpsk commented on GitHub (Jun 19, 2016):

What I typically apply is a versionCode that represents the build number counting up from 1, as this is Google's best practice recommendation. For display purposes in the Play Store and App I apply SemVer to the versionName.

@tdpsk commented on GitHub (Jun 19, 2016): What I typically apply is a versionCode that represents the build number counting up from 1, as this is Google's best practice recommendation. For display purposes in the Play Store and App I apply SemVer to the versionName.

GiteaMirror commented

2026-06-13 12:33:05 -05:00

@jwdonahue commented on GitHub (Oct 8, 2018):

@motobhakta, unless you have additional questions, please close this issue at your earliest possible convenience.

@jwdonahue commented on GitHub (Oct 8, 2018): @motobhakta, unless you have additional questions, please close this issue at your earliest possible convenience.

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: github-starred/semver#4467