You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Due to the OSSRH turndown, I migrated my project to the Central Repository. Publishing is done with ./gradlew publishToSonatype closeSonatypeStagingRepository. This is a Kotlin multiplatform project, which means publishing separate artifacts for each targeted platform; this is achieved by using a macOS host which supports cross-compilation on all supported platforms.
On my first attempt to publish a release, only one of the platforms was visible in the staging repository, despite the build logs indicating that all were built and published normally. When I contacted support, they indicated that the requests came from two IP addresses, which is unsupported, despite the fact that they all came from one GitHub action runner. My only guess is that separate network requests from the same runner can come from different IPs?
I'm not sure there's much that can be done about this - is it somehow possible to batch all of the artifact uploading into one API call? - but if nothing else, it seems worth investigating/documenting in the project README, since this is advertised as a supported drop-in replacement. The failure mode is subtle - the closed repository will be missing artifacts that would need to be spotted by human inspection, and projects that are configured to automatically publish would publish incomplete versions (unless that flow doesn't actually work with the staging API).
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
-
Due to the OSSRH turndown, I migrated my project to the Central Repository. Publishing is done with
./gradlew publishToSonatype closeSonatypeStagingRepository. This is a Kotlin multiplatform project, which means publishing separate artifacts for each targeted platform; this is achieved by using a macOS host which supports cross-compilation on all supported platforms.On my first attempt to publish a release, only one of the platforms was visible in the staging repository, despite the build logs indicating that all were built and published normally. When I contacted support, they indicated that the requests came from two IP addresses, which is unsupported, despite the fact that they all came from one GitHub action runner. My only guess is that separate network requests from the same runner can come from different IPs?
I'm not sure there's much that can be done about this - is it somehow possible to batch all of the artifact uploading into one API call? - but if nothing else, it seems worth investigating/documenting in the project README, since this is advertised as a supported drop-in replacement. The failure mode is subtle - the closed repository will be missing artifacts that would need to be spotted by human inspection, and projects that are configured to automatically publish would publish incomplete versions (unless that flow doesn't actually work with the staging API).
Beta Was this translation helpful? Give feedback.
All reactions