Context: <a class="issue-link js-issue-link" data-error-text="Failed to load title

<a class="issue-link js-issue-link" data-error-text="Failed to load title" data-id="74

<a class="user-mention notranslate" data-hovercard-type="user" data-hovercard-url="/us

Run sbt ci-release failure about scapegoat HOT 5 OPEN

mccartney commented on July 18, 2024

Run sbt ci-release failure

from scapegoat.

Comments (5)

mccartney commented on July 18, 2024 1

sbt/sbt-pgp#182 (comment) hints that this is a Sonatype credential issue.

Which reminds me of my recent problems with releasing an unrelated Maven/Java package. And there it turned out I should no longer use my username + password as credentials to Sonatype, but I should rather generate an Access Token (long-lived).

Therefore:
@sksamuel could you please:

login to https://oss.sonatype.org/
Go to Profile
Pull down User Token
Access User Token
Put these credentials into secrets in this Github repo? SONATYPE_PASSWORD + SONATYPE_USERNAME

(Likely you will need to do the same for other repos of yours)

from scapegoat.

Johnnei commented on July 18, 2024 1

Probably unsurprisingly, running into this for the sbt plugin as well: https://github.com/scapegoat-scala/sbt-scapegoat/actions/runs/9882941292/job/27296750946

from scapegoat.

mccartney commented on July 18, 2024 1

An alternative would probably be to set up a new Sonatype/Maven identity - i.e. new artifacts group/id and discontinue the sksamuel branding. But I wouldn't want to do that without involving Sam.
(the Github org has already shifted some time ago)

from scapegoat.