chore: Dev merge to Main#265
Merged
Merged
Conversation
PR #254 (dev -> main) shows infra/main.json on dev was last generated with Bicep CLI 0.42.1.51946, while main is already on 0.43.8.12551. This is a downgrade in the merge surface. Recompiled infra/main.bicep using Azure CLI's bundled Bicep (0.43.8.12551) so the generator metadata on dev matches what's already in main. The bicep source is unchanged; only the four _generator blocks (root + three nested modules) and their templateHash values are updated. Once this lands on dev, regenerating against PR #254 will no longer show a Bicep version downgrade on infra/main.json. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
…grade chore: regenerate infra/main.json with Bicep CLI 0.43.8 (fix PR #254 version downgrade)
Shreyas-Microsoft
requested review from
Avijit-Microsoft,
Dongbumlee,
Prajwal-Microsoft,
Roopan-Microsoft,
Vinay-Microsoft,
aniaroramsft,
dgp10801,
nchandhi,
sethsteenken and
toherman-msft
as code owners
Contributor
There was a problem hiding this comment.
Pull request overview
This pull request updates the generated ARM template at infra/main.json, primarily refreshing the Bicep _generator metadata to a newer Bicep build and making small ordering adjustments within a couple of dependsOn arrays.
Changes:
- Updated Bicep
_generator.versionand correspondingtemplateHashvalues in the template metadata blocks. - Reordered a couple of
dependsOnentries for the Storage and AI Foundry private endpoint nested deployments.
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
refactor: clean up imports and remove unused code across multiple components
Roopan-Microsoft
temporarily deployed
to
production
GitHub Actions
Inactive
Roopan-Microsoft
temporarily deployed
to
production
GitHub Actions
Inactive
Roopan-Microsoft
temporarily deployed
to
production
GitHub Actions
Inactive
Roopan-Microsoft
temporarily deployed
to
production
GitHub Actions
Inactive
Roopan-Microsoft
temporarily deployed
to
production
GitHub Actions
Inactive
Roopan-Microsoft
approved these changes
Jun 1, 2026
Avijit-Microsoft
approved these changes
Jun 1, 2026
|
🎉 This PR is included in version 2.1.1 🎉 The release is available on GitHub release Your semantic-release bot 📦🚀 |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Purpose
This pull request updates the
infra/main.jsoninfrastructure template with a newer Bicep generator version and makes minor corrections to the dependency order for certain resources. The main goal is to ensure the template is generated with the latest tooling and that resource dependencies are properly ordered.Key changes include:
Bicep Generator Update:
0.42.1.51946to0.43.8.12551throughout the template, along with corresponding updates totemplateHashvalues. [1] [2] [3] [4]Dependency Order Corrections:
dependsOnarrays for certain resources to ensure the correct provisioning order, specifically moving thestorageQueueandcognitiveServicesdependencies after their related entries. [1] [2]Does this introduce a breaking change?
Golden Path Validation
Deployment Validation
What to Check
Verify that the following are valid
Other Information