Skip to content

Bump FXIOS [Bitrise] Update NewXcodeVersions Workflow Xcode Stack#29699

Merged
FilippoZazzeroni merged 1 commit intomainfrom
update-br-new-xcode-version
Nov 20, 2025
Merged

Bump FXIOS [Bitrise] Update NewXcodeVersions Workflow Xcode Stack#29699
FilippoZazzeroni merged 1 commit intomainfrom
update-br-new-xcode-version

Conversation

@github-actions
Copy link
Contributor

Automated changes by create-pull-request GitHub action

@github-actions github-actions bot requested a review from a team as a code owner September 29, 2025 18:10
@github-actions github-actions bot requested a review from AaronMT September 29, 2025 18:10
@github-actions github-actions bot force-pushed the update-br-new-xcode-version branch from 11860c8 to e4ecfd9 Compare September 30, 2025 00:28
@mobiletest-ci-bot
Copy link

mobiletest-ci-bot commented Sep 30, 2025

🧹 Tidy commit

Just 1 file(s) touched. Thanks for keeping it clean and review-friendly!

✅ Per-file coverage

All changed files meet the threshold of 35.0%.

Generated by 🚫 Danger Swift against 166fa76

Copy link
Contributor

@mergify mergify bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Github-action[bot] 💪

@github-actions github-actions bot force-pushed the update-br-new-xcode-version branch 13 times, most recently from 8cf89a8 to 02c6c85 Compare October 6, 2025 18:09
@github-actions github-actions bot force-pushed the update-br-new-xcode-version branch 12 times, most recently from cbaf3cc to 7003e8d Compare October 13, 2025 18:09
@mergify
Copy link
Contributor

mergify bot commented Nov 12, 2025

This pull request has been removed from the queue for the following reason: pull request dequeued.

Pull request #29699 has been dequeued. Rebase merges are not allowed on this repository.. The repository configuration doesn't allow rebase merge. The merge method configured in Mergify configuration must be allowed in the repository configuration settings.

You can check the last failing draft PR here: #30548.

You should look at the reason for the failure and decide if the pull request needs to be fixed or if you want to requeue it.
If you do update this pull request, it will automatically be requeued once the queue conditions match again.
If you think this was a flaky issue instead, you can requeue the pull request, without updating it, by posting a @mergifyio requeue comment.

@mergify
Copy link
Contributor

mergify bot commented Nov 12, 2025

⚠️ The sha of the head commit of this PR conflicts with #30514. Mergify cannot evaluate rules on this PR. ⚠️

@mergify
Copy link
Contributor

mergify bot commented Nov 12, 2025

This pull request has been removed from the queue for the following reason: pull request dequeued.

Pull request #29699 has been dequeued. Rebase merges are not allowed on this repository.. The repository configuration doesn't allow rebase merge. The merge method configured in Mergify configuration must be allowed in the repository configuration settings.

You should look at the reason for the failure and decide if the pull request needs to be fixed or if you want to requeue it.
If you do update this pull request, it will automatically be requeued once the queue conditions match again.
If you think this was a flaky issue instead, you can requeue the pull request, without updating it, by posting a @mergifyio requeue comment.

1 similar comment
@mergify
Copy link
Contributor

mergify bot commented Nov 12, 2025

This pull request has been removed from the queue for the following reason: pull request dequeued.

Pull request #29699 has been dequeued. Rebase merges are not allowed on this repository.. The repository configuration doesn't allow rebase merge. The merge method configured in Mergify configuration must be allowed in the repository configuration settings.

You should look at the reason for the failure and decide if the pull request needs to be fixed or if you want to requeue it.
If you do update this pull request, it will automatically be requeued once the queue conditions match again.
If you think this was a flaky issue instead, you can requeue the pull request, without updating it, by posting a @mergifyio requeue comment.

@mergify
Copy link
Contributor

mergify bot commented Nov 13, 2025

⚠️ The sha of the head commit of this PR conflicts with #30514. Mergify cannot evaluate rules on this PR. ⚠️

@mergify
Copy link
Contributor

mergify bot commented Nov 13, 2025

This pull request has been removed from the queue for the following reason: pull request dequeued.

Pull request #29699 has been dequeued. Rebase merges are not allowed on this repository.. The repository configuration doesn't allow rebase merge. The merge method configured in Mergify configuration must be allowed in the repository configuration settings.

You should look at the reason for the failure and decide if the pull request needs to be fixed or if you want to requeue it.
If you do update this pull request, it will automatically be requeued once the queue conditions match again.
If you think this was a flaky issue instead, you can requeue the pull request, without updating it, by posting a @mergifyio requeue comment.

@mergify
Copy link
Contributor

mergify bot commented Nov 13, 2025

⚠️ The sha of the head commit of this PR conflicts with #30514. Mergify cannot evaluate rules on this PR. ⚠️

@mergify
Copy link
Contributor

mergify bot commented Nov 13, 2025

This pull request has been removed from the queue for the following reason: pull request dequeued.

Pull request #29699 has been dequeued. Rebase merges are not allowed on this repository.. The repository configuration doesn't allow rebase merge. The merge method configured in Mergify configuration must be allowed in the repository configuration settings.

You should look at the reason for the failure and decide if the pull request needs to be fixed or if you want to requeue it.
If you do update this pull request, it will automatically be requeued once the queue conditions match again.
If you think this was a flaky issue instead, you can requeue the pull request, without updating it, by posting a @mergifyio requeue comment.

1 similar comment
@mergify
Copy link
Contributor

mergify bot commented Nov 14, 2025

This pull request has been removed from the queue for the following reason: pull request dequeued.

Pull request #29699 has been dequeued. Rebase merges are not allowed on this repository.. The repository configuration doesn't allow rebase merge. The merge method configured in Mergify configuration must be allowed in the repository configuration settings.

You should look at the reason for the failure and decide if the pull request needs to be fixed or if you want to requeue it.
If you do update this pull request, it will automatically be requeued once the queue conditions match again.
If you think this was a flaky issue instead, you can requeue the pull request, without updating it, by posting a @mergifyio requeue comment.

@mergify
Copy link
Contributor

mergify bot commented Nov 14, 2025

⚠️ The sha of the head commit of this PR conflicts with #30514. Mergify cannot evaluate rules on this PR. ⚠️

@mergify
Copy link
Contributor

mergify bot commented Nov 15, 2025

This pull request has been removed from the queue for the following reason: pull request dequeued.

Pull request #29699 has been dequeued. Rebase merges are not allowed on this repository.. The repository configuration doesn't allow rebase merge. The merge method configured in Mergify configuration must be allowed in the repository configuration settings.

You should look at the reason for the failure and decide if the pull request needs to be fixed or if you want to requeue it.
If you do update this pull request, it will automatically be requeued once the queue conditions match again.
If you think this was a flaky issue instead, you can requeue the pull request, without updating it, by posting a @mergifyio requeue comment.

1 similar comment
@mergify
Copy link
Contributor

mergify bot commented Nov 17, 2025

This pull request has been removed from the queue for the following reason: pull request dequeued.

Pull request #29699 has been dequeued. Rebase merges are not allowed on this repository.. The repository configuration doesn't allow rebase merge. The merge method configured in Mergify configuration must be allowed in the repository configuration settings.

You should look at the reason for the failure and decide if the pull request needs to be fixed or if you want to requeue it.
If you do update this pull request, it will automatically be requeued once the queue conditions match again.
If you think this was a flaky issue instead, you can requeue the pull request, without updating it, by posting a @mergifyio requeue comment.

@mergify
Copy link
Contributor

mergify bot commented Nov 17, 2025

This pull request has been removed from the queue for the following reason: pull request dequeued.

Pull request #29699 has been dequeued. Rebase merges are not allowed on this repository.. The repository configuration doesn't allow rebase merge. The merge method configured in Mergify configuration must be allowed in the repository configuration settings.

You can check the last failing draft PR here: #30673.

You should look at the reason for the failure and decide if the pull request needs to be fixed or if you want to requeue it.
If you do update this pull request, it will automatically be requeued once the queue conditions match again.
If you think this was a flaky issue instead, you can requeue the pull request, without updating it, by posting a @mergifyio requeue comment.

@mergify
Copy link
Contributor

mergify bot commented Nov 18, 2025

This pull request has been removed from the queue for the following reason: pull request dequeued.

Pull request #29699 has been dequeued. Rebase merges are not allowed on this repository.. The repository configuration doesn't allow rebase merge. The merge method configured in Mergify configuration must be allowed in the repository configuration settings.

You can check the last failing draft PR here: #30700.

You should look at the reason for the failure and decide if the pull request needs to be fixed or if you want to requeue it.
If you do update this pull request, it will automatically be requeued once the queue conditions match again.
If you think this was a flaky issue instead, you can requeue the pull request, without updating it, by posting a @mergifyio requeue comment.

@mergify
Copy link
Contributor

mergify bot commented Nov 18, 2025

⚠️ The sha of the head commit of this PR conflicts with #30514. Mergify cannot evaluate rules on this PR. ⚠️

1 similar comment
@mergify
Copy link
Contributor

mergify bot commented Nov 18, 2025

⚠️ The sha of the head commit of this PR conflicts with #30514. Mergify cannot evaluate rules on this PR. ⚠️

@mergify
Copy link
Contributor

mergify bot commented Nov 18, 2025

This pull request has been removed from the queue for the following reason: pull request dequeued.

Pull request #29699 has been dequeued. Rebase merges are not allowed on this repository.. The repository configuration doesn't allow rebase merge. The merge method configured in Mergify configuration must be allowed in the repository configuration settings.

You can check the last failing draft PR here: #30738.

You should look at the reason for the failure and decide if the pull request needs to be fixed or if you want to requeue it.
If you do update this pull request, it will automatically be requeued once the queue conditions match again.
If you think this was a flaky issue instead, you can requeue the pull request, without updating it, by posting a @mergifyio requeue comment.

@mergify
Copy link
Contributor

mergify bot commented Nov 19, 2025

This pull request has been removed from the queue for the following reason: pull request dequeued.

Pull request #29699 has been dequeued. Rebase merges are not allowed on this repository.. The repository configuration doesn't allow rebase merge. The merge method configured in Mergify configuration must be allowed in the repository configuration settings.

You should look at the reason for the failure and decide if the pull request needs to be fixed or if you want to requeue it.
If you do update this pull request, it will automatically be requeued once the queue conditions match again.
If you think this was a flaky issue instead, you can requeue the pull request, without updating it, by posting a @mergifyio requeue comment.

@mergify
Copy link
Contributor

mergify bot commented Nov 19, 2025

⚠️ The sha of the head commit of this PR conflicts with #30514. Mergify cannot evaluate rules on this PR. ⚠️

@mergify
Copy link
Contributor

mergify bot commented Nov 19, 2025

This pull request has been removed from the queue for the following reason: checks failed.

The merge conditions cannot be satisfied due to failing checks:

You can check the last failing draft PR here: #30769.

You may have to fix your CI before adding the pull request to the queue again.
If you update this pull request, to fix the CI, it will automatically be requeued once the queue conditions match again.
If you think this was a flaky issue instead, you can requeue the pull request, without updating it, by posting a @mergifyio requeue comment.

@mergify
Copy link
Contributor

mergify bot commented Nov 20, 2025

This pull request has been removed from the queue for the following reason: pull request dequeued.

Pull request #29699 has been dequeued. Rebase merges are not allowed on this repository.. The repository configuration doesn't allow rebase merge. The merge method configured in Mergify configuration must be allowed in the repository configuration settings.

You should look at the reason for the failure and decide if the pull request needs to be fixed or if you want to requeue it.
If you do update this pull request, it will automatically be requeued once the queue conditions match again.
If you think this was a flaky issue instead, you can requeue the pull request, without updating it, by posting a @mergifyio requeue comment.

@github-actions
Copy link
Contributor Author

🚀 PR merged to main, targeting version: 145.3

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants