microsoft / microsoft/winget-pkgs

Package Request: Genshin Impact

Open
#20,435 6 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

Blocking-Issue Help-Wanted Interactive-Only-Installer Issue-Feature Package-Request
Dominant language
No language data
Stars
11.1k
Forks
9.7k
Avg merge
1h 32m
Merged PRs (30d)
376

Description

Package Requested

  • I would like someone else to build the manifest.
  • I would like help so I can submit the manifest.
  • I have performed a search and couldn't find this package.
  • I think there is a new version available and I have provided the URL.

Manifest:

Fill out as much of the manifest metadata you can:

PackageIdentifier:   miHoYo.GenshinImpact # publisher.package format (example: "Microsoft.WindowsTerminal")
PackageVersion:      2.9.1.0 # version number format x.y.z.a (example: "1.6.10571.0")
PackageLocale:       en-US # meta-data locale (example: "en-US")
Publisher:           miHoYo Co., Ltd. # publisher name (example: "Microsoft Corporation")
PackageName:         Genshin Impact # package name (example: "Windows Terminal")
License:             # package license (example: "MIT")
ShortDescription:    a free-to-play action role-playing game # package description (example: "The new Windows Terminal")
Installers: 
 - Architecture:     x64 # installer architecture (example: "x64")
   InstallerType:    exe # installer type (example: "msix")
   InstallerUrl:     https://genshinimpact.mihoyo.com/client_app/launcher/20210609_faac20994b76230c/GenshinImpact_install_mihoyo_20210525204658.exe # installer URL (should be https://)
   InstallerSha256:  # SHA256 hash calculated from installer
ManifestType: singleton
ManifestVersion: 1.0.0

Contributor guide

Open the contributing guide

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.

Research direction

Start with the YAML manifest block in the issue, checking the proposed PackageIdentifier, version, publisher, package name, and installer URL. A completed manifest should include the missing license and InstallerSha256 values and preserve the shown singleton manifest metadata; no tests or repository files are named.

Written by the indexing model from the issue text.

Assessment

Tech stack
yaml
Domain
tooling
Issue type
Feature
Difficulty
2/5
Estimated time
1-3 hours
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.