From 88e49c1d0fc31c6f5645d596e2339d83c3d74f36 Mon Sep 17 00:00:00 2001 From: "jorisjonkers-dev-agents[bot]" Date: Sun, 28 Jun 2026 21:22:12 +0000 Subject: [PATCH] fix(clients): link npm package to its repo for public visibility MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit The published @jorisjonkers-dev/*-client npm packages had no repository field, so GitHub Packages did not link them to their public source repo and defaulted them PRIVATE — consuming repos (the UIs) got 403 on install (while the linked Maven clients are public). Add a repository field pointing at GITHUB_REPOSITORY so new client publishes inherit public visibility. --- actions/api-client-publish/run.sh | 6 ++++++ 1 file changed, 6 insertions(+) diff --git a/actions/api-client-publish/run.sh b/actions/api-client-publish/run.sh index d056639..ebfbd62 100755 --- a/actions/api-client-publish/run.sh +++ b/actions/api-client-publish/run.sh @@ -259,6 +259,12 @@ const pkg = { import: './dist/index.js', }, }, + // Link the package to its (public) source repo so GitHub Packages inherits PUBLIC visibility + // and consuming repos can install it; without this it defaults to private -> cross-repo 403. + repository: { + type: 'git', + url: `git+https://github.com/${process.env.GITHUB_REPOSITORY || 'JorisJonkers-dev/api-clients'}.git`, + }, publishConfig: { registry: process.env.NODE_REGISTRY_URL, access: 'public',