Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

[Package Removal]: tinyrack.Tinest, tinyrack.TinestCLI, tinyrack.coder, tinyrack.coder-cli

Open Beginner friendly
  • Is something wrong?
#443,402 1 comment 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
65/100
Issue type
Refactor
Clarity
Mostly clear
Activity status
Active
Domain
release

Research direction

The issue identifies four package manifests by identifier but names no files or tests. Start by locating the manifests for tinyrack.Tinest, tinyrack.TinestCLI, tinyrack.coder, and tinyrack.coder-cli in this repository and review the package-removal process. Done means the four obsolete manifests are removed and the requested lowercase names can be republished.

Written by the indexing model from the issue text.

Description

Needs-Triage

Package Identifiers: tinyrack.Tinest (0.9.0), tinyrack.TinestCLI (0.9.0), tinyrack.coder (0.2.0), tinyrack.coder-cli (0.6.0)

Reason for Removal: Publisher request. I publish these packages; this account is the owner of the release repository tinyrack-net/tinest.

  1. tinyrack.coder and tinyrack.coder-cli are the previous names of the product that now ships as Tinest — tinyrack-net/coder redirects to tinyrack-net/tinest, and those identifiers stopped at coder 0.2.0 / coder-cli 0.6.0. They are superseded by the Tinest packages and should be gone.

  2. tinyrack.Tinest and tinyrack.TinestCLI do not match this publisher's established casing. Every other package of ours lives under the lowercase tinyrack directory with a lowercase product name (tinyrack.dotweave, tinyrack.proxer, tinyrack.coder, tinyrack.coder-cli). Since a publisher directory can only have one casing, we would like to remove these manifests and republish the same product as tinyrack.tinest / tinyrack.tinest-cli once the removal is published.

Removal PRs will be linked in a follow-up comment.

Dominant language
No language data
Stars
11.1k
Forks
9.7k
Avg merge
2h 15m
Merged PRs (30d)
733

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from microsoft/winget-pkgs

All issues in microsoft/winget-pkgs

Similar issues

More Release issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.