-
Notifications
You must be signed in to change notification settings - Fork 138
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
CI release failure #615
Comments
No worries :) Yes, you need someone to remove the secrets on this repository. See https://github.com/orgs/typelevel/teams/maintainers/discussions/6 for more details. |
Btw, downgrading the plugin won't help, because the change happened externally on sonatype (they moved |
@armanbilge oufff don't have access to this discussion either. |
Oh, I'm sorry about that :( I'm sure @rossabaker can add you to the maintainer team as well, it must have been an oversight. Anyway the discussion just explains what s01 is and says to remove the secrets from the repository. We installed new org-level secrets that they are overriding actually 😆 |
OMG, that's cool. |
I removed the repo credentials, so it should inherit the new org credentials. I also invited @pomadchin to the frameless team, which is a child of the maintainers team, which grants access to announcements like Arman's. If anything's still a mess, please ping me again. |
Thanks @rossabaker 🎉 it all works now! Closing this issue. |
At this point the release is failing (see https://github.com/typelevel/frameless/runs/5435773484?check_suite_focus=true)
I'm wondering, what could have triggered that, since it looks like after merging #614 releases were successful, see https://github.com/typelevel/frameless/actions/runs/1923599368.
@armanbilge do you have any thoughts about it? (sry for pinging you there).
I may also try to downgrade the plugin version to see what is different; another thought is that mb credentials were changed and are moved to s01? (I don't have access to the repo settings, so can't check that).
The text was updated successfully, but these errors were encountered: