Bump [v106] Upgrade to Glean v51.2.0 #11859
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
@badboy When we don't have an associated bug, we follow the PR naming guideline without the issue number. In your case it would be something like |
|
I think this PR may need to be updated with latest main. It failed on Bitrise because the git-clone step has an older version different than the one in the repo |
badboy
changed the title
badboy
changed the title
badboy
force-pushed
the
glean-update-51.2.0
branch
from
f26db89
to
36d17dc
Compare
|
Build is green here |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Update the bundles Glean version. This contains a necessary bugfix.
Re PR naming: there's no associated bug for this and it should land whenever possible. Happy to adjust the PR name if you tell me to what here.