Skip to content

Org TODO: fleet migration, registrations, and QAtlasHub roadmap #15

Open
Open
Org TODO: fleet migration, registrations, and QAtlasHub roadmap#15

Description

@sotashimozono
sotashimozono
opened on Jul 12, 2026

Tracking issue for the remaining QAtlasHub work after the org transfer + reusable-CI buildout.

🚧 Blocked on the General registry

The repo URL-change PRs must merge before these packages can register new versions (JuliaRegistrator blocks the URL change otherwise):

📦 Fleet migration to reusable workflows (@v1)

Done: ParamIO / DataVault / AbstractQAtlas are fully migrated (every workflow → thin @v1 caller, templates inherited, gate scripts removed).

  • QAtlas — full migration + AutoMerge stack. Waits for #160861 (don't pile version-bump PRs onto a stuck release flow). Also untangle: main 0.25.3 unregistered, cleanup PR #735 (0.25.4) open.
  • Pinax — full migration, after its docs/usability rework.

🔑 Registrations & credentials

  • Pinax — General new-package PR #159237 records the OLD sotashimozono/Pinax.jl URL (pre-transfer). Re-trigger @JuliaRegistrator register from QAtlasHub so the first registration records the new URL (avoids a future URL-change block).
  • doiget — crates.io Trusted Publisher re-registration for all 3 crates (doiget-core/cli/mcp) after the org move — doiget#392.
  • CODECOV_TOKEN — add as org secret to enable fleet coverage (deferred; julia-ci already wired for it).

🧭 Roadmap (bigger)

  • QAtlasRegistry — the cross-validated evidence registry. RFC: QAtlas#733; Phase-1 CMC-side corroboration cards: ClassicalMonteCarlo#50. (Repo QAtlasHub/QAtlasRegistry created, empty.)
  • ParaTensor org — private/closed self-hosted org for the tensor/research-front packages (ITensor*/ThermalMPS/REB/ParaLA/ComplexTime*/WilsonNRG/…). Org-level Rosina runner group; reuse doiget-citation-check; own .github with self-hosted defaults.
  • QAtlasHub.github.io — org website content (repo created, empty).

✅ Done this round (for reference)

Org .github complete: 12 reusable workflows + release-notes action + org-default FUNDING/dependabot/issue-PR templates/health files/profile + actionlint self-CI + @v1 tag. BOT_PAT (classic) → CompatHelper PRs trigger CI + auto-merge (validated on DataVault). doiget-citation-check@v1 published.

Activity

  1. JuliaRegistrator commented on Jul 12, 2026

    @JuliaRegistrator
    JuliaRegistrator
    on Jul 12, 2026

    Error while trying to register: Register Failed
    @sotashimozono, it looks like you are not a publicly listed member/owner in the parent organization (QAtlasHub).
    If you are a member/owner, you will need to change your membership to public. See GitHub Help

  2. sotashimozono commented on Sep 10, 2026

    @sotashimozono
    sotashimozono
    on Sep 10, 2026
    MemberAuthor

    Item-by-item, measured 2026-09-10.

    🚧 "Blocked on the General registry" — done
    QAtlas — General#160861 (URL change) MERGED 2026-07-13
    ParamIO — General#160862 MERGED 2026-07-13
    DataVault — General#160863 MERGED 2026-07-13

    And the version bumps they were blocking went through:

    QAtlas          0.31.17
ParamIO         0.4.9
DataVault       0.8.0
AbstractQAtlas  0.6.8
TestShards      0.3.40

    🔑 Registrations

    • Pinax — not registered. The PR this issue names, General#159237 (New package: Pinax v0.37.2), is CLOSED. A fresh @JuliaRegistrator register is needed; the old link is dead.
    • ExperimentalAPI — in flight, General#167674 (v0.1.0), all AutoMerge guidelines met, three-day clock running. Its earlier attempt (#166832, v0.1.1) is closed — AutoMerge accepts only 0.0.1 / 0.1.0 / 1.0.0 / X.0.0 as a new package's first version, which 0.1.1 is not.

    📦 Fleet migration

    • QAtlas was waiting on #160861, which merged two months ago. No longer blocked.
    • Pinax still to migrate.

    The registry section can be ticked off entirely. What is left in this issue is Pinax — registration and migration — plus the QAtlas migration that is now unblocked.

    [noblock]

  3. JuliaRegistrator commented on Sep 10, 2026

    @JuliaRegistrator
    JuliaRegistrator
    on Sep 10, 2026

    Error while trying to register: "File (Julia)Project.toml not found"

  4. sotashimozono commented on Sep 10, 2026

    @sotashimozono
    sotashimozono
    on Sep 10, 2026
    MemberAuthor

    Correction to my previous comment — the Pinax line was wrong.

    I said a fresh @JuliaRegistrator register was needed. It is not. I searched for the PR this issue names and stopped there; there is a live one.
    General#167419 — New package: Pinax v0.1.0 OPEN, created 2026-09-07T12:54Z
    AutoMerge guidelines all met ✅ (bot comment, 13:04Z)
    mandatory three-day wait elapses 2026-09-10T12:54Z

    Two closed attempts precede it — #159237 (v0.37.2) and #166879 (v0.39.26) — and both failed for the same reason ExperimentalAPI's #166832 did: AutoMerge accepts only 0.0.1 / 0.1.0 / 1.0.0 / X.0.0 as a new package's first version. v0.1.0 is the version that works, and Project.toml was rolled back to match.

    One thing not to be misled by, since I nearly was: the AutoMerge-regular (1.12) check on that PR shows FAILURE, from the run that started eight seconds after the PR was created. The "all guidelines met" comment came ten minutes later and the later runs are skipped — skipped because the waiting period had not elapsed, which is the normal state until it does.

    So Pinax's registration needs nothing. The remaining Pinax item in this issue is the fleet migration to the reusable workflows, not registration.

    [noblock]

  5. JuliaRegistrator commented on Sep 10, 2026

    @JuliaRegistrator
    JuliaRegistrator
    on Sep 10, 2026

    Error while trying to register: "File (Julia)Project.toml not found"

  6. sotashimozono commented on Oct 15, 2026

    @sotashimozono
    sotashimozono
    on Oct 15, 2026
    MemberAuthor

    Hermes の整理（自動。何も変更していません）

    状態: 2026-10-15 時点で本文と 9/10 コメントを現状と突き合わせた。

    • Registrations: Pinax は New package: Pinax v0.1.0 JuliaRegistries/General#167419 が MERGED（2026-09-10T12:56Z）、ExperimentalAPI は General#167674 が MERGED（2026-09-12T23:37Z）。9/10 コメントの「in flight」は両方完了。
    • doiget#392（crates.io Trusted Publisher）は CLOSED（2026-08-22）。ただし実際に 3 crates の再登録が済んだかは 要確認（issue の close 状態のみ確認）。
    • CODECOV_TOKEN: org secrets に CODECOV_TOKEN と BOT_PAT が存在する（orgs/QAtlasHub/actions/secrets）。本文の「CODECOV_TOKEN org secret（deferred）」は解消済みに見える。
    • Fleet migration: Pinax.jl の CI.yml は QAtlasHub/TestShards.jl/.github/workflows/sharded-tests.yml@main を呼ぶが、Documentation.yml は inline の steps。QAtlas.jl の CI.yml は reusable 呼び出しが無く inline。どちらも「.github の @v1 reusable への完全移行」には見えない（要確認。org の方針が TestShards へ移ったため @v1 の定義自体が変わった可能性: .githubRetire julia-ci.yml — its three callers have moved to TestShards #22 / ci: track the hub's main instead of the @v1 tag #21 参照）。
    • Roadmap: QAtlasRegistry は empty repo のまま、QAtlasHub.github.io は LICENSE のみ。

    次の一手: チェックボックスを現状に合わせて更新し、残りを (a) QAtlas / Pinax の CI 移行方針の再確認、(b) QAtlasRegistry, ParaTensor org, QAtlasHub.github.io の roadmap に絞る。

    関連: #23（docs URL）、QAtlas#733 / ClassicalMonteCarlo#50（本文の roadmap 項目。今回は未確認）。

    close 候補（提案のみ。閉じていません）: 現時点では無し。roadmap が残るため。Registrations と Blocked 節を完了扱いにした上で、残りを別 issue に切り出すなら本 issue は閉じられる、という整理（confidence low）。

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions