bicep breaking changes
Bicep, published as Azure/bicep.
Azure
Latest v0.49.2, released · 1 release that lists breaking changes in the last 12 months
Pick your version
Every release from v0.2.3 up to v0.49.2: 5 releases with breaking changes, 6 changes
Breaking changes
v0.43.1
- [BREAKING CHANGE] Block usage of custom domains for ACR (#19564)
v0.29.45
- Replace the provider keyword with the extension keyword (#14379)
- Deprecate provider in Bicep configuration files (#14468)
v0.23.1
- [BREAKING CHANGE] Changes to our Module Manifests (#12057)
v0.17.1
- Name resolution & scoping behavior for variables declared in lambdas & for loops is now consistent with variables declared at the global scope. This means that previously, the following would have been permitted, whereas now it is blocked: See #10657 for more detail.
v0.4.1272
- [BREAKING CHANGE] Renamed linter rule error code for commandToExecute (#5591) use-protectedsettings-for-commandtoexecute-secrets has been renamed to protect-commandtoexecute-secrets If you have chosen to disable the rule in bicepconfig.json or via the #disable-next-line directive, you will need to use the new error code. Apologies for not making this known further in advance.