-
Notifications
You must be signed in to change notification settings - Fork 1.2k
Merge editorialized release notes for 18.2 #17131
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
Conversation
The one from ce0ed56 was the wrong one 🤦♂️
I've done the `msgid` bugfix real-world testing I wanted to do. Now switching back to the expected version.
|
You can trigger an installable build for these changes by visiting CircleCI here. |
| faraday (>= 0.9) | ||
| sawyer (~> 0.8.0, >= 0.5.3) | ||
| oj (3.13.1) | ||
| oj (3.13.4) |
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.
These gems patch version changes are a byproduct of my dance with the release toolkit version. They snuck in there because I had to go through two versions, so instead of git revert two commits I manually rolled back the Pluginfile and run bundle update fastlane-plugin-wpmreleasetoolkit.
I don't think they present any issue, so I decided not to spend any extra time to amend them.
Generated by 🚫 dangerJS |
Please forgive the long commit history. I was curious to try my
msgidfix, which is merged in the release toolkitdevelopbut hasn't been release yet, in another codebase but pointed totrunkinstead ofdevelopand, becauseupdate_appstore_stringspushes, I didn't have a chance to rebase the mistake away. FWIW, 69e4335 and confirm 7b3ecb5 one more time that the fix is legit.