Skip to content

release: 2.41.0#352

Open
stainless-app[bot] wants to merge 3 commits into
mainfrom
release-please--branches--main--changes--next
Open

release: 2.41.0#352
stainless-app[bot] wants to merge 3 commits into
mainfrom
release-please--branches--main--changes--next

Conversation

@stainless-app

@stainless-app stainless-app Bot commented Jun 11, 2026

Copy link
Copy Markdown
Contributor

Automated Release PR

2.41.0 (2026-06-11)

Full Changelog: v2.40.1...v2.41.0

Build System


This pull request is managed by Stainless's GitHub App.

The semver version number is based on included commit messages. Alternatively, you can manually set the version number in the title of this pull request.

For a better experience, it is recommended to use either rebase-merge or squash-merge when merging this pull request.

🔗 Stainless website
📚 Read the docs
🙋 Reach out for help or questions

- Enable the Gradle daemon and give the Kotlin daemon its own JVM args with
  full tiered JIT compilation (the old -XX:TieredStopAtLevel=1 crippled the
  long-lived, CPU-bound Kotlin compiler; cold compile 84s -> 62s)
- Audit the daemon JVM flags against measurements: drop no-op or unhelpful
  flags (-XX:+OptimizeStringConcat is default-on, -XX:+UseStringDeduplication
  had no measurable effect, -Xms2g/-XX:GCTimeRatio/-XX:CICompilerCount tuned
  the old no-daemon setup) and document why each kept flag earns its place
- Cap daemon heaps so the Gradle daemon, Kotlin daemon, and test workers fit
  in a 16 GB GitHub Actions runner; uncapped daemons got CI jobs killed
- Fix CI caching: setup-java's 'cache: gradle' restored ~/.gradle first, which
  made setup-gradle skip both restoring and saving its own cache (including
  the build cache), so CI recompiled everything every run
- Unify on gradle/actions/setup-gradle v4 (the test and release workflows
  used the deprecated gradle-build-action v2) and wire cache-encryption-key
  so configuration-cache data can be saved/restored on CI
- Generate the anthropic-java javadoc JAR from aggregated source sets on its
  own dokkaJavadoc task instead of the root dokkaJavadocCollector task, whose
  outputs overlap with the per-module dokka tasks' outputs, disabling build
  caching and re-documenting every module on every CI build (~17 min cold);
  warm CI publish step is now ~13s with dokka fully cached
- Raise the build job timeout to 30 minutes so the first cache-seeding run
  (full compile + full dokka) can complete; cached runs are much faster
- Make anthropic-java-proguard-test configuration-cache compatible (pass the
  shadow JAR path instead of the task to ProGuard's injars) and declare
  inputs/outputs on the ProGuard/R8 tasks so warm test runs skip ~15s of
  re-verification
- Remove forkEvery=100 from test tasks and fix the underlying flakiness: SLF4J
  prints a 'no providers' warning to stderr on first use, corrupting tests
  that assert on exact stderr contents; binding slf4j-nop on the test runtime
  classpath keeps SLF4J silent (also ~4s faster test execution)
- Raise the Gradle daemon heap to 6g: Dokka generates documentation in-process
  and a cold build OOMs the daemon at 3g (locally: 10.5 min of GC thrash, then
  OOM; at 6g the same cold publish completes in 1.5 min)
- Run the anthropic-java dokkaJavadoc task after every other module's: two
  large in-process Dokka generations running concurrently can exhaust the
  daemon heap regardless of machine size (a CI run hung for 25 minutes this
  way); serializing them costs ~6s on a cold build
- Move CI jobs to ubuntu-latest-16-core runners (16 vCPU / 64 GB vs 4 vCPU /
  16 GB), cutting the cold-cache build job to ~10 min and lint to ~1 min
@stainless-app stainless-app Bot requested a review from a team as a code owner June 11, 2026 18:33
@stainless-app

stainless-app Bot commented Jun 11, 2026

Copy link
Copy Markdown
Contributor Author

🧪 Testing

To try out this version of the SDK:

Add the following URL as a Maven source: 'https://pkg.stainless.com/s/anthropic-java/19882bbada3e1ccbd1cb4fc10b011801cd0865fa/mvn'

Expires at: Sat, 11 Jul 2026 20:57:47 GMT
Updated at: Thu, 11 Jun 2026 20:57:47 GMT

@stainless-app stainless-app Bot force-pushed the release-please--branches--main--changes--next branch from 30c6c30 to f8712fa Compare June 11, 2026 20:56
@TomerAberbach TomerAberbach changed the title release: 2.40.2 release: 2.41.0 Jun 11, 2026
@stainless-app

stainless-app Bot commented Jun 11, 2026

Copy link
Copy Markdown
Contributor Author

Release version edited manually

The Pull Request version has been manually set to 2.41.0 and will be used for the release.

If you instead want to use the version number 2.40.2 generated from conventional commits, just remove the label autorelease: custom version from this Pull Request.

@stainless-app stainless-app Bot force-pushed the release-please--branches--main--changes--next branch from f8712fa to 213d307 Compare June 11, 2026 21:06
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant