microsoft / microsoft/react-native-windows
Update release.yml to be properly classified as a 1ES release pipeline
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 17.3k
- Forks
- 1.2k
- Avg merge
- 1d 13h
- Merged PRs (30d)
- 33
Description
Problem Description
We used the 1ES tooling to create our release.yml pipeline, but it looks like it's not actually configured as a release pipeline. Release pipelines have different features: https://eng.ms/docs/cloud-ai-platform/devdiv/one-engineering-system-1es/1es-docs/1es-pipeline-templates/features/releasepipelines/overview
Steps To Reproduce
See release.yml
Expected Results
No response
CLI version
npx @react-native-community/cli -v
Environment
npx @react-native-community/cli info
Community Modules
No response
Target Platform Version
None
Target Device(s)
No response
Visual Studio Version
None
Build Configuration
None
Snack, code example, screenshot, or link to a repository
No response
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by inspecting release.yml and the linked 1ES release-pipeline documentation. Compare the pipeline configuration with the documented requirements, then verify that release.yml is classified as a release pipeline.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions
- Domain
- ci-cd, release
- Issue type
- Refactor
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100