Skip to content

Update dependency @sentry/react to ^10.51.0 - autoclosed #3649

Update dependency @sentry/react to ^10.51.0 - autoclosed

Update dependency @sentry/react to ^10.51.0 - autoclosed #3649

  • prompt-dev-vm requires an approval to start deploying changes

    View pending deployments

    View pending deployments
    requested by renovate[bot] in Build and Deploy to Dev #3649

Triggered via pull request May 5, 2026 08:45
Status Waiting
Total duration
Artifacts 69
  • prompt-dev-vm requires an approval to start deploying changes

    View pending deployments

    View pending deployments
    requested by renovate[bot] in Build and Deploy to Dev #3649

dev.yml

on: pull_request
detect-changes  /  detect
9s
detect-changes / detect
assign-author
4s
assign-author
detect-migrations  /  detect-migrations
8s
detect-migrations / detect-migrations
Matrix: lint-clients / lint-client
Matrix: lint-servers / lint-server
generate-api-spec  /  resolve-directories
6s
generate-api-spec / resolve-directories
Matrix: build-clients / clients-base / build
Matrix: vet-servers / vet-server
Waiting for pending jobs
Matrix: generate-api-spec / generate-api-spec
build-clients  /  ...  /  merge
23s
build-clients / clients-base / merge
Matrix: test-servers / test
Waiting for pending jobs
Matrix: build-clients / assessment / build
Matrix: build-clients / certificate / build
Matrix: build-clients / core / build
Matrix: build-clients / devops-challenge / build
Matrix: build-clients / interview / build
Matrix: build-clients / matching / build
Matrix: build-clients / self-team-allocation / build
Matrix: build-clients / team-allocation / build
Matrix: build-clients / template / build
build-clients  /  debug-job
3s
build-clients / debug-job
Matrix: build-servers / assessment / build
Matrix: build-servers / certificate / build
Matrix: build-servers / core / build
Matrix: build-servers / interview / build
Matrix: build-servers / self-team-allocation / build
Matrix: build-servers / team-allocation / build
build-clients  /  ...  /  merge
23s
build-clients / assessment / merge
build-clients  /  ...  /  merge
13s
build-clients / certificate / merge
build-clients  /  ...  /  merge
20s
build-clients / core / merge
build-clients  /  ...  /  merge
21s
build-clients / devops-challenge / merge
build-clients  /  ...  /  merge
21s
build-clients / interview / merge
build-clients  /  ...  /  merge
15s
build-clients / matching / merge
build-clients  /  ...  /  merge
12s
build-clients / self-team-allocation / merge
build-clients  /  ...  /  merge
25s
build-clients / team-allocation / merge
build-clients  /  ...  /  merge
23s
build-clients / template / merge
build-servers  /  ...  /  merge
19s
build-servers / assessment / merge
build-servers  /  ...  /  merge
13s
build-servers / certificate / merge
build-servers  /  ...  /  merge
22s
build-servers / core / merge
build-servers  /  ...  /  merge
20s
build-servers / interview / merge
build-servers  /  ...  /  merge
15s
build-servers / self-team-allocation / merge
build-servers  /  ...  /  merge
14s
build-servers / team-allocation / merge
deploy-dev  /  deploy
deploy-dev / deploy
prompt-dev-vm waiting for review
Fit to window
Zoom out
Zoom in

Deployment protection rules

Reviewers, timers, and other rules protecting deployments in this run
Event Environments Comment
renovate[bot]
requested review
prompt-dev-vm -

Annotations

49 warnings
detect-changes / detect
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: tj-actions/changed-files@v45. 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/
build-servers / team-allocation / Build linux/amd64 Docker Image for ghcr.io/prompt-edu/prompt/prompt-server-team-allocation
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: docker/build-push-action@v6, docker/login-action@v3, docker/metadata-action@v5, docker/setup-buildx-action@v3, docker/setup-qemu-action@v3. 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/
build-servers / certificate / Build linux/amd64 Docker Image for ghcr.io/prompt-edu/prompt/prompt-server-certificate
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: docker/build-push-action@v6, docker/login-action@v3, docker/metadata-action@v5, docker/setup-buildx-action@v3, docker/setup-qemu-action@v3. 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/
build-servers / core / Build linux/amd64 Docker Image for ghcr.io/prompt-edu/prompt/prompt-server-core
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: docker/build-push-action@v6, docker/login-action@v3, docker/metadata-action@v5, docker/setup-buildx-action@v3, docker/setup-qemu-action@v3. 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/
build-servers / assessment / Build linux/amd64 Docker Image for ghcr.io/prompt-edu/prompt/prompt-server-assessment
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: docker/build-push-action@v6, docker/login-action@v3, docker/metadata-action@v5, docker/setup-buildx-action@v3, docker/setup-qemu-action@v3. 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/
build-servers / self-team-allocation / Build linux/amd64 Docker Image for ghcr.io/prompt-edu/prompt/prompt-server-self-team-allocation
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: docker/build-push-action@v6, docker/login-action@v3, docker/metadata-action@v5, docker/setup-buildx-action@v3, docker/setup-qemu-action@v3. 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/
build-servers / assessment / Build linux/arm64 Docker Image for ghcr.io/prompt-edu/prompt/prompt-server-assessment
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: docker/build-push-action@v6, docker/login-action@v3, docker/metadata-action@v5, docker/setup-buildx-action@v3, docker/setup-qemu-action@v3. 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/
build-servers / interview / Build linux/amd64 Docker Image for ghcr.io/prompt-edu/prompt/prompt-server-interview
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: docker/build-push-action@v6, docker/login-action@v3, docker/metadata-action@v5, docker/setup-buildx-action@v3, docker/setup-qemu-action@v3. 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/
build-servers / core / Build linux/arm64 Docker Image for ghcr.io/prompt-edu/prompt/prompt-server-core
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: docker/build-push-action@v6, docker/login-action@v3, docker/metadata-action@v5, docker/setup-buildx-action@v3, docker/setup-qemu-action@v3. 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/
build-servers / self-team-allocation / Build linux/arm64 Docker Image for ghcr.io/prompt-edu/prompt/prompt-server-self-team-allocation
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: docker/build-push-action@v6, docker/login-action@v3, docker/metadata-action@v5, docker/setup-buildx-action@v3, docker/setup-qemu-action@v3. 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/
build-servers / team-allocation / Build linux/arm64 Docker Image for ghcr.io/prompt-edu/prompt/prompt-server-team-allocation
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: docker/build-push-action@v6, docker/login-action@v3, docker/metadata-action@v5, docker/setup-buildx-action@v3, docker/setup-qemu-action@v3. 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/
build-servers / certificate / Build linux/arm64 Docker Image for ghcr.io/prompt-edu/prompt/prompt-server-certificate
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: docker/build-push-action@v6, docker/login-action@v3, docker/metadata-action@v5, docker/setup-buildx-action@v3, docker/setup-qemu-action@v3. 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/
build-servers / interview / Build linux/arm64 Docker Image for ghcr.io/prompt-edu/prompt/prompt-server-interview
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: docker/build-push-action@v6, docker/login-action@v3, docker/metadata-action@v5, docker/setup-buildx-action@v3, docker/setup-qemu-action@v3. 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/
build-servers / assessment / merge
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: docker/login-action@v3, docker/metadata-action@v5, docker/setup-buildx-action@v3. 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/
build-servers / self-team-allocation / merge
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: docker/login-action@v3, docker/metadata-action@v5, docker/setup-buildx-action@v3. 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/
build-servers / team-allocation / merge
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: docker/login-action@v3, docker/metadata-action@v5, docker/setup-buildx-action@v3. 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/
build-servers / core / merge
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: docker/login-action@v3, docker/metadata-action@v5, docker/setup-buildx-action@v3. 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/
build-servers / certificate / merge
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: docker/login-action@v3, docker/metadata-action@v5, docker/setup-buildx-action@v3. 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/
build-servers / interview / merge
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: docker/login-action@v3, docker/metadata-action@v5, docker/setup-buildx-action@v3. 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/
build-clients / clients-base / Build linux/arm64 Docker Image for ghcr.io/prompt-edu/prompt/prompt-clients-base
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: docker/build-push-action@v6, docker/login-action@v3, docker/metadata-action@v5, docker/setup-buildx-action@v3, docker/setup-qemu-action@v3. 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/
build-clients / clients-base / Build linux/amd64 Docker Image for ghcr.io/prompt-edu/prompt/prompt-clients-base
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: docker/build-push-action@v6, docker/login-action@v3, docker/metadata-action@v5, docker/setup-buildx-action@v3, docker/setup-qemu-action@v3. 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/
build-clients / clients-base / merge
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: docker/login-action@v3, docker/metadata-action@v5, docker/setup-buildx-action@v3. 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/
build-clients / template / Build linux/amd64 Docker Image for ghcr.io/prompt-edu/prompt/prompt-clients-template-component
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: docker/build-push-action@v6, docker/login-action@v3, docker/metadata-action@v5, docker/setup-buildx-action@v3, docker/setup-qemu-action@v3. 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/
build-clients / devops-challenge / Build linux/arm64 Docker Image for ghcr.io/prompt-edu/prompt/prompt-clients-devops-challenge-component
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: docker/build-push-action@v6, docker/login-action@v3, docker/metadata-action@v5, docker/setup-buildx-action@v3, docker/setup-qemu-action@v3. 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/
build-clients / matching / Build linux/arm64 Docker Image for ghcr.io/prompt-edu/prompt/prompt-clients-matching-component
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: docker/build-push-action@v6, docker/login-action@v3, docker/metadata-action@v5, docker/setup-buildx-action@v3, docker/setup-qemu-action@v3. 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/
build-clients / assessment / Build linux/amd64 Docker Image for ghcr.io/prompt-edu/prompt/prompt-clients-assessment-component
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: docker/build-push-action@v6, docker/login-action@v3, docker/metadata-action@v5, docker/setup-buildx-action@v3, docker/setup-qemu-action@v3. 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/
build-clients / certificate / Build linux/amd64 Docker Image for ghcr.io/prompt-edu/prompt/prompt-clients-certificate-component
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: docker/build-push-action@v6, docker/login-action@v3, docker/metadata-action@v5, docker/setup-buildx-action@v3, docker/setup-qemu-action@v3. 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/
build-clients / self-team-allocation / Build linux/arm64 Docker Image for ghcr.io/prompt-edu/prompt/prompt-clients-self-team-allocation-component
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: docker/build-push-action@v6, docker/login-action@v3, docker/metadata-action@v5, docker/setup-buildx-action@v3, docker/setup-qemu-action@v3. 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/
build-clients / team-allocation / Build linux/arm64 Docker Image for ghcr.io/prompt-edu/prompt/prompt-clients-team-allocation-component
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: docker/build-push-action@v6, docker/login-action@v3, docker/metadata-action@v5, docker/setup-buildx-action@v3, docker/setup-qemu-action@v3. 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/
build-clients / self-team-allocation / Build linux/amd64 Docker Image for ghcr.io/prompt-edu/prompt/prompt-clients-self-team-allocation-component
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: docker/build-push-action@v6, docker/login-action@v3, docker/metadata-action@v5, docker/setup-buildx-action@v3, docker/setup-qemu-action@v3. 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/
build-clients / core / Build linux/arm64 Docker Image for ghcr.io/prompt-edu/prompt/prompt-clients-core
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: docker/build-push-action@v6, docker/login-action@v3, docker/metadata-action@v5, docker/setup-buildx-action@v3, docker/setup-qemu-action@v3. 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/
build-clients / interview / Build linux/amd64 Docker Image for ghcr.io/prompt-edu/prompt/prompt-clients-interview-component
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: docker/build-push-action@v6, docker/login-action@v3, docker/metadata-action@v5, docker/setup-buildx-action@v3, docker/setup-qemu-action@v3. 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/
build-clients / interview / Build linux/arm64 Docker Image for ghcr.io/prompt-edu/prompt/prompt-clients-interview-component
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: docker/build-push-action@v6, docker/login-action@v3, docker/metadata-action@v5, docker/setup-buildx-action@v3, docker/setup-qemu-action@v3. 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/
build-clients / template / Build linux/arm64 Docker Image for ghcr.io/prompt-edu/prompt/prompt-clients-template-component
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: docker/build-push-action@v6, docker/login-action@v3, docker/metadata-action@v5, docker/setup-buildx-action@v3, docker/setup-qemu-action@v3. 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/
build-clients / assessment / Build linux/arm64 Docker Image for ghcr.io/prompt-edu/prompt/prompt-clients-assessment-component
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: docker/build-push-action@v6, docker/login-action@v3, docker/metadata-action@v5, docker/setup-buildx-action@v3, docker/setup-qemu-action@v3. 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/
build-clients / devops-challenge / Build linux/amd64 Docker Image for ghcr.io/prompt-edu/prompt/prompt-clients-devops-challenge-component
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: docker/build-push-action@v6, docker/login-action@v3, docker/metadata-action@v5, docker/setup-buildx-action@v3, docker/setup-qemu-action@v3. 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/
build-clients / core / Build linux/amd64 Docker Image for ghcr.io/prompt-edu/prompt/prompt-clients-core
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: docker/build-push-action@v6, docker/login-action@v3, docker/metadata-action@v5, docker/setup-buildx-action@v3, docker/setup-qemu-action@v3. 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/
build-clients / matching / Build linux/amd64 Docker Image for ghcr.io/prompt-edu/prompt/prompt-clients-matching-component
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: docker/build-push-action@v6, docker/login-action@v3, docker/metadata-action@v5, docker/setup-buildx-action@v3, docker/setup-qemu-action@v3. 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/
build-clients / team-allocation / Build linux/amd64 Docker Image for ghcr.io/prompt-edu/prompt/prompt-clients-team-allocation-component
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: docker/build-push-action@v6, docker/login-action@v3, docker/metadata-action@v5, docker/setup-buildx-action@v3, docker/setup-qemu-action@v3. 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/
build-clients / certificate / Build linux/arm64 Docker Image for ghcr.io/prompt-edu/prompt/prompt-clients-certificate-component
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: docker/build-push-action@v6, docker/login-action@v3, docker/metadata-action@v5, docker/setup-buildx-action@v3, docker/setup-qemu-action@v3. 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/
build-clients / self-team-allocation / merge
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: docker/login-action@v3, docker/metadata-action@v5, docker/setup-buildx-action@v3. 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/
build-clients / template / merge
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: docker/login-action@v3, docker/metadata-action@v5, docker/setup-buildx-action@v3. 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/
build-clients / interview / merge
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: docker/login-action@v3, docker/metadata-action@v5, docker/setup-buildx-action@v3. 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/
build-clients / matching / merge
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: docker/login-action@v3, docker/metadata-action@v5, docker/setup-buildx-action@v3. 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/
build-clients / assessment / merge
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: docker/login-action@v3, docker/metadata-action@v5, docker/setup-buildx-action@v3. 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/
build-clients / core / merge
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: docker/login-action@v3, docker/metadata-action@v5, docker/setup-buildx-action@v3. 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/
build-clients / certificate / merge
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: docker/login-action@v3, docker/metadata-action@v5, docker/setup-buildx-action@v3. 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/
build-clients / devops-challenge / merge
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: docker/login-action@v3, docker/metadata-action@v5, docker/setup-buildx-action@v3. 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/
build-clients / team-allocation / merge
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: docker/login-action@v3, docker/metadata-action@v5, docker/setup-buildx-action@v3. 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/

Artifacts

Produced during runtime
Name Size Digest
api-spec-assessment
27.6 KB
sha256:6308d37ea9c749256af2db51e6779d35df15dced740881aa204bbf0f6dccb3e3
api-spec-core
27.3 KB
sha256:25ef38e210774b780036d8277d1cb50bec19ccb0a40c8eb5b51734d10e9743f9
api-spec-interview
6.35 KB
sha256:c1480dc7f6b333eb2878316347f7774a003b0ace1e2f37987576a6eb13433aba
api-spec-self_team_allocation
6.98 KB
sha256:4ac4056eadeb2adfd64c79b43b6163eff29eb7f98f2287bb47c9bab76216f47d
api-spec-template_server
3.26 KB
sha256:2677724ecbc6bd3e26a9ca0f93f02d20b1d7d4ad6ff8f23b50598014b8bf4873
digests-25366627192-ghcr.io-prompt-edu-prompt-prompt-clients-assessment-component-linux-amd64 Expired
244 Bytes
sha256:ebfa8a935783c2e8131ed02ab2cf3f30c7199b3042d9da247022c53b7539f3b6
digests-25366627192-ghcr.io-prompt-edu-prompt-prompt-clients-assessment-component-linux-arm64 Expired
244 Bytes
sha256:789a66da09f5c5568a990fb4d4d21a4bb66c39759835279bf9e92508ebeb66b2
digests-25366627192-ghcr.io-prompt-edu-prompt-prompt-clients-base-linux-amd64 Expired
244 Bytes
sha256:bc0ea6964c84d753d4f99b3894f4efcbbcdd3909b1366baabd19433a352f7819
digests-25366627192-ghcr.io-prompt-edu-prompt-prompt-clients-base-linux-arm64 Expired
244 Bytes
sha256:fe5ac854f06ea60641f9041d0aa42e385600d667396ff6b52f2bb36a10558313
digests-25366627192-ghcr.io-prompt-edu-prompt-prompt-clients-certificate-component-linux-amd64 Expired
244 Bytes
sha256:d0d6930b63129cd7b5906e0b6f48426f3554a56d550fc69a179438ee153ea7d4
digests-25366627192-ghcr.io-prompt-edu-prompt-prompt-clients-certificate-component-linux-arm64 Expired
244 Bytes
sha256:6fbe6af3873713e6cfc4580c0d3029c87b3374276fef406050b2ccbe7c7acd80
digests-25366627192-ghcr.io-prompt-edu-prompt-prompt-clients-core-linux-amd64 Expired
244 Bytes
sha256:3e1f60881d236c20eab3a749afd8798e43c930de3832a6fec295f69e645c72c4
digests-25366627192-ghcr.io-prompt-edu-prompt-prompt-clients-core-linux-arm64 Expired
244 Bytes
sha256:3a042b3a0dac3483de493159d4962e571a63c009bf10131809b083e9543536f2
digests-25366627192-ghcr.io-prompt-edu-prompt-prompt-clients-devops-challenge-component-linux-amd64 Expired
244 Bytes
sha256:4e6a42bc6047795fdeebfe5ecac5ecdf6e7d2d0617d438e4e9e5f908df6b1155
digests-25366627192-ghcr.io-prompt-edu-prompt-prompt-clients-devops-challenge-component-linux-arm64 Expired
244 Bytes
sha256:a200b663cc5c796932704060086cd5ce4da463385a499ec976e269ba21ecbf7c
digests-25366627192-ghcr.io-prompt-edu-prompt-prompt-clients-interview-component-linux-amd64 Expired
244 Bytes
sha256:b2a6e9e372853e9efb479bc64c2c3d3e5686674581436233f4fbdf83a3aa24af
digests-25366627192-ghcr.io-prompt-edu-prompt-prompt-clients-interview-component-linux-arm64 Expired
244 Bytes
sha256:a5373ad1ad30ddc5c66d090e5b778a4dfffa0685c108d46d596b7e7f9b9948a3
digests-25366627192-ghcr.io-prompt-edu-prompt-prompt-clients-matching-component-linux-amd64 Expired
244 Bytes
sha256:a4516bfc9e876b8648ccb0ba8fb84443aabb10eae70f7c2f5760c5f4b57b5ae9
digests-25366627192-ghcr.io-prompt-edu-prompt-prompt-clients-matching-component-linux-arm64 Expired
244 Bytes
sha256:05a2aa5904fbbf51064e74ffedfdf51aaa74edb300c532a6c651f97e0f07fc97
digests-25366627192-ghcr.io-prompt-edu-prompt-prompt-clients-self-team-allocation-component-linux-amd64 Expired
244 Bytes
sha256:112a2dd357ef94e0fc69e8a9b0b7953788d9a2c2fa4ba92cae207bc0cb763fa5
digests-25366627192-ghcr.io-prompt-edu-prompt-prompt-clients-self-team-allocation-component-linux-arm64 Expired
244 Bytes
sha256:2064bd122ec5aa5f6da5418098867301d5580f4cf43d2d7a746ca527714f9407
digests-25366627192-ghcr.io-prompt-edu-prompt-prompt-clients-team-allocation-component-linux-amd64 Expired
244 Bytes
sha256:69cc4b0227b40f4431f57feec772900b07a8bc23afc094f682fc2bf643bc6858
digests-25366627192-ghcr.io-prompt-edu-prompt-prompt-clients-team-allocation-component-linux-arm64 Expired
244 Bytes
sha256:f2b600b5c5842b183ae827b63dbd0ef0e73b8e56c607cae0e17e0def72027cc4
digests-25366627192-ghcr.io-prompt-edu-prompt-prompt-clients-template-component-linux-amd64 Expired
244 Bytes
sha256:8455aff8164d114adf1cb0d32ce9a97bdbb48959ed14bb97649d94f8644bb2fa
digests-25366627192-ghcr.io-prompt-edu-prompt-prompt-clients-template-component-linux-arm64 Expired
244 Bytes
sha256:b9fd9e2f451a05d0fb335dd0f1ac17cc41cf558c641a5d3258f055ed228b6f25
digests-25366627192-ghcr.io-prompt-edu-prompt-prompt-server-assessment-linux-amd64 Expired
244 Bytes
sha256:7146c3b6047ef5a2fed8d3dc71f8f9287b07c7377b02bc318f7e60faccd48033
digests-25366627192-ghcr.io-prompt-edu-prompt-prompt-server-assessment-linux-arm64 Expired
244 Bytes
sha256:ca20579b9b467843db5fdacee5b63e7ce8bc3331d1afb3bf11607aafcd300b5d
digests-25366627192-ghcr.io-prompt-edu-prompt-prompt-server-certificate-linux-amd64 Expired
244 Bytes
sha256:9239d012b1ff9787ce7a6fc40f6c46a8e979aa7b8abc4f33952776218ee6c563
digests-25366627192-ghcr.io-prompt-edu-prompt-prompt-server-certificate-linux-arm64 Expired
244 Bytes
sha256:6c300184f533d8f48e0ad4a90af6c129d68e324e1073dfc3cf8aa41ac8192778
digests-25366627192-ghcr.io-prompt-edu-prompt-prompt-server-core-linux-amd64 Expired
244 Bytes
sha256:17067dde03342d1abd02ad49f0d8d3c586cd26644c6610bb413cecc48e78609d
digests-25366627192-ghcr.io-prompt-edu-prompt-prompt-server-core-linux-arm64 Expired
244 Bytes
sha256:15c3befb098efb2bccd49c524037216bc6a7b4e04de5ba4a51b40ca4905cc220
digests-25366627192-ghcr.io-prompt-edu-prompt-prompt-server-interview-linux-amd64 Expired
244 Bytes
sha256:e5097ba06feea5f0cc9dd93e912d462be6228cc3331a6bded032b42944ace546
digests-25366627192-ghcr.io-prompt-edu-prompt-prompt-server-interview-linux-arm64 Expired
244 Bytes
sha256:f2f51d4a5e9704ddf5cb813857f4b8bc900edca15317c32c0477cb02fd9e28a1
digests-25366627192-ghcr.io-prompt-edu-prompt-prompt-server-self-team-allocation-linux-amd64 Expired
244 Bytes
sha256:45691b44e3aaaf8aa55abd902fb75b33e3698f613d1aead91912be12626e6d08
digests-25366627192-ghcr.io-prompt-edu-prompt-prompt-server-self-team-allocation-linux-arm64 Expired
244 Bytes
sha256:2006a65e9a764fea08de9922ef037c60f8bab3cf5c3109b80739514bd8a93018
digests-25366627192-ghcr.io-prompt-edu-prompt-prompt-server-team-allocation-linux-amd64 Expired
244 Bytes
sha256:2c53861e2d3a50c57c530c327ef750e88d07c698b3f8ba42b5f773e6609d4c12
digests-25366627192-ghcr.io-prompt-edu-prompt-prompt-server-team-allocation-linux-arm64 Expired
244 Bytes
sha256:c8e39dac596bdc49cdeb9b9569bb57187b627a7fa21f93187cbfe1706c516167
prompt-edu~prompt~0J8H6Y.dockerbuild
70.1 KB
sha256:57fb8ebb0d19566e1cab1a5069ca8aea33b5146e592fa0cc33a46388f59e0155
prompt-edu~prompt~31B1HT.dockerbuild
68.8 KB
sha256:27a9c4111c57bbcbe0e49f3aee1506d8b401dc4bd7d3f783d055c3683cdcbedf
prompt-edu~prompt~3R2TSC.dockerbuild
68.4 KB
sha256:f5d9d6770c9adbd5f6dce1ab2327e2b1a6a50d66a5c9b40ad70c59e27a000891
prompt-edu~prompt~4JS76Z.dockerbuild
71.2 KB
sha256:ab5989f235d5001f7138a2c3b8afe6b78305457efe51c867165e75bf2bcf2da4
prompt-edu~prompt~4P174P.dockerbuild
70 KB
sha256:6d6326263d9115e77bff27c40eacb1ab748a22e834448b13df021c165c552edd
prompt-edu~prompt~609JBK.dockerbuild
69.3 KB
sha256:297ab7809661ab715ea8f5912a4e93856454bc3d43c8ff476d62cf6b32cff36b
prompt-edu~prompt~6157YP.dockerbuild
68.5 KB
sha256:4eedf74fe33790daa6df0c18e97f5c2389b322151dae79be3e13929c9246f7c4
prompt-edu~prompt~6LNN2M.dockerbuild
70.1 KB
sha256:f3f9af4e4652d6352083fd7a33a14ccf4eab8076db195536aa9b836e74011302
prompt-edu~prompt~71BDVN.dockerbuild
71.3 KB
sha256:a573bc02fc5f1351d742795bc02ad6670396fd6601ebd13bf7c36947ddf522ab
prompt-edu~prompt~DJ1L1F.dockerbuild
67.6 KB
sha256:cd1958bddcb8c8db9932bb70fce356b804145a237baaa4dce388ab3c3e7918b1
prompt-edu~prompt~E2JKEN.dockerbuild
69 KB
sha256:5f26760cc324198da18624ed1458133fc14a4c06eeefb7fb6b0671a56e59e2f1
prompt-edu~prompt~FSGLIQ.dockerbuild
69.5 KB
sha256:ab0671ca08c64e16860e2d3f5c97c5d99b973f1f82d2225934ee8f76754a0563
prompt-edu~prompt~MIBW0D.dockerbuild
69.4 KB
sha256:e9d951b66f011444b98a8b7ff141ddcbfa19a166e9d69e4d4133bf8abed781d2
prompt-edu~prompt~MS7QPI.dockerbuild
70.1 KB
sha256:4124b54fa75d4ca8739ad1e83a7d2d9db63b2d30b9930e8fa38ad890c0c88eb5
prompt-edu~prompt~NUOKHS.dockerbuild
70.9 KB
sha256:f492ff6cca0f2269dc963bc50a86b07318371a1176fb8c6ce74c4e848f223af2
prompt-edu~prompt~OBZ5UV.dockerbuild
68.8 KB
sha256:170f49095754bf845c729be344895ae0a95242649505fdfa820b707d9e69b4a9
prompt-edu~prompt~OOPTVC.dockerbuild
68.8 KB
sha256:74d240bb88d0d09bcda5ea3011373090342d5fa3855eb6ad58318db16c9eb6cd
prompt-edu~prompt~OR92N6.dockerbuild
68.8 KB
sha256:87908d9e28dffe6f0bd691f3184d4f770aa80e33caa2781574411038de4e74b8
prompt-edu~prompt~P2OOZY.dockerbuild
70.9 KB
sha256:8fd51f255b71ff6ba466e4493b222e897d728b813545db12ce5d5c3dc8077668
prompt-edu~prompt~QGI5ME.dockerbuild
56.6 KB
sha256:7b4f7cd781e7d14c9adb39ff8f08c25f8de252bdf5e8e8b325f7945e52de4056
prompt-edu~prompt~QSBURQ.dockerbuild
70.8 KB
sha256:e8cac3400907ba8b00df09876f7e3f2a4c8c38235f25f9913f5628b8dbb8db11
prompt-edu~prompt~RVMEWW.dockerbuild
69.8 KB
sha256:39a51fb348f7dd8113a24f6a5f16a2786a38eccd2054837424ca9d9be8a9e404
prompt-edu~prompt~SE3V9R.dockerbuild
68.6 KB
sha256:7a004ca1fcfcf0d5a3ab53145aac93f98b4f9d0f11c514091264a0ae6e60f8fe
prompt-edu~prompt~TOYVR7.dockerbuild
70.7 KB
sha256:d57c219f3342449042c9d61bd60a187e737c6b3214b0de2b3259540da61da22f
prompt-edu~prompt~UY1P2U.dockerbuild
73.2 KB
sha256:1f12c2b35998c2ec09b6aaec00ef98010e39568023070c41137233cf4753024f
prompt-edu~prompt~V00P6O.dockerbuild
75.2 KB
sha256:24a25f75042b40e555fa8fd14f06fc4c461d0881145cd61898bf9c71285fc8cf
prompt-edu~prompt~V1FKU9.dockerbuild
56.4 KB
sha256:e4fa6caac2be576f983c7ede2f6f5056d592d1ec1323476e00854f76af0cbefa
prompt-edu~prompt~WCDT8S.dockerbuild
69.9 KB
sha256:69ec6dd3f9ab922444d74fd5cc04993767862a90373d51e5a7308962150c3c0d
prompt-edu~prompt~WFK3AJ.dockerbuild
71.4 KB
sha256:95a8f1f4752f7e343080d503f84dd11c2769b408efa0e450158d1578b8a4dc01
prompt-edu~prompt~WSNWHT.dockerbuild
72.7 KB
sha256:e69bc95626b92c27161dd9f0aca827848d978c5911d54d54d541be40700a6961
prompt-edu~prompt~XUO1KG.dockerbuild
70.4 KB
sha256:8352268627180b95aeafe44f0a854d656d427ca860123149a67629f2fd613a1f
prompt-edu~prompt~Y1KVN4.dockerbuild
69.5 KB
sha256:667bc4bfab94a58ce31f311ba035a09c257d702be8eed706a95068a9f958394f