Pull fenix manifests for release from m-c once 126 ships #10515
Assignees
Comments
brennie
added a commit
that referenced
this issue
May 21, 2024
Because: - there will be no futher 125.x release for Fenix; and - Fenix has merged into 126 release This commit: - stops fetching manifests from Fenix via the @mozilla-mobile/firefox-android repository; and - fetches manifests from the @mozilla/gecko-dev repository on the release branch. Fixes #10515
brennie
added a commit
that referenced
this issue
May 21, 2024
Because: - there will be no futher 125.x release for Fenix; and - Fenix has merged into 126 release This commit: - stops fetching manifests from Fenix via the @mozilla-mobile/firefox-android repository; - fetches manifests from the @mozilla/gecko-dev repository on the release branch; and - removes the `fenix_legacy` entry from apps.yaml and all references to it from manifesttool's unit tests. Fixes #10515
brennie
added a commit
that referenced
this issue
May 21, 2024
Because: - there will be no futher 125.x release for Fenix; and - Fenix has merged into 126 release This commit: - stops fetching manifests from Fenix via the @mozilla-mobile/firefox-android repository; - fetches manifests from the @mozilla/gecko-dev repository on the release branch; and - removes the `fenix_legacy` entry from apps.yaml and all references to it from manifesttool's unit tests. Fixes #10515
brennie
added a commit
that referenced
this issue
May 21, 2024
Because: - there will be no futher 125.x release for Fenix; and - Fenix has merged into 126 release This commit: - stops fetching manifests from Fenix via the @mozilla-mobile/firefox-android repository; - fetches manifests from the @mozilla/gecko-dev repository on the release branch; and - removes the `fenix_legacy` entry from apps.yaml and all references to it from manifesttool's unit tests. Fixes #10515
github-merge-queue bot
pushed a commit
that referenced
this issue
May 21, 2024
…ase (#10740) Because: - there will be no futher 125.x release for Fenix; and - Fenix has merged into 126 release This commit: - stops fetching manifests from Fenix via the @mozilla-mobile/firefox-android repository; - fetches manifests from the @mozilla/gecko-dev repository on the release branch; and - removes the `fenix_legacy` entry from apps.yaml and all references to it from manifesttool's unit tests. Fixes #10515
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Fenix is currently only on the nightly branch on m-c. Once 126 merges into release, we need to change our configurations to update from m-c for 126. At this point, we can remove the configuration that pulls from the legacy repository (@mozilla-mobile/firefox-android)
┆Issue is synchronized with this Jira Task
The text was updated successfully, but these errors were encountered: