-
Couldn't load subscription status.
- Fork 3.1k
feat(deps): bump androidxFragment from 1.5.7 to 1.6.2 #4355
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
base: master
Are you sure you want to change the base?
Conversation
181b7aa to
ecaddcc
Compare
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.
LGTM!
|
@dependabot rebase |
|
Looks like this PR has been edited by someone other than Dependabot. That means Dependabot can't rebase it - sorry! If you're happy for Dependabot to recreate it from scratch, overwriting any edits, you can request |
eadb289 to
07daedb
Compare
Bumps `androidxFragment` from 1.5.7 to 1.6.2. Updates `androidx.fragment:fragment-ktx` from 1.5.7 to 1.6.2 Updates `androidx.fragment:fragment-testing` from 1.5.7 to 1.6.2 --- updated-dependencies: - dependency-name: androidx.fragment:fragment-ktx dependency-type: direct:production update-type: version-update:semver-minor - dependency-name: androidx.fragment:fragment-testing dependency-type: direct:production update-type: version-update:semver-minor ... Signed-off-by: dependabot[bot] <[email protected]>
…sActivityTest, LoginActivityTest and PassCodeActivityTest
07daedb to
ad35faa
Compare
|
We are having problems with Bitrise because it does not pass the tests due to flakies. Therefore we have made a list of the flakies that are being played to ignore them from Bitrise. We have looked at the last 10 worksflows that have failed in bitrise and we have put the tests that have been played the most in order from most to least. In any case all these tests except
|
that one failed 1 out of 10, same as Just as my opinion, i'd ignore only the two on the top. |
Because that one in particular I've never seen it in other past worksflows (maybe appear too more often). For example, the |
6d49ac0 to
ad35faa
Compare
|
This bump is not going to be merged because the bitrise UI Tests are giving a lot of problems. |
Bumps
androidxFragmentfrom 1.5.7 to 1.6.2.Updates
androidx.fragment:fragment-ktxfrom 1.5.7 to 1.6.2Updates
androidx.fragment:fragment-testingfrom 1.5.7 to 1.6.2You can trigger a rebase of this PR by commenting
@dependabot rebase.Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
@dependabot rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot mergewill merge this PR after your CI passes on it@dependabot squash and mergewill squash and merge this PR after your CI passes on it@dependabot cancel mergewill cancel a previously requested merge and block automerging@dependabot reopenwill reopen this PR if it is closed@dependabot closewill close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually@dependabot show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@dependabot ignore this major versionwill close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this minor versionwill close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this dependencywill close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)