microsoft / microsoft/AdaptiveCards
[JS][Infrastructure] Separate daily built packages from a public feed
Open
Nobody has claimed this yet.
Task
- Dominant language
- C#
- Stars
- 2k
- Forks
- 595
- Avg merge
- 1d 19h
- Merged PRs (30d)
- 1
Description
Platform
- JavaScript
Issue
If an ado feed user installs the daily package, it will get added into a feed, and if the feed's upstream has public source such npm js. ADO will block the public sources.
Suggestion
- temporally stop publishing daily builds & re-access if the daily builds are necessary.
- if necessary, add measure of not corrupting a feed with public packages.
- add a scope to daily builds.
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 tracing the daily package publishing flow and the Azure DevOps feed/upstream behavior described in the issue. Define how daily builds should be separated or scoped, then verify that installing them no longer causes a feed with public upstream sources to be blocked.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- azure, javascript
- Domain
- build-system, devops, release
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100