You can now upload GitHub release assets when an SDK is published:

targets:
  # Or any other target
  typescript:
    publish:
      release_assets:
        github:
          - ./path/to/what/you/want/to/upload
            # Or this
          - name: Display Name
            path: ./path/to/what/you/want/to/upload
          # As many as you want...

This is useful for uploading bundled or compiled artifacts or additional documentation files to your GitHub release.

You can now omit all X-Stainless-* headers from generated SDKs by adding the omit_stainless_headers to your Stainless config:

client_settings:
  omit_stainless_headers: true

This is particularly useful if your API has a headers allowlist that rejects requests containing unknown headers.

Generated CLI tools now support endpoints for downloading files using raw file data. The output destination can be specified with --output / -o flags, or if unspecified, a smart filename will be chosen to avoid overwriting local files. Files can also be sent through pipes or IO redirection.

When a Java SDK build completes successfully, Stainless will generate a hosted Maven repo that can be shared for early testing, before the SDK is formally released.

The details on how to use this repo are visible when clicking on the info icon in the “Build” row in the build status panel in the studio. We also generate a custom doc page in the repo root, which is viewable by clicking on the “Learn more” link in the popup.

A similar feature has been available for Python and Typescript builds for a while; with this change, sharing and testing pre-release Java builds is just as easy.