chore: rename Phase 2 bucket repos to apt-wheels / yum-wheels for naming consistency (#2788)

Phase 2 Linux native-repo templates and dispatch wiring referenced
`wheels-dev/apt-wheels-dev` and `wheels-dev/yum-wheels-dev`. The `-dev`
suffix appeared to mirror the DNS form (`apt.wheels.dev`
→ `apt-wheels-dev`) but reads as a redundant org echo inside the
`wheels-dev` org and breaks the established `<package-manager>-wheels`
naming used by the other sister repos (`homebrew-wheels`,
`scoop-wheels`, `chocolatey-wheels`).

Rename everywhere to drop the `-dev` suffix:

- wheels-dev/apt-wheels-dev → wheels-dev/apt-wheels
- wheels-dev/yum-wheels-dev → wheels-dev/yum-wheels

The actual bucket repos were just created under the new names today
(2026-05-21 ~20:15 UTC), so this PR brings the templates / docs /
release-workflow dispatch in sync with the on-GitHub reality before
the first end-to-end dispatch fires. No live infrastructure references
the old names yet — Cloudflare Pages, DNS, and the bucket-side CI
secrets all post-date this rename.

Mechanical substitution across 9 files (27 references). Stable `wheels`
package name (the bare `wheels` in nfpm configs and `apt install
wheels` snippets) is untouched — only the org-namespaced repo names
change.

Signed-off-by: Peter Amiri <peter@alurium.com>

Author: bpamiri

.github/workflows/release.yml

@@ -23,7 +23,7 @@ on:
       DOWNSTREAM_DISPATCH_TOKEN:
         required: false
       # Optional — when present, the build job's "Dispatch Linux repo buckets"
-      # step fires repository_dispatch on apt-wheels-dev / yum-wheels-dev so
+      # step fires repository_dispatch on apt-wheels / yum-wheels so
       # their metadata regen workflows pick up the new .deb/.rpm and republish
       # apt.wheels.dev / yum.wheels.dev within minutes. When absent, the step
       # skips silently — the bucket repos can be populated manually via each
@@ -306,7 +306,7 @@ jobs:
         # CHANNEL derives from the version so develop snapshots produce the
         # `wheels-be` package (which the Phase 2 bleeding-edge receiver
         # downloads) instead of `wheels`. Without this, the snapshot release
-        # ships `wheels_<v>_amd64.deb` and the apt-wheels-dev / yum-wheels-dev
+        # ships `wheels_<v>_amd64.deb` and the apt-wheels / yum-wheels
         # receiver workflow 404s on its `wheels-be_<v>_amd64.deb` fetch.
         # RC builds keep CHANNEL=stable — RCs aren't fanned out to apt/yum
         # (see release.yml § "Dispatch Linux repo buckets").
@@ -588,8 +588,8 @@ jobs:
       #############################################
       # Dispatch Linux repo buckets (apt.wheels.dev / yum.wheels.dev)
       #
-      # Fires repository_dispatch on wheels-dev/apt-wheels-dev and
-      # wheels-dev/yum-wheels-dev so their metadata-regen workflows pick up
+      # Fires repository_dispatch on wheels-dev/apt-wheels and
+      # wheels-dev/yum-wheels so their metadata-regen workflows pick up
       # the new .deb / .rpm asset and republish apt.wheels.dev /
       # yum.wheels.dev within minutes. See issue #2605.
       #
@@ -616,7 +616,7 @@ jobs:
           fi
 
           # Same channel derivation as the homebrew/scoop dispatch.
-          # apt-wheels-dev / yum-wheels-dev route on `channel` in the payload
+          # apt-wheels / yum-wheels route on `channel` in the payload
           # to slot the .deb/.rpm into the right pool (stable vs bleeding-edge).
           # RC releases aren't currently published to apt/yum, so we skip them.
           if echo "${WHEELS_RELEASE_VERSION}" | grep -qiE '\-snapshot[\.\+]'; then
@@ -632,7 +632,7 @@ jobs:
           # Static event type, fixed repo list — no untrusted input flows into
           # the curl arguments. WHEELS_RELEASE_VERSION is generated earlier in
           # the same workflow from wheels.json + run number.
-          for repo in apt-wheels-dev yum-wheels-dev; do
+          for repo in apt-wheels yum-wheels; do
             echo "Dispatching wheels-released to wheels-dev/${repo}..."
             http_status=$(curl -sS -o /tmp/linux-dispatch-resp.txt -w "%{http_code}" \
               -X POST \

.github/workflows/snapshot.yml

@@ -215,7 +215,7 @@ jobs:
       FORGEBOX_PASS: ${{ secrets.FORGEBOX_PASS }}
       DOWNSTREAM_DISPATCH_TOKEN: ${{ secrets.DOWNSTREAM_DISPATCH_TOKEN }}
       # Optional: when present, the build job's "Dispatch Linux repo buckets"
-      # step fires repository_dispatch on apt-wheels-dev / yum-wheels-dev so
+      # step fires repository_dispatch on apt-wheels / yum-wheels so
       # the bleeding-edge channel of apt.wheels.dev / yum.wheels.dev tracks
       # every develop push. When absent, the step skips silently. See #2605.
       LINUX_REPO_DISPATCH_TOKEN: ${{ secrets.LINUX_REPO_DISPATCH_TOKEN }}

tools/distribution-drafts/apt-repo/README.md

@@ -1,6 +1,6 @@
-# `apt-wheels-dev` bucket repo template
+# `apt-wheels` bucket repo template
 
-This directory is the **template** for the standalone `wheels-dev/apt-wheels-dev`
+This directory is the **template** for the standalone `wheels-dev/apt-wheels`
 repository that backs `https://apt.wheels.dev`. The bucket repo holds the static
 apt metadata tree plus the pooled `.deb` artifacts, and is auto-deployed to
 Cloudflare Pages on every push.
@@ -105,7 +105,7 @@ Before this bucket repo will function:
    the apex domain `apt.wheels.dev`. The build command is empty (the repo
    *is* the static site); the output dir is `./`.
 3. **CI secrets** (set on the bucket repo at
-   `https://github.com/wheels-dev/apt-wheels-dev/settings/secrets/actions`):
+   `https://github.com/wheels-dev/apt-wheels/settings/secrets/actions`):
    - `WHEELS_REPO_GPG_PRIVATE_KEY` — ASCII-armored private key
    - `WHEELS_REPO_GPG_PASSPHRASE` — passphrase
 4. **Upstream dispatch** — the release workflow in `wheels-dev/wheels`

tools/distribution-drafts/apt-repo/templates/index.html

@@ -79,7 +79,7 @@ <h2>Upgrading</h2>
   <pre><code>sudo apt update &amp;&amp; sudo apt upgrade wheels        # or wheels-be</code></pre>
 
   <h2>Signing key</h2>
-  <p>The repository is signed with the Wheels project key. The public half is published at <a href="/wheels.gpg"><code>/wheels.gpg</code></a>. The fingerprint is committed to the <a href="https://github.com/wheels-dev/apt-wheels-dev">source repo</a> in <code>FINGERPRINT</code> for offline verification.</p>
+  <p>The repository is signed with the Wheels project key. The public half is published at <a href="/wheels.gpg"><code>/wheels.gpg</code></a>. The fingerprint is committed to the <a href="https://github.com/wheels-dev/apt-wheels">source repo</a> in <code>FINGERPRINT</code> for offline verification.</p>
 
   <h2>Other platforms</h2>
   <ul>
@@ -89,7 +89,7 @@ <h2>Other platforms</h2>
   </ul>
 
   <footer>
-    <p>Hosted on Cloudflare Pages. Repository contents at <a href="https://github.com/wheels-dev/apt-wheels-dev">wheels-dev/apt-wheels-dev</a>.</p>
+    <p>Hosted on Cloudflare Pages. Repository contents at <a href="https://github.com/wheels-dev/apt-wheels">wheels-dev/apt-wheels</a>.</p>
   </footer>
 </main>
 </body>

tools/distribution-drafts/apt-repo/workflows/wheels-released.yml

@@ -1,4 +1,4 @@
-# Receiver workflow for `wheels-dev/apt-wheels-dev`.
+# Receiver workflow for `wheels-dev/apt-wheels`.
 #
 # Listens for `repository_dispatch` from `wheels-dev/wheels`'s release workflow,
 # downloads the new `.deb` asset from the upstream GitHub Release, slots it

tools/distribution-drafts/linux-packages/README.md

@@ -65,8 +65,8 @@ Practical impact for this directory:
 Two new repos (separate from the source monorepo, mirroring the snapshots-repo
 pattern):
 
-- `wheels-dev/apt-wheels-dev` — Cloudflare Pages site at `apt.wheels.dev`
-- `wheels-dev/yum-wheels-dev` — Cloudflare Pages site at `yum.wheels.dev`
+- `wheels-dev/apt-wheels` — Cloudflare Pages site at `apt.wheels.dev`
+- `wheels-dev/yum-wheels` — Cloudflare Pages site at `yum.wheels.dev`
 
 Each repo holds the static metadata tree (Packages.gz, repodata/, etc.) plus
 the `.deb` / `.rpm` files in a `pool/` directory. A CI workflow listens for
@@ -129,27 +129,27 @@ The remaining work is operational:
    `wheels.gpg` (template placeholders live at
    `<bucket>/templates/wheels.gpg.placeholder`).
 2. **Create the two bucket repos** under `wheels-dev`:
-   - `wheels-dev/apt-wheels-dev` — copy contents of `apt-repo/` template
-   - `wheels-dev/yum-wheels-dev` — copy contents of `yum-repo/` template
+   - `wheels-dev/apt-wheels` — copy contents of `apt-repo/` template
+   - `wheels-dev/yum-wheels` — copy contents of `yum-repo/` template
 3. **Create two CF Pages projects** pointing at the new repos, binding the
    apex domains:
-   - `wheels-dev/apt-wheels-dev` → `apt.wheels.dev`
-   - `wheels-dev/yum-wheels-dev` → `yum.wheels.dev`
+   - `wheels-dev/apt-wheels` → `apt.wheels.dev`
+   - `wheels-dev/yum-wheels` → `yum.wheels.dev`
 4. **Add CI secrets** to `wheels-dev/wheels` (for the dispatch sender) and to
    each bucket repo (for the signing receiver):
    - On `wheels-dev/wheels`:
      - `LINUX_REPO_DISPATCH_TOKEN` — fine-grained PAT with `actions: write`
        on both bucket repos. The dispatch step in `release.yml` skips
        silently when this secret is unset, so it's safe to land the wiring
        before the bucket repos exist.
-   - On each bucket repo (`apt-wheels-dev`, `yum-wheels-dev`):
+   - On each bucket repo (`apt-wheels`, `yum-wheels`):
      - `WHEELS_REPO_GPG_PRIVATE_KEY` — ASCII-armored private key
      - `WHEELS_REPO_GPG_PASSPHRASE` — passphrase
 5. **Smoke-test** by running the bucket-repo workflows manually (each
    supports `workflow_dispatch` for backfill). For the apt bucket:
    ```
    gh workflow run wheels-released.yml \
-     --repo wheels-dev/apt-wheels-dev \
+     --repo wheels-dev/apt-wheels \
      -f version=4.0.0 -f channel=stable
    ```
    then verify the published tree on a fresh Debian/Ubuntu host. Do the same

tools/distribution-drafts/yum-repo/README.md

@@ -1,6 +1,6 @@
-# `yum-wheels-dev` bucket repo template
+# `yum-wheels` bucket repo template
 
-This directory is the **template** for the standalone `wheels-dev/yum-wheels-dev`
+This directory is the **template** for the standalone `wheels-dev/yum-wheels`
 repository that backs `https://yum.wheels.dev`. The bucket repo holds the
 static yum metadata tree plus the pooled `.rpm` artifacts, and is auto-deployed
 to Cloudflare Pages on every push.
@@ -79,7 +79,7 @@ so `rpmvercmp` orders snapshot releases below the next GA correctly.
 Same GPG key as the apt repo (one key for both, importable on both clients
 via `https://apt.wheels.dev/wheels.gpg` or `https://yum.wheels.dev/wheels.gpg`).
 
-CI secrets on `https://github.com/wheels-dev/yum-wheels-dev/settings/secrets/actions`:
+CI secrets on `https://github.com/wheels-dev/yum-wheels/settings/secrets/actions`:
 - `WHEELS_REPO_GPG_PRIVATE_KEY` — ASCII-armored private key
 - `WHEELS_REPO_GPG_PASSPHRASE` — passphrase
 

tools/distribution-drafts/yum-repo/templates/index.html

@@ -72,7 +72,7 @@ <h2>Upgrading</h2>
   <pre><code>sudo dnf upgrade wheels        # or wheels-be</code></pre>
 
   <h2>Signing key</h2>
-  <p>The repository is signed with the Wheels project key. The public half is published at <a href="/wheels.gpg"><code>/wheels.gpg</code></a>. Both <code>.repo</code> files reference it via <code>gpgkey=</code>, so <code>dnf</code> imports it automatically on first refresh. The fingerprint is committed to the <a href="https://github.com/wheels-dev/yum-wheels-dev">source repo</a> in <code>FINGERPRINT</code> for offline verification.</p>
+  <p>The repository is signed with the Wheels project key. The public half is published at <a href="/wheels.gpg"><code>/wheels.gpg</code></a>. Both <code>.repo</code> files reference it via <code>gpgkey=</code>, so <code>dnf</code> imports it automatically on first refresh. The fingerprint is committed to the <a href="https://github.com/wheels-dev/yum-wheels">source repo</a> in <code>FINGERPRINT</code> for offline verification.</p>
 
   <h2>Other platforms</h2>
   <ul>
@@ -82,7 +82,7 @@ <h2>Other platforms</h2>
   </ul>
 
   <footer>
-    <p>Hosted on Cloudflare Pages. Repository contents at <a href="https://github.com/wheels-dev/yum-wheels-dev">wheels-dev/yum-wheels-dev</a>.</p>
+    <p>Hosted on Cloudflare Pages. Repository contents at <a href="https://github.com/wheels-dev/yum-wheels">wheels-dev/yum-wheels</a>.</p>
   </footer>
 </main>
 </body>

tools/distribution-drafts/yum-repo/workflows/wheels-released.yml

@@ -1,4 +1,4 @@
-# Receiver workflow for `wheels-dev/yum-wheels-dev`.
+# Receiver workflow for `wheels-dev/yum-wheels`.
 #
 # Listens for `repository_dispatch` from `wheels-dev/wheels`'s release workflow,
 # downloads the new `.rpm` asset from the upstream GitHub Release, slots it