afa75715af
When we migrated l10n to github in https://bugzilla.mozilla.org/show_bug.cgi?id=1900421 I switched these files away from referencing `default` (which would no longer be valid in the git world) to use a concrete ref "to avoid breaking repacks before l10n bumper runs". At this point it's unclear to me why I didn't use `main` instead, to continue taking the latest strings without the need to bump this file. I have a vague memory of thinking it was ideal to use concrete refs to make things work better on non-latest branch, but I don't think that holds water: we only have one branch in the strings repository, and as far as I know it's totally backwards compatible. This patch switches the `onchange` files back to using a branch ref rather than a concrete rev. It would be possible to fix this issue by bumping the `onchange` files in addition to the regular ones, but unless we can find some actual benefit to doing so, using branch refs seems preferable. Differential Revision: https://phabricator.services.mozilla.com/D243826
35 lines
662 B
JSON
35 lines
662 B
JSON
{
|
|
"en-CA": {
|
|
"platforms": [
|
|
"android",
|
|
"android-arm",
|
|
"android-multilocale"
|
|
],
|
|
"revision": "main"
|
|
},
|
|
"he": {
|
|
"platforms": [
|
|
"android",
|
|
"android-arm",
|
|
"android-multilocale"
|
|
],
|
|
"revision": "main"
|
|
},
|
|
"it": {
|
|
"platforms": [
|
|
"android",
|
|
"android-arm",
|
|
"android-multilocale"
|
|
],
|
|
"revision": "main"
|
|
},
|
|
"ja": {
|
|
"platforms": [
|
|
"android",
|
|
"android-arm",
|
|
"android-multilocale"
|
|
],
|
|
"revision": "main"
|
|
}
|
|
}
|