Skip to content

refactor: Remove legacy claim-based restrictions from chat command se… #268

refactor: Remove legacy claim-based restrictions from chat command se…

refactor: Remove legacy claim-based restrictions from chat command se… #268

Triggered via push June 4, 2026 11:22
Status Success
Total duration 5m 35s
Artifacts 2

deploy-prd.yml

on: push
detect-changes
6s
detect-changes
terraform-state-check-dev
23s
terraform-state-check-dev
build-and-test
2m 0s
build-and-test
terraform-plan-and-apply-dev
25s
terraform-plan-and-apply-dev
app-service-deploy-dev
1m 20s
app-service-deploy-dev
terraform-plan-and-apply-prd
27s
terraform-plan-and-apply-prd
app-service-deploy-prd
1m 9s
app-service-deploy-prd
Fit to window
Zoom out
Zoom in

Annotations

2 warnings
app-service-deploy-dev
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: azure/webapps-deploy@v3.0.1. 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/
app-service-deploy-prd
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: azure/webapps-deploy@v3.0.1. 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/

Artifacts

Produced during runtime
Name Size Digest
XtremeIdiots.Portal.Web
53.3 MB
sha256:e1785bf7f4d85da9fb76acbbd4c1922b5a98702a0b363fad0d81ba1dc1edbf0c
test-results-XtremeIdiots.Portal.Web
38.5 KB
sha256:f5fbc7ef013347afacee2bd544b4e14c1c04b216acff1a737285de2fed223efd