[ReenigneArcher]

Description

Authorize shared CI, coverage uploads, and publishing from the organizations registered in organizations.json. A reusable check reads the trusted registry from master, rejects malformed or unavailable data, and leaves ordinary fork test builds enabled. Replicated wrappers delegate owner checks to the shared workflows; controller-only jobs retain their restrictions.

Preserve existing container/package namespaces and central website, Homebrew, pacman, and WinGet destinations after repository transfers. Cross-org GitHub npm publishing accepts the bot token for the existing LizardByte package namespace.

Run Dependabot validation, Renovate validation, and the full repository test suite in one validate job with one dependency installation. Branch protection should require validate for these checks.

Merge this foundation before the active projects' workflow PRs, then review the replicator's delivery PRs before transferring repositories. Archived connectors remain archived.

Screenshot

Issues Fixed or Closed

Roadmap Issues

Testing

npm test: 189 tests passed, including registry authorization, failure handling, fork behavior, and publishing guards. These tests run through __validate-config.yml, which installs dependencies once, validates Dependabot and Renovate configuration, and invokes the full suite. npm run validate-dependabot also passed locally.

Actionlint 1.7.12 (shellcheck/pyflakes disabled) and yamllint 1.38.0 passed for the changed/new YAML workflows. git diff --check passed. No release or external provider writes were performed; hosted checks are pending.

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