Repository navigation
fix(sdk): preserve OIDC lifecycle across the Java API refresh - #5
Merged
Merged
Conversation
Adds the release half of the Fern pipeline for whopsdk-java: a four-job publish workflow that ships com.whop.api:whop-java to Maven Central through the Sonatype Central Portal, the Maven coordinate and publication metadata the Fern Java generator does not emit, and the .fernignore that keeps all of it alive across regenerations. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01XV1533iUUxKJxfn4FXptWz
Maven Central is blocked on a Sonatype namespace, a DNS TXT record on whop.com and a signing key, none of which anyone here can create. Internal consumers need a resolvable artifact now, and a jar attached to a GitHub Release is not one: build.gradle declares okhttp and three Jackson modules at `api` scope, so a bare jar in a flatDir repo resolves none of them and every consumer hand-copies four coordinates that drift on each regeneration. GitHub Packages gives real coordinates, a POM and transitive resolution for the cost of a GITHUB_TOKEN. Same publication, same POM, same com.whop.api:whop-java that Central would get — a later migration is a repository URL, not a dependency line. - RELEASE_TARGET selects the registry, a workflow_dispatch input overrides it, and every pull request forces target=both so neither path rots. - The decide job runs the same guards against whichever registries are selected; the GitHub Packages existence check reads the package versions API, which answers 404 for a package that was never published and 403 with a scope message when it cannot read, and refuses on anything else. - publish-github-packages holds packages:write and no environment. It asserts it cannot see the Central credentials, matches its POM against the one the build job verified, and reads the artifact back out of the registry afterwards. - The build job's POM check now parses build.gradle's api dependencies and asserts each reaches the POM at compile scope. - stamp-version.py is the version stamp both publish paths run.
fern-api
Bot
force-pushed
the
fern-bot/2026-08-25_02-09-15_476
branch
from
August 25, 2026 06:27
713af1e to
5163b2f
Compare
Preserve the release workflow assets and current OIDC helper/test protections in .fernignore. Verified 52 tests, full build, Spotless, actionlint, local bundle contents, and the registry task graph without uploading.
Generated by Fern CLI Version: unknown Generators: - fernapi/fern-java-sdk: 4.37.6
fern-api
Bot
force-pushed
the
fern-bot/2026-08-25_02-09-15_476
branch
from
November 13, 2026 19:42
5163b2f to
42f5603
Compare
antonwhop
marked this pull request as draft
November 13, 2026 20:33
antonwhop
marked this pull request as ready for review
November 13, 2026 20:46
antonwhop
marked this pull request as draft
November 13, 2026 20:52
This branch was successfully deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Why / Prompt
What changed?
Release and integration notes