chore: force clean release 1.19.1 (Expo SDK 57 patches) - #104
Merged
Conversation
Force a clean release from current main so the already-merged Expo patch bumps (#103) ship in a properly-versioned AAB, without re-tagging the existing v1.19.0 (which points at the 1.18.2 commit). Release-As: 1.19.1
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Pourquoi
La release PR #100 (1.19.0) ne pouvait pas créer sa Release : le tag
v1.19.0existait déjà (créé le 29/07, pointant par erreur sur le commit release 1.18.2). En mergeant #100,mainest passé en 1.19.0 (cohérent) mais aucun AAB neuf n'a été buildé, donc les patchs Expo SDK 57 (#103) ne sont dans aucun build livré.Quoi
Commit vide portant le footer release-please
Release-As: 1.19.1. Une fois mergé, release-please ouvrira une PR release 1.19.1 → tagv1.19.1(neuf, pas de collision) → Release → build AAB signé + upload auto Play interne (versionCode = rev-list count, monotone).Aucun re-tag / suppression de la v1.19.0 existante.