.avif)
Fern Autorelease automatically detects updates to your API specification, regenerates SDKs, determines version bumps, and publishes new packages.
Why we built Fern Autorelease
Releasing SDKs should be predictable, not something your team has to babysit.
Before Autorelease, teams had to manually initiate generation, bump versions, merge PRs, and publish packages after every API change.
Fern Autorelease removes those steps. Through the existing Fern GitHub App, every API specification update triggers a managed release pipeline — regenerating, versioning, publishing, and updating changelogs automatically.
How it works
.avif)
Step 1: Detect API changes
Fern monitors your OpenAPI specification for updates and automatically starts the release pipeline.
Detection works in two ways:
- Git-based: Connect Fern to the repository containing your spec. Any commit that updates it automatically starts a release.
- Pull-based: Fern periodically fetches your hosted OpenAPI spec (e.g., hourly or daily) and triggers a release only when it changes
Step 2: Version automatically
Fern infers the next version based on the diff between your new and previous API specifications.
Autorelease follows your existing versioning scheme or strategy, whether semantic, calendar-based, integer, or custom. If Fern isn't confident about the version bump, it pauses and requests confirmation before releasing.
Step 3: Commit and release SDKs
Fern commits the updated SDKs to your GitHub repositories, tags the release, and publishes each package to its registry — npm, PyPI, Maven, NuGet, etc. You can also configure Fern to open a pull request for review before publishing.
Publishing uses the tokens stored in your GitHub Actions secrets. Fern never has access to these credentials.
That's it, no changes to your CI/CD setup required. After Autorelease is enabled, you just need to run fern generate to regenerate and publish your SDKs. Fern will handle the rest.
Learn more: buildwithfern.com/learn/sdks/overview/autorelease
.avif)