-
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 19.5.0.1 and editorialized release notes #18201
Conversation
As expected when merging the branch for the release currently in code freeze into an hotfix branch with the purpose of opening a PR to track the hotfix process into the latest release branch, we got conflicts in `config/Version.internal.xcconfig` and `config/Version.public.xcconfig` because both hotfix 19.4.1 and release 19.5 change the version compared to their common ancestor. I resolved the conflict, as usual, by keeping the value from 19.5 which is the latest.
Remove log messages that could crash the app due to missing params.
They are the same between WordPress and Jetpack.
Generated by 🚫 dangerJS |
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.
- Updates to the localization files (
.strings
and Fastlane metadata) automatically pulled for the new translations that have already been approved in GlotPress – With the caveat from the PR description - Version update in
.xcconfig
-
AppStoreStrings.po
changed with editorialized release notes - Diffs from the PRs that made it into this beta
<!--Warning: Auto-generated file, do not edit.--> | ||
<plist version="1.0"> | ||
<dict/> | ||
</plist> |
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.
See #18061 for why this and all the other .strings
in this diff changed in such a way.
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.
- Changes from bugfix PRs which landed in the release branch
- Version bump in
.xcconfig
files - Latest app and metadata translations pulled from Glotpress
- As you mentioned, no update to
Localizable.strings
but that's because of the issue you encountered with them not being properly committed with the new actions; will follow up on that in Ensure all downloaded translations and metadata are committed #18199 InfoPlist.strings
andSites.strings
files updated with latest translations, thanks to the new actions and process now properly handling them 🎉
- As you mentioned, no update to
- Editorialized Release Notes for WP+JP are in
<key>NSCameraUsageDescription</key> | ||
<string>Um Fotos oder Videos für deine Beiträge aufzunehmen.</string> | ||
<key>NSLocationUsageDescription</key> | ||
<string>Darf WordPress zu Beiträgen auf Websites, auf denen du Geotagging aktiviert hast, deinen Standort hinzufügen?</string> | ||
<key>NSLocationWhenInUseUsageDescription</key> | ||
<string>Darf WordPress zu Beiträgen auf Websites, auf denen du Geotagging aktiviert hast, deinen Standort hinzufügen?</string> | ||
<key>NSMicrophoneUsageDescription</key> | ||
<string>Aktiviere den Mikrofonzugriff, um in deinen Videos Ton aufzeichnen zu können.</string> | ||
<key>NSPhotoLibraryUsageDescription</key> | ||
<string>Um deinen Beiträgen Fotos oder Videos hinzuzufügen.</string> |
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.
Nice to see some translations slowly coming in for those 🎉
<dict> | ||
<key>CFBundleDisplayName</key> | ||
<string>Als Entwurf speichern</string> | ||
<key>CFBundleName</key> | ||
<string>Als Entwurf speichern</string> | ||
</dict> |
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.
Likewise 🎉
<dict> | ||
<key>BOl9KQ</key> | ||
<string>Es gibt ${count} Optionen, die zu „${site}“ passen.</string> | ||
<key>ILcGmf</key> | ||
<string>Website</string> | ||
<key>cyajMn</key> | ||
<string>Website</string> | ||
<key>gpCwrM</key> | ||
<string>Website auswählen</string> | ||
<key>s4dJhx</key> | ||
<string>Nur um sicherzugehen, du willst „${site}“?</string> | ||
<key>tVvJ9c</key> | ||
<string>Website-Intent auswählen</string> | ||
</dict> |
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.
🎉
Includes:
Notice that the diff doesn't include the usual set of translations. The reason is explained in #18199.
When I noticed that some
.strings
were not committed, I decided not to cancel the build and to still open this PR because:trunk
and the beta lane commits on the release branch itself, and since that's protected, I couldn't rewrite the history and try again after Ensure all downloaded translations and metadata are committed #18199 is merged.