fix(ci): publish github package under org scope#4
Conversation
Greptile SummaryCorrects the GitHub Packages scope in both Confidence Score: 5/5Safe to merge — a one-line scope rename in each workflow file with no logic changes. Both files contain a single, consistent string substitution ( No files require special attention. Important Files Changed
Sequence DiagramsequenceDiagram
participant GH as GitHub Actions
participant CI as ci.yml (dry_run=true)
participant PUB as publish.yml (on release)
participant NPM as npm registry (@tummycrypt/*)
participant GHP as GitHub Packages (@tinyland-inc/*)
GH->>CI: push / PR to main
CI->>GH: js-bazel-package workflow (dry run, no publish)
GH->>PUB: release published / workflow_dispatch
PUB->>NPM: publish @tummycrypt/tinyland-activitypub (NPM_TOKEN)
PUB->>GHP: publish @tinyland-inc/tinyland-activitypub (GITHUB_TOKEN)
Reviews (1): Last reviewed commit: "fix(ci): publish github package under or..." | Re-trigger Greptile |
Fixes the GitHub Packages mirror scope from the public npm scope to the GitHub org scope.
The public npm artifact remains under
@tummycrypt/*; this only changes thegithub_package_nameinput used by the reusable publish workflow so GitHub Packages publishes under@tinyland-inc/*.Tracking: TIN-713