[New Feature]: Retire legacy SST OpenCode package identifiers
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 68/100
- Issue type
- Feature
- Clarity
- Clearly specified
- Activity status
- Active
- Tech stack
- github, json
- Domain
- release
Research direction
Start by locating the manifests for SST.opencode and SST.OpenCodeDesktop and identify the oldest package version directory. For one version, delete only its manifest files, link the pull request to this tracking issue, and leave other versions unchanged. Done means the pull request removes that single version’s manifests and is independently reviewable.
Written by the indexing model from the issue text.
Description
Description of the new feature/enhancement
Retire the legacy community-maintained SST.opencode and SST.OpenCodeDesktop package identifiers now that the upstream publisher is submitting the official Anomaly.OpenCode and Anomaly.OpenCode.Desktop identifiers.
Each historical package version will be removed in a separate pull request so every catalog change remains independently reviewable and reversible.
Proposed technical implementation details (optional)
Process versions from oldest to newest. Each pull request deletes only the manifest files in one package version directory, links this tracking issue, and leaves all other package versions unchanged.
- Dominant language
- No language data
- Stars
- 11.3k
- Forks
- 11.8k
- Avg merge
- 6h 46m
- Merged PRs (30d)
- 435
Getting set up
- No Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing 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.
More from microsoft/winget-pkgs
-
Help-Wanted Needs-Triage Package-Update
Difficulty 1/5 Under an hour Newbie friendliness 72/100
microsoft/winget-pkgs#473210 ·
Maintainers usually reply within 1 day
-
[Package Issue]: hadc188.Reader is being mistaken for Readwise Reader, which doesn't exist in WingetPossibly taken @SpecterShell claimed this 30 days ago. OpenIssue-Bug
Difficulty 2/5 1-3 hours Newbie friendliness 60/100
microsoft/winget-pkgs#471494 ·
Maintainers usually reply within 1 day
-
[Package Request]: FileZilla Server for Windows (64bit x86)Possibly taken @akhil9tiet claimed this 1 day ago. OpenHelp-Wanted Needs-Triage Package-Request
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
microsoft/winget-pkgs#471389 · 2 comments ·
Maintainers usually reply within 1 day
-
[Update Request]: Java 8 Update 511 b33Possibly taken @akhil9tiet claimed this 1 day ago. OpenHelp-Wanted Needs-Triage Package-Update
Difficulty 1/5 Under an hour Newbie friendliness 72/100
microsoft/winget-pkgs#471333 · 3 comments ·
Maintainers usually reply within 1 day
-
Needs-Triage
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
microsoft/winget-pkgs#471261 ·
Maintainers usually reply within 1 day
All issues in microsoft/winget-pkgs
Similar issues
-
0.kind: enhancement 9.needs: package (update)
Difficulty 2/5 1-3 hours Newbie friendliness 66/100
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 84/100
cline/mcp-marketplace#3597 ·
-
3.3.0 .deb is missing the libssl3t64 dependency, so hex fails to start on distros with OpenSSL 4Open
Difficulty 1/5 Under an hour Newbie friendliness 84/100
Maintainers usually reply within 1 day
-
package-update
Difficulty 1/5 Under an hour Newbie friendliness 72/100
oSoWoSo/oco#888 · 2 comments ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day