microsoft / microsoft/msstore-cli
Add automatic cleanup of obsolete packages
Nobody has claimed this yet.
- Dominant language
- C#
- Stars
- 163
- Forks
- 22
- Avg merge
- 5d 6h
- Merged PRs (30d)
- 10
Description
Description:
Currently, when newer versions of packages are uploaded, older versions remain in the system even though they won't be distributed to customers. It would be beneficial to have an automatic cleanup feature that removes these obsolete packages and avoid submission warnings.
Current Behavior:
- Old package versions remain in the system even after uploading newer versions
- Manual removal is required for obsolete packages
- System shows warnings about packages that won't be distributed due to higher-version packages
Proposed Behavior:
- Automatically detect packages that won't be distributed due to higher versions
- Provide an option to automatically remove these obsolete packages
- Log cleanup actions for tracking purposes
Use Case Example:
When package Packaging_0.1.7.0_x64_ARM64_bundle.msixupload is uploaded and supersedes Packaging_0.1.2.0_x64_ARM64_bundle.msixupload, the older version should be automatically removed since it won't be distributed to customers.
Additional Context:
The web interface provides this feature.
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
The payload names no files or tests; start by locating the package-upload or submission flow that reports warnings for superseded versions. Compare its behavior with the web interface's cleanup feature. Done means an explicit cleanup option detects obsolete packages, logs the cleanup actions, and addresses the described warning scenario.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp
- Domain
- cli
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100