Quick update: I was able to restore the ability to publish 2.18 components, including snapshots, by creating a user token for Sonatype OSSRH repository and using that for authentication.
But interestingly enough this did NOT resolve the issue with 3.0 (master). I will need to work with Sonatype support to get that done too, but right now 2.18 is still more important to have working so that's good. -+ Tatu +- On Sat, Jun 15, 2024 at 9:51 AM Tatu Saloranta <[email protected]> wrote: > > Quick note: our automated CI releases -SNAPSHOT versions from pushes > to all 2.x branches and master (3.0.0). But it looks like something > broke yesterday -- I suspect it is due to Sonatype's deprecation of > the old token system, and I need to see what/how to upgrade. > > In the meantime, SNAPSHOT versions available may be slightly outdated > until I fix the issue. > > -+ Tatu +- > > ps. In better news, we now have dual-dependent build system: pushes to > 2.18 AND master of jackson-core and jackson-databind now trigger > cascading rebuilds (see > https://medium.com/@cowtowncoder/cascading-dependency-rebuilds-for-jackson-ci-5113d0b71631) > -- originally only 2.18 (default branch) was supported, but I added > secondary workflow for master so we ensure 3.0.0 branch also builds. > (obviously these are also affected by publishing problem, but once > that is resolved we should have much better visibility into breaking > changes across components) -- You received this message because you are subscribed to the Google Groups "jackson-dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/jackson-dev/CAL4a10g48p2%3DVO9LNAp0Qmxpgpi69u2jH5bXR2N03V-g4Uegvw%40mail.gmail.com.
