Update setup user authentication instructions #50189
Sharra-writesAnnotations
54 errors and 16 warnings
|
workflows
Canceling since a higher priority waiting request for Test @ wi11ialvl:wi11ialvl/add-setup-user-recovery exists
|
|
products
Canceling since a higher priority waiting request for Test @ wi11ialvl:wi11ialvl/add-setup-user-recovery exists
|
|
products
The operation was canceled.
|
|
secret-scanning
Canceling since a higher priority waiting request for Test @ wi11ialvl:wi11ialvl/add-setup-user-recovery exists
|
|
secret-scanning
The operation was canceled.
|
|
archives
Canceling since a higher priority waiting request for Test @ wi11ialvl:wi11ialvl/add-setup-user-recovery exists
|
|
archives
The operation was canceled.
|
|
audit-logs
Canceling since a higher priority waiting request for Test @ wi11ialvl:wi11ialvl/add-setup-user-recovery exists
|
|
audit-logs
The operation was canceled.
|
|
color-schemes
Canceling since a higher priority waiting request for Test @ wi11ialvl:wi11ialvl/add-setup-user-recovery exists
|
|
color-schemes
The operation was canceled.
|
|
fixtures
Canceling since a higher priority waiting request for Test @ wi11ialvl:wi11ialvl/add-setup-user-recovery exists
|
|
fixtures
The operation was canceled.
|
|
article-api
Canceling since a higher priority waiting request for Test @ wi11ialvl:wi11ialvl/add-setup-user-recovery exists
|
|
article-api
The operation was canceled.
|
|
content-linter
Canceling since a higher priority waiting request for Test @ wi11ialvl:wi11ialvl/add-setup-user-recovery exists
|
|
content-linter
The operation was canceled.
|
|
data-directory
Canceling since a higher priority waiting request for Test @ wi11ialvl:wi11ialvl/add-setup-user-recovery exists
|
|
data-directory
The operation was canceled.
|
|
webhooks
Canceling since a higher priority waiting request for Test @ wi11ialvl:wi11ialvl/add-setup-user-recovery exists
|
|
github-apps
Canceling since a higher priority waiting request for Test @ wi11ialvl:wi11ialvl/add-setup-user-recovery exists
|
|
webhooks
The operation was canceled.
|
|
github-apps
The operation was canceled.
|
|
release-notes
Canceling since a higher priority waiting request for Test @ wi11ialvl:wi11ialvl/add-setup-user-recovery exists
|
|
assets
Canceling since a higher priority waiting request for Test @ wi11ialvl:wi11ialvl/add-setup-user-recovery exists
|
|
assets
The operation was canceled.
|
|
release-notes
The operation was canceled.
|
|
versions
Canceling since a higher priority waiting request for Test @ wi11ialvl:wi11ialvl/add-setup-user-recovery exists
|
|
versions
The operation was canceled.
|
|
rest
Canceling since a higher priority waiting request for Test @ wi11ialvl:wi11ialvl/add-setup-user-recovery exists
|
|
rest
The operation was canceled.
|
|
content-render
Canceling since a higher priority waiting request for Test @ wi11ialvl:wi11ialvl/add-setup-user-recovery exists
|
|
content-render
The operation was canceled.
|
|
graphql
Canceling since a higher priority waiting request for Test @ wi11ialvl:wi11ialvl/add-setup-user-recovery exists
|
|
graphql
The operation was canceled.
|
|
observability
Canceling since a higher priority waiting request for Test @ wi11ialvl:wi11ialvl/add-setup-user-recovery exists
|
|
observability
The operation was canceled.
|
|
events
Canceling since a higher priority waiting request for Test @ wi11ialvl:wi11ialvl/add-setup-user-recovery exists
|
|
events
The operation was canceled.
|
|
landings
Canceling since a higher priority waiting request for Test @ wi11ialvl:wi11ialvl/add-setup-user-recovery exists
|
|
landings
The operation was canceled.
|
|
early-access
Canceling since a higher priority waiting request for Test @ wi11ialvl:wi11ialvl/add-setup-user-recovery exists
|
|
early-access
The operation was canceled.
|
|
shielding
Canceling since a higher priority waiting request for Test @ wi11ialvl:wi11ialvl/add-setup-user-recovery exists
|
|
shielding
The operation was canceled.
|
|
automated-pipelines
Canceling since a higher priority waiting request for Test @ wi11ialvl:wi11ialvl/add-setup-user-recovery exists
|
|
automated-pipelines
The operation was canceled.
|
|
redirects
Canceling since a higher priority waiting request for Test @ wi11ialvl:wi11ialvl/add-setup-user-recovery exists
|
|
redirects
The operation was canceled.
|
|
frame
Canceling since a higher priority waiting request for Test @ wi11ialvl:wi11ialvl/add-setup-user-recovery exists
|
|
frame
The operation was canceled.
|
|
search
Canceling since a higher priority waiting request for Test @ wi11ialvl:wi11ialvl/add-setup-user-recovery exists
|
|
search
The operation was canceled.
|
|
Test
Canceling since a higher priority waiting request for Test @ wi11ialvl:wi11ialvl/add-setup-user-recovery exists
|
|
color-schemes
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4. Actions will be forced to run with Node.js 24 by default starting June 16th, 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/
|
|
fixtures
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4. Actions will be forced to run with Node.js 24 by default starting June 16th, 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/
|
|
content-linter
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4. Actions will be forced to run with Node.js 24 by default starting June 16th, 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/
|
|
data-directory
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4. Actions will be forced to run with Node.js 24 by default starting June 16th, 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/
|
|
webhooks
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4. Actions will be forced to run with Node.js 24 by default starting June 16th, 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/
|
|
github-apps
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4. Actions will be forced to run with Node.js 24 by default starting June 16th, 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/
|
|
release-notes
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4. Actions will be forced to run with Node.js 24 by default starting June 16th, 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/
|
|
versions
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4. Actions will be forced to run with Node.js 24 by default starting June 16th, 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/
|
|
rest
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4. Actions will be forced to run with Node.js 24 by default starting June 16th, 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/
|
|
events
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4. Actions will be forced to run with Node.js 24 by default starting June 16th, 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/
|
|
landings
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4. Actions will be forced to run with Node.js 24 by default starting June 16th, 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/
|
|
early-access
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4. Actions will be forced to run with Node.js 24 by default starting June 16th, 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/
|
|
redirects
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4. Actions will be forced to run with Node.js 24 by default starting June 16th, 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/
|
|
frame
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4. Actions will be forced to run with Node.js 24 by default starting June 16th, 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/
|
|
search
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4. Actions will be forced to run with Node.js 24 by default starting June 16th, 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/
|
|
search
Failed to restore:
|