t1k:unity:base:publish-package
| Field | Value |
|---|---|
| Module | base |
| Version | 5.116.6 |
| Effort | medium |
| Tools | — |
Keywords: npm publish, package publish, publish package, publish to registry, registry publish, upm package version, upm publish, upm version bump
How to invoke
Section titled “How to invoke”/t1k:unity:base:publish-packagePublish a TheOne UPM Package (Unity side)
Section titled “Publish a TheOne UPM Package (Unity side)”This skill holds only what is specific to a Unity package. Every registry fact (hosts, name
scopes, auth, size ceiling, errors, the CI route, never-unpublish) lives in the shared
t1k:registry skill (.claude/skills/t1k-registry/, theonekit-core). Read it there; this page
does not repeat it, so it cannot drift from it.
Decision Tree
Section titled “Decision Tree”| Intent | Go to |
|---|---|
| Publish a new version | Unity checklist, then the preflight, then the publish flow |
| “Can I publish this package?” | Preflight: bun .claude/skills/t1k-registry/scripts/registry-publish-preflight.cjs <package-dir> |
| Get or repair a token | t1k:unity:base:upm-auth (Unity editor side), the t1k:registry auth-paths page (publish side) |
| Publish failed (401, 403, 413, 502) | the t1k:registry errors page |
| Tarball too large | the t1k:registry size-limits page |
“I pushed package.json to master and nothing published” | Push-triggered publish |
| “Unity still has the old code after publishing” | Publishing is not shipping |
Unity checklist
Section titled “Unity checklist”Before the preflight:
package.jsoncarries the version you intend to ship, strictly higher than any published one (published versions are immutable; see thet1k:registrypublish-flow page, section Versions). A gap in the sequence is normal, not corruption.- The package keeps the UPM layout:
package.jsonat the package root, runtime and editor code in their own assembly definitions (.asmdef), and a.metafile beside every asset (a missing.metamakes Unity regenerate GUIDs in the consumer). - The package
namefollows the Unity name rule inregistry-facts.json(tenants.upm). The preflight checks it; do not retype the scopes here. - Dependencies in
package.jsonname published versions, not local paths.
Then run the preflight and follow the t1k:registry publish-flow page for the Unity row.
Push-triggered publish
Section titled “Push-triggered publish”A package repo may carry a .github/workflows/upm-publish-dispatcher.yml that fires on a
package.json push to the default branch and sends a package_publish repository_dispatch to
The1Studio/UPMAutoPublisher, whose publish-upm-package.yml does the publish. No dispatcher in the
repo means the push publishes nothing and reports no error. How a repo is registered for that route
is in the t1k:registry publish-flow page (Registering a repo for auto-publish). Mechanism
detail: references/ci-publish-path.md.
Publishing is not shipping
Section titled “Publishing is not shipping”Publishing only makes a version available. It reaches no player until the consuming Unity
project bumps its exact pin in Packages/manifest.json (for example
"com.theone.nativeoverlay": "0.1.10").
That is the difference between “the code is out” and “the code is live”. A publish can therefore happen before device verification with little risk, but the manifest bump is the real gate: nothing reaches players until it lands.
Executed by
Section titled “Executed by”Running the preflight and quoting its lines is mechanical (t1k:registry names the agent). The
version bump and the publish need the operator’s own token, so they run inline in the main
session, not on a sub-agent. Routing SSOT: rules/orchestration-rules.md section
“Task-Type to Agent Routing”.
Documents the Unity-specific half of publishing a UPM package. It does not execute a real publish
on the user’s behalf, and it owns no registry fact and no registry credential: those belong to
t1k:registry and t1k:unity:base:upm-auth.
Related
Section titled “Related”t1k:registry(theonekit-core) — hosts, auth, publish flow, errors, size limits, preflight.t1k:unity:base:upm-auth— Unity-side scoped-registry credentials in~/.upmconfig.toml.references/ci-publish-path.md— the push-triggered dispatcher chain.