-
Notifications
You must be signed in to change notification settings - Fork 1.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merge changes from beta 20.7.0.1, hotfix 20.6.1, editorialized release notes, and beta 20.7.0.2 #19294
Conversation
This makes the lane parameter using the same name as the `buildkite_trigger_build` action, avoiding confusion in the rare cases we need to call it manually. If you called the `trigger_release_build` or `trigger_beta_build` lane without a parameter, you'll get prompted to pass a `branch` one, by the underlying `buildkite_trigger_build` action. But if you next time called the lane with a `branch` parameter, you'd still get prompted to pass one, because the lane expected `branch_to_build` , but this was not made clear by the messages Fastlane prompted. Rather than adding extra code for this, I thought aligning the parameters name would sort out the issue. This leans a bit into the convention over configuration realm, though. There's nothing stopping future developers to reintroduce the same confusion by renaming the parameter either at the lane or action level. Given the limited userbase of this code and the relative slow pace at which it changes, I think that's an acceptable tradeoff to have convenience for the time being.
This makes the code a tiny bit clearer.
…-parameters-names-in-buildkite-actions
…elease_1.81.2 Integrate gutenberg-mobile release 1.81.2
Got conflicts in the `Podfile` and `Podfile.lock` and the version `xcconfig` files. As usual with hotfixes, I resolved the version conflict by keeping the release version value, 20.7. For the pod conflict, that was between Gutenberg 1.81.2 and 1.82.0. I kept 1.82.0 under the assumption the fix in 1.81.2 will land in the 1.82.x release series soon.
You can test the changes in Jetpack from this Pull Request by:
|
You can test the changes in WordPress from this Pull Request by:
|
Generated by 🚫 dangerJS |
@@ -1 +1,3 @@ | |||
* [*] Block Editor: Update link colors in action sheets from green to blue [https://github.com/WordPress/gutenberg/pull/42996] | |||
Links in action sheets (those pop-up menus on your device that bring up extra options) are now blue instead of green. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Sorry for missing this earlier and before this was sent for editorial, but looking at WordPress/gutenberg#42996 it seems that this change in Gutenberg might only after iOS after all and this shouldn't have been added to the Android release notes?
Never mind, I though I was reviewing the PR for Android… this is the PR for iOS, so all good 😊
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Though this entry in the release notes for Jetpack still feels odd, because it's about Jetpack and yet we're saying we updated colors from green to blue, not the other way around…?!
Or @mokagio did you accidentally swapped the WP and JP release notes when you copied the Editorialized versions in the wrong files?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
For posterity, just x-posting the comment here to confirm all looks good with the notes: wordpress-mobile/WordPress-Android#17145 (comment)
…elease_1.82.1 Integrate gutenberg-mobile release 1.82.1
Ratings submitted for the Jetpack app were being submitted to the WordPress app's store listing. This happened because the app was using the incorrect URL to open the App Store app review screen. While the app correctly defined the URL for the Jetpack app, it was then being overwritten at runtime by a URL fetched from an endpoint. This endpoint was only returning a URL for the WordPress app, so it overwrote the Jetpack app's URL with the WordPress app's one. This PR mitigates the problem on the Jetpack app by skipping the endpoint request for the Jetpack app only. This doesn't change behavior on the WordPress app. The impact of this change is that we can no longer remotely disable in-app requests for reviews. However, I don't recall this every being used. The priority here is to restore the Rate Us functionality for the Jetpack app, so follow-up work can look for a more permanenent fix.
…ck-app Fix Jetpack app review URL
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Checked the diff and saw this also includes:
- Tooling PR Rename
branch_to_build
parameter intobranch
#19281 - Beta fix Fix Jetpack app review URL #19299
- Gutenberg
1.82.1
, following recent hotfix - Editorialized Release Notes in
AppStoreStrings.po
- Some new
.strings
already translated (including new App Store metadata forru
)
utility.checkIfAppReviewPromptsHaveBeenDisabled(success: nil, failure: { | ||
DDLogError("Was unable to retrieve data about throttling") | ||
}) | ||
if AppConfiguration.isWordPress { | ||
utility.checkIfAppReviewPromptsHaveBeenDisabled(success: nil, failure: { | ||
DDLogError("Was unable to retrieve data about throttling") | ||
}) | ||
} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Comes from https://github.com/wordpress-mobile/WordPress-iOS/pull/19299/files which was merged in release/20.7
after code freeze 👍
/* Add an author prompt for the jetpack prologue */ | ||
"jetpack.prologue.prompt.addAuthor" = "Ajouter un auteur"; | ||
|
||
/* Build a site prompt for the jetpack prologue */ | ||
"jetpack.prologue.prompt.buildSite" = "Construire un site"; | ||
|
||
/* Check notifications prompt for the jetpack prologue */ | ||
"jetpack.prologue.prompt.checkNotifications" = "Vérifier vos notifications"; | ||
|
||
/* Share on Facebook prompt for the jetpack prologue */ | ||
"jetpack.prologue.prompt.fbShare" = "Partager sur Facebook"; | ||
|
||
/* Fix a security issue prompt for the jetpack prologue */ | ||
"jetpack.prologue.prompt.fixSecurity" = "Résoudre un incident de sécurité"; | ||
|
||
/* Post a photo prompt for the jetpack prologue */ | ||
"jetpack.prologue.prompt.postPhoto" = "Publier une photo"; | ||
|
||
/* Read an article prompt for the jetpack prologue */ | ||
"jetpack.prologue.prompt.readArticle" = "Lire un article"; | ||
|
||
/* Respond to comments prompt for the jetpack prologue */ | ||
"jetpack.prologue.prompt.respondComments" = "Répondre aux commentaires"; | ||
|
||
/* Restore a backup prompt for the jetpack prologue */ | ||
"jetpack.prologue.prompt.restoreBackup" = "Rétablir une sauvegarde"; | ||
|
||
/* Search for plugins prompt for the jetpack prologue */ | ||
"jetpack.prologue.prompt.searchPlugins" = "Rechercher des extensions"; | ||
|
||
/* Search for posts or sites prompt for the jetpack prologue */ | ||
"jetpack.prologue.prompt.searchPosts" = "Rechercher des articles ou sites"; | ||
|
||
/* Watch your stats prompt for the jetpack prologue */ | ||
"jetpack.prologue.prompt.watchStats" = "Consulter vos statistiques"; | ||
|
||
/* Write a blog prompt for the jetpack prologue */ | ||
"jetpack.prologue.prompt.writeBlog" = "Tenir un blog"; | ||
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@@ -0,0 +1 @@ | |||
Jetpack — конструктор сайтов |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
New translation finally fitting length limits? :nice: 👍
20.7.0.1
Notice that a new beta wasn't necessary because, so far, we only had changes to the release notes and the release automation.
The reason I'm shipping one, though, is that the Jetpack
20.7.0.0
binary was rejected during TestFlight review with:I think/hope this was a random TestFlight issue, but the only way to verify is to submit a new binary, with a new version, for review. I don't want to leave this verification till later in the release cycle in case the issue is legitimately on our end.
20.7.0.2
This PR was still open when new changes landed in the release branch after
20.7.0.1
, so I queue20.7.0.2
to it.Includes:
gutenberg-mobile
release 1.82.1 which includes a List v2 fix by @SiobhyB.strings
and Fastlane metadata) automatically pulled for the new translations that have already been approved in GlotPress.xcconfig