support: Prevent SSRF for slack integration

[yuki-takei]

Task

https://redmine.weseek.co.jp/issues/166249

[changeset-bot]

⚠️ No Changeset found

Latest commit: f6963d1

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[yuki-takei]

@mergify queue

[mergify]

queue

🛑 The pull request has been removed from the queue default

Details

The merge conditions cannot be satisfied due to failing checks.

You can take a look at Queue: Embarked in merge queue check runs for more details about the failure.

[mergify]

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:

• ❌ test-prod-node20 / run-playwright (chromium, 1/2)
• ☑️ approve-updating-patch-version
• ☑️ auto-labeling
• ☑️ check-title
• ☑️ ci-pdf-converter-launch-prod
• ☑️ ci-slackbot-proxy-launch-prod
• ☑️ test-prod-node18 / report-playwright
• ☑️ test-prod-node18 / run-playwright

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

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.

[yuki-takei]

@mergify queue

[mergify]

queue

🛑 The pull request has been removed from the queue default

Details

The following conditions don't match anymore:

• any of: [🔀 queue conditions]
  • all of: [📌 queue conditions of queue default]
    • -check-failure ~= test-prod-node20 /

[mergify]

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 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.

[yuki-takei]

@mergify requeue

[mergify]

requeue

✅ The queue state of this pull request has been cleaned. It can be re-embarked automatically

[yuki-takei]

@mergify queue

[mergify]

queue

🛑 The pull request has been removed from the queue default

Details

The following conditions don't match anymore:

• any of: [🔀 queue conditions]
  • all of: [📌 queue conditions of queue default]
    • -check-failure ~= test-prod-node20 /

[mergify]

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: #9959.

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.

[yuki-takei]

@mergify requeue

[mergify]

requeue

✅ The queue state of this pull request has been cleaned. It can be re-embarked automatically

[yuki-takei]

@mergify queue

[mergify]

queue

🛑 The pull request has been removed from the queue default

Details

The merge conditions cannot be satisfied due to failing checks.

You can take a look at Queue: Embarked in merge queue check runs for more details about the failure.

[mergify]

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:

• ❌ test-prod-node20 / run-playwright (firefox, 1/2)
• ☑️ approve-updating-patch-version
• ☑️ auto-labeling
• ☑️ check-title
• ☑️ ci-pdf-converter-launch-prod
• ☑️ ci-slackbot-proxy-launch-prod
• ☑️ test-prod-node18 / report-playwright
• ☑️ test-prod-node18 / run-playwright

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

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.

[yuki-takei]

@mergify requeue

[mergify]

requeue

✅ The queue state of this pull request has been cleaned. It can be re-embarked automatically

[yuki-takei]

@mergify queue

[mergify]

queue

🛑 The pull request has been removed from the queue default

Details

The merge conditions cannot be satisfied due to failing checks.

You can take a look at Queue: Embarked in merge queue check runs for more details about the failure.

[mergify]

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:

• ❌ test-prod-node20 / run-playwright (chromium, 1/2)
• ☑️ approve-updating-patch-version
• ☑️ auto-labeling
• ☑️ check-title
• ☑️ ci-pdf-converter-launch-prod
• ☑️ ci-slackbot-proxy-launch-prod
• ☑️ test-prod-node18 / report-playwright
• ☑️ test-prod-node18 / run-playwright

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

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.

[yuki-takei]

@mergify requeue

[mergify]

requeue

✅ The queue state of this pull request has been cleaned. It can be re-embarked automatically

[yuki-takei]

@mergify queue

[mergify]

queue

🛑 The pull request has been removed from the queue default

Details

The merge conditions cannot be satisfied due to failing checks.

You can take a look at Queue: Embarked in merge queue check runs for more details about the failure.

[mergify]

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:

• ❌ test-prod-node20 / run-playwright (chromium, 1/2)
• ❌ test-prod-node20 / run-playwright (firefox, 1/2)
• ☑️ approve-updating-patch-version
• ☑️ auto-labeling
• ☑️ check-title
• ☑️ ci-pdf-converter-launch-prod
• ☑️ ci-slackbot-proxy-launch-prod
• ☑️ test-prod-node18 / report-playwright
• ☑️ test-prod-node18 / run-playwright

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

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.

[yuki-takei]

@mergify requeue

[yuki-takei]

@mergify queue

[mergify]

requeue

✅ The queue state of this pull request has been cleaned. It can be re-embarked automatically

[mergify]

queue

✅ The pull request has been merged automatically

Details

The pull request has been merged automatically at 4f6227f