fix: resolve GitHub Packages publish pipeline failures#29
Merged
guillaumebadin merged 1 commit intomainfrom Apr 7, 2026
Merged
fix: resolve GitHub Packages publish pipeline failures#29guillaumebadin merged 1 commit intomainfrom
guillaumebadin merged 1 commit intomainfrom
Conversation
The publish-ghp workflow failed on all 3 attempts due to two root causes: 1. publishTo was set at ThisBuild scope, but sbt-typelevel's TypelevelSonatypePlugin overrides it at project scope. Artifacts were sent to central.sonatype.com instead of maven.pkg.github.com. Fix: move publishTo into ghpPublishSettings applied at project scope via the module() function. 2. publish-ghp.sbt contained a duplicate publishTo/credentials block (also at ThisBuild scope) that was equally ineffective. Fix: remove duplicates, keep only gpgWarnOnFailure. Additional fixes: - Update cachix/install-nix-action v17 → v31 (Node.js 20 deprecated) - Fix README: GitHub Packages requires auth even for public repos Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
This was referenced Apr 7, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
publishToscoping: moved fromThisBuildto project scope (viaghpPublishSettingsinmodule()) so it overridessbt-typelevel'sTypelevelSonatypePlugin— this was the root cause of artifacts being sent tocentral.sonatype.cominstead ofmaven.pkg.github.compublish-ghp.sbt(redundantpublishTo+credentialsthat were also ineffective atThisBuildscope)cachix/install-nix-actionv17 → v31 (Node.js 20 deprecation)read:packagesauth even for public reposRoot cause analysis
All 3 publish attempts on April 2 failed because
sbt-typelevel'sTypelevelSonatypePluginsetspublishToat project scope, which beats theThisBuildscope used in bothbuild.sbtandpublish-ghp.sbt. SBT's scope precedence: project > ThisBuild > Global.Test plan
auto-tag.ymlcreatesv0.12.7publish-ghp.ymlruns successfully for all 3 matrix jobs (rootJVM, rootJS, rootNative)https://maven.pkg.github.com/beyond-scale-group/edomata🤖 Generated with Claude Code