Skip to content

fix(sdk): preserve OIDC lifecycle across the Java API refresh - #5

Merged
antonwhop merged 11 commits into
mainfrom
fern-bot/2026-08-25_02-09-15_476
Nov 14, 2026
Merged

antonwhop merged 11 commits into
mainfrom
fern-bot/2026-08-25_02-09-15_476

Conversation

@fern-api

@fern-api fern-api Bot commented Aug 25, 2026 •

Copy link
Copy Markdown
Contributor

Why / Prompt

  • Refresh the Java API client without regressing existing OIDC authentication or leaving the generated tree disconnected from its release pipeline.

What changed?

  • Regenerate the current public API and preserve Tristan’s OIDC behavior, including ownership-aware async client closure.
  • Reconcile the existing release pipeline, retaining Maven coordinates, compiler memory settings, helper protections and migration guidance.
  • Verify the installed Maven artifact, including transitive dependencies, sync/async sandbox routing, API/SDK version headers, numbered funnel query parameters and OIDC entrypoints.
  • Keep pull-request release rehearsals read-only and restrict package writes and tagging to intentional main releases. The placeholder version cannot publish or tag.
  • Validation: compile and 60 persisted tests pass locally and in CI on the refreshed source. The packaged-consumer check and release dry run passed; the final guard/consumer followup also passed CI. Keep this PR draft; nothing has been published.
Release and integration notes
  • This branch includes the existing release-pipeline ci: release pipeline for the Java SDK, publishing to GitHub Packages now and Maven Central later #2 history; do not merge its older workflow over the reconciled version here.
  • Java remains outside the shared release train. After this source/pipeline change merges, an approved version-only change in gradle.properties is the publication signal. The current 0.0.0 placeholder is deliberately blocked.
  • GitHub Packages is the initial target and requires package-read authentication for consumers. Maven Central additionally requires namespace and main-only credential setup.
  • The older builder .url(...) API becomes environment(Environment.custom().api(...).vault(...).build()); MIGRATING.md covers both clients and custom OIDC exchange hosts.
  • Pending webhook feat(helpers): verify webhook signatures without a Standard Webhooks library #4 still needs its .fernignore additions reconciled; preserve its helper/test protections. Its generated-source integration was not silently included in this refresh.

antonwhop and others added 2 commits August 22, 2026 14:11
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
fern-api Bot force-pushed the fern-bot/2026-08-25_02-09-15_476 branch from 713af1e to 5163b2f Compare August 25, 2026 06:27
antonwhop and others added 3 commits November 2, 2026 08:26
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
fern-api Bot force-pushed the fern-bot/2026-08-25_02-09-15_476 branch from 5163b2f to 42f5603 Compare November 13, 2026 19:42
@antonwhop antonwhop changed the title SDK regeneration chore(sdk): refresh Java API sources and the version pin Nov 13, 2026
@antonwhop
antonwhop marked this pull request as draft November 13, 2026 20:33
@antonwhop
antonwhop marked this pull request as ready for review November 13, 2026 20:46
@antonwhop
antonwhop marked this pull request as draft November 13, 2026 20:52
@antonwhop antonwhop changed the title chore(sdk): refresh Java API sources and the version pin fix(sdk): preserve OIDC lifecycle across the Java API refresh Nov 13, 2026
@antonwhop
antonwhop marked this pull request as ready for review November 14, 2026 20:59
@antonwhop
antonwhop merged commit 5cbce2a into main Nov 14, 2026
7 checks passed

This branch was successfully deployed

1 active deployment
dry-run — e58ef38f Deployed Nov 14, 2026 by antonwhop via publish #8
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant