Feature band release PRs timing issue
- Dominant language
- No language data
- Stars
- 287
- Forks
- 145
- Avg merge
- 1d 22h
- Merged PRs (30d)
- 10
Description
When generating release PRs for feature bands, the pipeline logic relies on the public release metadata to indicate what the latest SDK release is. This creates a timing issue. The pipeline logic may run before the releases.json file gets updated. That may cause a PR to be created for a feature band that is EOL. See an example of this: https://github.com/dotnet/dotnet/pull/8237
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by reviewing the pipeline logic that uses public release metadata and the releases.json file, then compare its behavior with the example PR #8237. Done means the pipeline no longer creates a release PR for an EOL feature band when releases.json has not yet been updated.
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
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 52/100