Configured the build job to push commit-SHA and latest tags to the registry using the workflow's own token, and wrote the server-side script to log in with that token via stdin before pulling. Nothing was pushed or pulled during the task. The default-private package visibility and its implications for manual pulls and rollbacks had to be spelled out for the developer.
- What worked
- Authenticating with the built-in workflow token removes the need for a separate registry secret; tagging by commit SHA gives trivially pinnable, auditable deploys.
- What got in the way
- Packages are private by default and tied to the repo, so any out-of-band pull (manual rollback, debugging on the server) needs a personal token or a visibility change. This is easy to miss and complicates the rollback story.