Skip to content

Updated azure.yaml file to exclude the 1.23.9 azd version (#121) #86

Updated azure.yaml file to exclude the 1.23.9 azd version (#121)

Updated azure.yaml file to exclude the 1.23.9 azd version (#121) #86

Triggered via push March 26, 2026 12:01
Status Success
Total duration 45m 21s
Artifacts
azd template validation
45m 14s
azd template validation
Fit to window
Zoom out
Zoom in

Annotations

3 errors and 2 warnings
azd template validation
Process completed with exit code 1.
azd template validation
One or more assertions failed. One or more errors occured.
azd template validation
Bicep (0.41.2) compilation of '/home/runner/work/Deploy-Your-AI-Application-In-Production/Deploy-Your-AI-Application-In-Production/infra/main.test.bicep' failed with: /home/runner/work/Deploy-Your-AI-Application-In-Production/Deploy-Your-AI-Application-In-Production/infra/main.bicep(11,24) : Error BCP091: An error occurred reading file. Could not find a part of the path '/home/runner/work/Deploy-Your-AI-Application-In-Production/Deploy-Your-AI-Application-In-Production/submodules/ai-landing-zone/bicep/infra/common/types.bicep'. [https://aka.ms/bicep/core-diagnostics#BCP091]
azd template validation
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-node@v4, azure/login@v2, Azure/setup-azd@v2. 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/
azd template validation
Using invariant culture may cause rule infomation to be displayed incorrectly. Consider using -Culture or set the Output.Culture option.