Oliver Bertuch (May 09 2025 at 05:52): Oliver Bertuch (May 09 2025 at 05:52):OSSRH is sunsetting on 6/30/2025. We need to migrate all of our namespaces and adapt our build processes.
Philip Durbin 🚀 (May 09 2025 at 12:46):Yikes, would you be willing to create an issue about this? In the main repo. We can also create sub issues, per repo.
Oliver Bertuch (May 09 2025 at 13:04):I can, but not now. Maybe late next week. Need to go juggle kids around... :face_with_peeking_eye:
Philip Durbin 🚀 (May 09 2025 at 13:28):Are some of our repos using the old way and some using the new? Or are they all old?
Oliver Bertuch (May 09 2025 at 14:49):All old
Philip Durbin 🚀 (May 09 2025 at 14:53):
Philip Durbin 🚀 (May 09 2025 at 14:54):Thanks for bringing this to our attention! :grimacing:
Oliver Bertuch (May 09 2025 at 14:56):It's just because Sonatype sent me a mail ala hey as you probably are aware already... :innocent:
Philip Durbin 🚀 (May 09 2025 at 14:58):Yeah, I got it too:
Greetings OSSRH Publisher,
As you may have heard, OSSRH is reaching end of life on June 30, 2025. OSSRH users need to migrate their namespaces to the Central Portal as soon as possible.
Instructions for self migration are located here: https://central.sonatype.org/faq/what-is-different-between-central-portal-and-legacy-ossrh/#self-service-migration
To make the transition smoother we will be automatically migrating publishers that have not used oss.sonatype.org or s01.sonatype.org to publish artifacts in some time starting with the oldest and working our way forward. To avoid disruption to your publishing processes we strongly encourage migrating before the June 30, 2025 deadline.
Thank you for your assistance,
The Central Team
Philip Durbin 🚀 (May 22 2025 at 14:31):I just created this issue: the way we publish to Maven Central (OSSRH) is reaching end of life on June 30, 2025 #11512
Philip Durbin 🚀 (May 22 2025 at 14:31):Please edit away!
Oliver Bertuch (Jun 28 2025 at 00:08):Progress.
Philip Durbin 🚀 (Jul 01 2025 at 00:15):Yeah? Great! Thank you!
Philip Durbin 🚀 (Jul 16 2025 at 14:24):One thing that's bothering me slightly is that https://github.com/gdcc/xoai/blob/2ab1ea8e263fa7d5e2a218dba6cda3b23da8e2c7/.github/workflows/maven-snapshot.yml uses 4 spaces while https://github.com/gdcc/xoai/blob/2ab1ea8e263fa7d5e2a218dba6cda3b23da8e2c7/.github/workflows/maven-release.yml uses 2 spaces.
Should we standardize? I'm updating another repo based on these files.
Philip Durbin 🚀 (Jul 16 2025 at 15:33):yamlfmt (https://github.com/google/yamlfmt) seems to prefer 2 spaces.
I don't have a preference myself and I only downloaded that tool just now.
Philip Durbin 🚀 (Jul 17 2025 at 17:32):@Oliver Bertuch sounds like you don't care about number of spaces but you do want to preserve line breaks. What if we use the retain_line_breaks_single option from yamlfmt?
"(NOTE: Takes precedence over retain_line_breaks) Retain line breaks in formatted yaml, but only keep a single line in groups of many blank lines." -- https://github.com/google/yamlfmt/blob/main/docs/config-file.md#basic-formatter
Philip Durbin 🚀 (Sep 04 2025 at 20:33):Bleh. I'm hitting some roadblocks.
@Oliver Bertuch I just created a doc of questions I have for you: https://docs.google.com/document/d/1L6-PpMAmoiL8EuRInZwt2MiWhwI23SlVXPZ-PhybgJE/edit?usp=sharing
Probably easiest to discuss over video call, when you have time!
Philip Durbin 🚀 (Sep 08 2025 at 14:54):Also, we still have this issue under the 6.8 milestone and "in progress". Please lemme know if we should bump it to 6.9 and move it to "on hold".
Last updated: Nov 01 2025 at 14:11 UTC