feat(deploy-bicep): expose bicep-version input#149
Merged
vatsalyagoel merged 2 commits intomainfrom May 6, 2026
Merged
Conversation
Forwards a new optional `bicep-version` input through to both the what-if and deploy `azure/bicep-deploy` steps. When unset, behaviour is unchanged: bicep-deploy resolves https://downloads.bicep.azure.com/releases/latest at runtime, which is non-deterministic across runs and exposes consumers to silent breakage on new Bicep releases. Consumers can now opt into a deterministic Bicep version per call, matching the pattern in Azure/bicep-deploy v2.3.0+ but keeping the wrapper's portal-link and what-if niceties. Tracking issue: Azure/bicep#19600 — newer Bicep versions may stop emitting the 2.1-experimental ARM language version that the @RetryOn decorator relies on, so consumers using @RetryOn need to pin.
Contributor
🛡️ SHA Pinned Actions Report✅ All 28 file(s) passed — actions are allowed and pinned as required. |
Replaces abbreviated version comments (# v6, # v7, # v3, etc.) with full release tags (# v6.0.2, # v7.0.1, # v3.0.0, ...) on every SHA-pinned action across this repo's workflows and composite actions. Pure documentation change — no SHAs altered, no behaviour change. Makes it obvious at a glance which exact release every pinned SHA corresponds to, instead of having to look it up. Skipped: peter-evans/repository-dispatch in zendesk_github_*.yml — current SHA 0fbcdc30 is an unreleased commit on main (post-v4.0.1 dependabot dev-deps bump), so there's no released tag to point at.
cuzzlor
approved these changes
May 6, 2026
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
2 participants
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.
Summary
Adds an optional
bicep-versioninput on thedeploy-bicepcomposite action, forwarded through to both the what-if and deployazure/bicep-deploysteps.When unset, behaviour is unchanged:
bicep-deployresolveshttps://downloads.bicep.azure.com/releases/latestat runtime, which is non-deterministic per run and silently exposes consumers to new Bicep releases.Why
Azure/bicep#19600 — newer Bicep versions may stop emitting the 2.1-experimental ARM language version that the
@retryOndecorator relies on. Consumers using@retryOnneed to pin to a known-good Bicep version (e.g. 0.43.1). Today there's no way to pin through this wrapper.Test plan