Fix W-21968404: Make authentication_type optional in update_connections #793
Annotations
3 errors and 1 warning
|
Comment on pull request with coverage
Resource not accessible by integration - https://docs.github.com/rest/issues/comments#create-an-issue-comment
|
|
Comment on pull request with coverage
HttpError: Resource not accessible by integration - https://docs.github.com/rest/issues/comments#create-an-issue-comment
|
|
Comment on pull request with coverage
Permission denied when trying to create/update comment.
This PR is from a fork. GitHub restricts the GITHUB_TOKEN to read-only
for fork PRs triggered by the `pull_request` event.
To fix this, use the `pull_request_target` event instead:
```yaml
on:
pull_request_target:
types: [opened, synchronize, reopened]
permissions:
contents: read
pull-requests: write
```
Note: `pull_request_target` runs in the context of the base branch.
Be cautious when checking out fork code — never run untrusted code
from the fork with elevated permissions.
For more information, see:
https://github.com/MishaKav/pytest-coverage-comment#fork-prs
|
|
Complete job
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/setup-python@v5. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
background
wait
wait-all
cancel
Loading