fix: get jwt from apigw (merge request !2734) #4883
lint.yml
on: push
bcs-webconsole
1m 53s
bcs-monitor
2m 43s
bcs-cluster-manager
4m 59s
bcs-helm-manager
3m 11s
bcs-project-manager
2m 37s
bcs-user-manager
1m 43s
bcs-cluster-resources
3m 5s
bcs-platform-manager
1m 31s
bcs-task
1m 36s
Annotations
2 errors and 27 warnings
|
bcs-monitor
issues found
|
|
bcs-monitor:
bcs-services/bcs-monitor/pkg/rest/rest.go#L106
the line is 138 characters long, which exceeds the maximum of 120 characters. (lll)
|
|
bcs-task
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v3, actions/setup-go@v3, golangci/golangci-lint-action@v3. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
bcs-task
Failed to save: <h2>Our services aren't available right now</h2><p>We're working to restore all services as soon as possible. Please check back soon.</p>0kh+yaQAAAAAW8XPo47bTQqT+8mh5ROZlUEhMMzBFREdFMDQwOABFZGdl
|
|
bcs-task
Failed to restore: Cache service responded with 400
|
|
bcs-user-manager
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v3, actions/setup-go@v3, golangci/golangci-lint-action@v3. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
bcs-user-manager
Failed to save: <h2>Our services aren't available right now</h2><p>We're working to restore all services as soon as possible. Please check back soon.</p>0mR+yaQAAAABYhqlf1F8XRaaudyf/xXxoUEhYMzFFREdFMDUwOQBFZGdl
|
|
bcs-user-manager
Failed to restore: Cache service responded with 400
|
|
bcs-webconsole
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v3, actions/setup-go@v3, golangci/golangci-lint-action@v3. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
bcs-webconsole
Failed to save: <h2>Our services aren't available right now</h2><p>We're working to restore all services as soon as possible. Please check back soon.</p>0ox+yaQAAAABz2Kql9P0hRLTCFbY+i7TiRE0yRURHRTA5MTQARWRnZQ==
|
|
bcs-webconsole
Failed to restore: Cache service responded with 400
|
|
bcs-platform-manager
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v3, actions/setup-go@v3, golangci/golangci-lint-action@v3. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
bcs-platform-manager
Failed to save: <h2>Our services aren't available right now</h2><p>We're working to restore all services as soon as possible. Please check back soon.</p>0ph+yaQAAAADBuHlbSVGcSaDnDiq3AdgSQ0hJMzBFREdFMDMxOQBFZGdl
|
|
bcs-platform-manager
Failed to restore: Cache service responded with 400
|
|
bcs-project-manager
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v3, actions/setup-go@v3, golangci/golangci-lint-action@v3. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
bcs-project-manager
Failed to save: <h2>Our services aren't available right now</h2><p>We're working to restore all services as soon as possible. Please check back soon.</p>0zx+yaQAAAABJzJw/yZw/SIug7hlwdTevQ0hHRURHRTE3MTcARWRnZQ==
|
|
bcs-project-manager
Failed to restore: Cache service responded with 400
|
|
bcs-monitor
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v3, actions/setup-go@v3, golangci/golangci-lint-action@v3. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
bcs-monitor
Failed to save: <h2>Our services aren't available right now</h2><p>We're working to restore all services as soon as possible. Please check back soon.</p>01R+yaQAAAACZtdxS9NvPQIiJnE5DVKavQ0hJMzBFREdFMDIwOQBFZGdl
|
|
bcs-monitor
Failed to restore: Cache service responded with 400
|
|
bcs-cluster-resources
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v3, actions/setup-go@v3, golangci/golangci-lint-action@v3. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
bcs-cluster-resources
Failed to save: <h2>Our services aren't available right now</h2><p>We're working to restore all services as soon as possible. Please check back soon.</p>06x+yaQAAAADdZSdjqYJlQrSfGkrFP+ZmREVOMzAxMDAwMTA0MDIzAEVkZ2U=
|
|
bcs-cluster-resources
Failed to restore: Cache service responded with 400
|
|
bcs-helm-manager
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v3, actions/setup-go@v3, golangci/golangci-lint-action@v3. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
bcs-helm-manager
Failed to save: <h2>Our services aren't available right now</h2><p>We're working to restore all services as soon as possible. Please check back soon.</p>08R+yaQAAAAA1auDant6nRJ83rZRK3tZvUEhYMzFFREdFMDUxNABFZGdl
|
|
bcs-helm-manager
Failed to restore: Cache service responded with 400
|
|
bcs-cluster-manager
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v3, actions/setup-go@v3, golangci/golangci-lint-action@v3. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
bcs-cluster-manager
Failed to save: <h2>Our services aren't available right now</h2><p>We're working to restore all services as soon as possible. Please check back soon.</p>0XCCyaQAAAACaDWRRANKVSoTJiu53/oZLQ0hJMzBFREdFMDMxOQBFZGdl
|
|
bcs-cluster-manager
Failed to restore: Cache service responded with 400
|