microsoft / microsoft/json-schemas
Deployment is broken?
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 159
- Forks
- 134
- Avg merge
- 10d 15h
- Merged PRs (30d)
- 7
Description
The problem
We recently merged an update in PR https://github.com/microsoft/json-schemas/pull/115, which can be seen here:
However 24 hours later, the CDN deployed file is still missing the new choiceList item:
https://developer.microsoft.com/json-schemas/rush/v5/command-line.schema.json
Possible regression?
@DevArvindsa Maybe the json-schemas deployment was broken by your recent change in https://github.com/microsoft/json-schemas/commit/04df5431a9aaca9aa5ba24d49da36ad23c5f3c3f ? Could someone from Microsoft investigate? Thanks!
CC @iclanton @apostolisms @EscapeB
Contributor guide
No contributing guide indexed for this repository
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 comparing rush/v5/command-line.schema.json on the referenced main and live revisions with the CDN copy. Review PR 115 and commit 04df5431a9aaca9aa5ba24d49da36ad23c5f3c3f to trace the deployment path and identify why the update was not published. Done means the CDN file contains the new choiceList item and deployment behavior is understood.
Written by the indexing model from the issue text.
Assessment
- Domain
- cloud, devops, release
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100