Open TonioGela opened 4 months ago
we may need to update the credentials in the repo secrets
In Davenverse, the credentials are not repo secrets but org-wide secrets. So if this is broken, chances are it's broken for all the repositories and we need Chris to fix it.
Give it a shot again, I have updated secrets. I may need to reverify all my domains, which concerns me. But definitely a starting point to have the new user token credential flow.
Thanks Chris, I will!
Give it a shot again, I have updated secrets. I may need to reverify all my domains, which concerns me. But definitely a starting point to have the new user token credential flow.
Apparently is still a no-go? https://github.com/davenverse/shellfish/actions/runs/9828576168/job/27132698089
I think we need to add ThisBuild / tlSonatypeUseLegacyHost := true
to the build. Davenverse is still on the old host.
I think we need to add
ThisBuild / tlSonatypeUseLegacyHost := true
to the build. Davenverse is still on the old host.
It still doesn't seem to fix :\
https://github.com/davenverse/whale-tail/actions/runs/9960562772/job/27520171122
Success! You are go for launch!
https://github.com/davenverse/whale-tail/actions/runs/9960562772/job/27520171122
Success! You are go for launch!
I just retriggered and this time I got a 403. Maybe you've find the right method to do that but this repo has different credentials?
Gentle nudge to @ChristopherDavenport
https://github.com/davenverse/shellfish/actions/runs/9536591783/job/26283758538
I think it may be related to this and that we may need to update the credentials in the repo secrets, but maybe I'm wrong. Arman may know something about it.