Skip to content

SDK regeneration - #267

Merged
dylburger merged 3 commits into
mainfrom
fern-bot/2026-09-03_18-10-25_116
Oct 21, 2026
Merged

dylburger merged 3 commits into
mainfrom
fern-bot/2026-09-03_18-10-25_116

Conversation

@fern-api

@fern-api fern-api Bot commented Sep 3, 2026 •

Copy link
Copy Markdown
Contributor

Automated SDK generation by Fern


Action required: 3 files with unresolved customization conflicts

The new generation changed code you previously customized. Non-conflicting customizations have been applied automatically. The following files need manual resolution:

File Your customization Why it conflicted
README.md feat: authenticate with a private key (private_key_jwt) instead of a client secret (CON-211) (#268) The new generation changed the same lines you edited
build.gradle feat: authenticate with a private key (private_key_jwt) instead of a client secret (CON-211) (#268) The new generation changed the same lines you edited
src/main/java/com/pipedream/api/core/ClientOptions.java feat: authenticate with a private key (private_key_jwt) instead of a client secret (CON-211) (#268) The new generation changed the same lines you edited

How to resolve

  1. Check out this branch:
    git fetch origin && git checkout -b fern-bot/2026-09-03_18-10-25_116 origin/fern-bot/2026-09-03_18-10-25_116
    Or if you don't have the repo cloned:
    git clone https://github.com/PipedreamHQ/pipedream-sdk-java.git && cd pipedream-sdk-java && git checkout -b fern-bot/2026-09-03_18-10-25_116 origin/fern-bot/2026-09-03_18-10-25_116
  2. Run: fern replay resolve
  3. Open the conflicting files in your editor — you'll see standard merge conflict markers
  4. Resolve using your editor's merge tools (VS Code, IntelliJ, etc.)
  5. Run: fern replay resolve again to finalize
  6. Push your changes

Your resolved customizations will be remembered on future SDK generations.
If you merge this PR without resolving, your unresolved customizations will conflict again on the next generation.

@fern-api
fern-api Bot force-pushed the fern-bot/2026-09-03_18-10-25_116 branch from 867b77c to a34a15b Compare September 11, 2026 18:25
@coderabbitai

coderabbitai Bot commented Sep 11, 2026 •

Copy link
Copy Markdown

Important

Review skipped

Bot user detected.

To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration
  • Configuration used: Organization UI
  • Review profile: ASSERTIVE
  • Plan: Advanced
  • Run ID: d1693bf7-9352-4fa4-ab6e-354f3d96be45

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

  • 🔍 Trigger review
  • Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

Comment @coderabbitai help to get the list of available commands.

@fern-api
fern-api Bot force-pushed the fern-bot/2026-09-03_18-10-25_116 branch from a34a15b to c433917 Compare September 22, 2026 23:20
@fern-api
fern-api Bot force-pushed the fern-bot/2026-09-03_18-10-25_116 branch 2 times, most recently from 866157a to 7c40ae4 Compare October 20, 2026 18:59
fern-api Bot added 2 commits October 21, 2026 00:10
Generated by Fern
CLI Version: unknown
Generators:
  - fernapi/fern-java-sdk: 4.8.4
Patches with unresolved conflicts (1):
  - patch-865b33f6: feat: authenticate with a private key (private_key_jwt) instead of a client secret (CON-211) (#268)
    Run `fern-replay resolve` to apply these customizations.
@fern-api
fern-api Bot force-pushed the fern-bot/2026-09-03_18-10-25_116 branch from 7c40ae4 to b860740 Compare October 21, 2026 00:10
This release adds methods and types (webhook delivery state reset, OAuth
app and app fields, 400 error bodies), so it's a minor version rather than
the regen's 2.2.1.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@dylburger
dylburger merged commit 91f6816 into main Oct 21, 2026
4 checks passed
@dylburger
dylburger deleted the fern-bot/2026-09-03_18-10-25_116 branch October 21, 2026 20:30
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