[ReenigneArcher]

Description

The package index currently discovers repositories only in LizardByte and requests every repository's releases from that owner. Discover public repositories across the organizations in LizardByte/.github/organizations.json, deduplicate them by GitHub ID, and fetch releases from each repository's current owner.

Keep the existing Sunshine and libvirtualhid asset directories and public download URLs. Qualified retention policies include their GitHub repository IDs so they continue to apply after a transfer. New mirrored repositories default to ID-based directories; duplicate repository names also have distinct release routes and card state. Existing name-based release links remain usable when unambiguous, and search includes the organization name.

Run the synchronization regression tests in the existing update workflow before generating the package index.

Screenshot

Issues Fixed or Closed

Roadmap Issues

Testing

• node --test .github/scripts/*.test.js: all 14 tests passed, including cross-org release owners, duplicate names, transfer-stable retention policies and URLs, existing asset/hash preservation, invalid registry/API failures before cleanup, directory validation, and browser routing.
• actionlint, yamllint, and git diff --check passed.
• Read-only live discovery found 85 public repositories across all five registered organizations. Compared the current published package index against the resolved storage directories: all 29 mirrored-asset URLs keep their exact paths.
• Production dist and Pages branches were not modified. Hosted CI and the existing pull-request package preview will validate the proposed deployment.

Type of Change

• feat: New feature (non-breaking change which adds functionality)
• fix: Bug fix (non-breaking change which fixes an issue)
• docs: Documentation only changes
• style: Changes that do not affect the meaning of the code (white-space, formatting, missing semicolons, etc.)
• refactor: Code change that neither fixes a bug nor adds a feature
• perf: Code change that improves performance
• test: Adding missing tests or correcting existing tests
• build: Changes that affect the build system or external dependencies
• ci: Changes to CI configuration files and scripts
• chore: Other changes that don't modify src or test files
• revert: Reverts a previous commit
• BREAKING CHANGE: Introduces a breaking change (can be combined with any type above)

Checklist

• Code follows the style guidelines of this project
• Code has been self-reviewed
• Code has been commented, particularly in hard-to-understand areas
• Code docstring/documentation-blocks for new or existing methods/components have been added or updated
• Tests have been added or updated for new or modified functionality, including regression tests for bug fixes

AI Usage

See our AI usage policy.

• AI tools were used while preparing this PR

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud