Bug 1898394 - Use gecko-dev repo for Fenix and Focus Android manifests #6347
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.
Firefox 125 was the last version to use the
@mozilla-mobile/firefox-android repo. Now it is in mozilla-central, so we can use the @mozilla/gecko-dev mirror. Unfortunately, gecko-dev does not have tagged releases, so we cannot look up manifests by their version and have to use --ref instead.
Additionally, we were looking for Fenix manifests in the @mozilla-mobile/fenix repo for version < 110. However, v110 was released from the fenix repo and v111 was the first version to use the combnined @mozilla-mobile/firefox-android repo. This has been updated.
Pull Request checklist
[ci full]
to the PR title.Branch builds: add
[firefox-android: branch-name]
to the PR title.