Gas City publishes first-party reusable packs through the public
gascity-packs registry — a discovery catalog for finding packs to import (the
model lives in
Understanding Packs).
The public main registry is configured by default, so there is nothing to
add. Refresh its catalog before browsing:
Search and inspect entries:
When you decide to use a pack, prefer the import command printed by
gc pack registry show. It writes the durable source URL and selected
version; it does not write the local registry handle into pack.toml.
First-Party Packs
Built-In Packs
Built-in packs (core, bd) are explicit pinned imports gc init writes, not
registry entries — see System Packs for that
contract.
Freshness
Registry records are cached locally, and gc pack registry search/show warn
when the cache is older than the freshness window (default 24 hours). Pass
--refresh to fetch the latest catalog first, or set GC_REGISTRY_FRESHNESS to
a Go duration to change the window:
Publishing
gc pack registry publish <path> submits a pack to the configured registry
service. The hosted registry reviews and lands the change before others see it;
refresh local caches afterward.
Publish Request Updates
After a successful publish, follow the printed request command to check its
status and any Registry feedback:
List your recent requests with gc pack registry requests. This read-only
status report uses your personal Registry login; run gc pack registry login
if you have not logged in yet. A withdrawn request tells you to address the
decision and submit a new request. Last modified on July 29, 2026
