Register with JuliaRegistrator — v0.1.0 #3

Activity

1. hyperpolymath commented on Apr 27, 2026

   

   hyperpolymath

   on Apr 27, 2026

   OwnerAuthor

   More actions

   @JuliaRegistrator register
2. hyperpolymath commented on Apr 30, 2026

   

   hyperpolymath

   on Apr 30, 2026

   OwnerAuthor

   More actions

   @JuliaRegistrator register branch=main
3. hyperpolymath commented on May 16, 2026

   

   hyperpolymath

   on May 16, 2026

   OwnerAuthor

   More actions

   @JuliaRegistrator register
4. hyperpolymath commented on May 16, 2026

   

   hyperpolymath

   on May 16, 2026

   OwnerAuthor

   More actions

   Stage 1 of 4 — UNBLOCKED, register first. Only stdlib dep; nothing waits on it. Everything else in the chain waits on this one.

   ---

   Registration runbook (prep — verified 2026-05-17)

   This is not an independent issue. The four estate Julia packages form a strict dependency chain. AutoMerge in JuliaRegistries/General rejects a package whose estate deps/weakdeps are not yet registered, so they must be registered in this exact order, each fully merged into General before the next is triggered:

   Order	Package	Version	Blocked until	TagBot
   1	AcceleratorGate.jl (#3)	0.1.0	— nothing (only stdlib Dates)	✗ tag manually
   2	KnotTheory.jl (#6)	1.0.1	AcceleratorGate merged in General	✓ release.yml present
   3	Skein.jl (#6)	0.3.1	AcceleratorGate and KnotTheory merged	✗ tag manually
   4	KRLAdapter.jl (#1)	0.1.0	KnotTheory and Skein merged	✗ tag manually

   Tier rationale: Skein has AcceleratorGate in [deps] and KnotTheory in [weakdeps] (compat "1") — General requires weakdeps to be registered too. KRLAdapter has both KnotTheory and Skein in [deps].

   Trigger (per package, when unblocked)

   1. Confirm the JuliaRegistrator GitHub App is installed on hyperpolymath (org-level) — without it the @JuliaRegistrator register comment is inert.
   2. Comment @JuliaRegistrator register on the latest default-branch commit (not just this issue).
   3. ⏳ New-package 3-day hold: first-time registrations sit in General AutoMerge for 3 days unless a JuliaRegistries maintainer merges early. Because the chain is sequential, end-to-end is realistically ~12 days (4 × 3-day holds) absent manual merges.
   4. After the General PR merges: ensure tag vX.Y.Z exists on this repo. Repos without TagBot (release.yml) need it manually:

      git tag vX.Y.Z <registered-commit> && git push origin vX.Y.Z
      

   Project.toml audit — AutoMerge-clean

   name, uuid, version, [compat] for julia and every non-stdlib dep all present and well-formed across all four. No blockers other than the ordering above.
5. hyperpolymath

   closed this as completedon May 19, 2026