Publish provider artifacts (using minor version to start off)
- Dominant language
- Bicep
- Stars
- 3.6k
- Forks
- 830
- Avg merge
- 1d 21m
- Merged PRs (30d)
- 79
Description
## Context
This is a subtask of https://github.com/Azure/bicep/issues/10662.
In order for the bicep compiler to consume a provider types package we first need to be able to publish this package to the public Bicep registry.
## Acceptance Criteria
- A manually triggered CI job can publish the `az` provider package as an OCI artifact to the Bicep public registry given a manually entered package version
Contributor guide
Research direction
The issue names no files, tests, or entry points. Start by locating the CI workflow and the `az` provider package, then determine how a manually entered version can publish it as an OCI artifact to the public Bicep registry. Done means the manually triggered job publishes the package successfully with the supplied version.
Written by the indexing model from the issue text.
Assessment
- Domain
- ci-cd, release
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100