Skip to content

release: 2.12.0#113

Open
stainless-app[bot] wants to merge 5 commits intomasterfrom
release-please--branches--master--changes--next--components--lmnt-node
Open

release: 2.12.0#113
stainless-app[bot] wants to merge 5 commits intomasterfrom
release-please--branches--master--changes--next--components--lmnt-node

Conversation

@stainless-app
Copy link
Copy Markdown
Contributor

@stainless-app stainless-app bot commented Oct 7, 2025

Automated Release PR

2.12.0 (2026-04-01)

Full Changelog: v2.11.1...v2.12.0

Features

Chores

  • internal: remove .eslintcache (7c0a5e5)
  • internal: use npm pack for build uploads (00f524a)
  • tests: bump steady to v0.20.2 (3a9acb5)

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

@stainless-app
Copy link
Copy Markdown
Contributor Author

stainless-app bot commented Oct 7, 2025

🧪 Testing

To try out this version of the SDK, run:

npm install 'https://pkg.stainless.com/s/lmnt-com-node/00f524a1b07a146bed6af884e48e6c4dafce63ac/dist.tar.gz'

Expires: Thu, 06 Nov 2025 03:22:18 GMT

@stainless-app
Copy link
Copy Markdown
Contributor Author

stainless-app bot commented Nov 29, 2025

Note: this release PR has been open for more than 60 days. Until this PR is merged, we will temporarily stop pushing codegen updates due to changes to Stainless' codegen.

@stainless-app stainless-app bot force-pushed the release-please--branches--master--changes--next--components--lmnt-node branch from 187c138 to 4b3a325 Compare March 31, 2026 18:26
@stainless-app stainless-app bot changed the title release: 2.11.2 release: 2.12.0 Mar 31, 2026
@stainless-app stainless-app bot force-pushed the release-please--branches--master--changes--next--components--lmnt-node branch from 4b3a325 to 92a2580 Compare March 31, 2026 18:26
@stainless-app stainless-app bot force-pushed the release-please--branches--master--changes--next--components--lmnt-node branch from 92a2580 to 0860a39 Compare April 1, 2026 08:16
@stainless-app
Copy link
Copy Markdown
Contributor Author

stainless-app bot commented Apr 1, 2026

Note: this release PR has been open for more than 60 days. Until this PR is merged, we will temporarily stop pushing codegen updates due to changes to Stainless' codegen.

5 similar comments
@stainless-app
Copy link
Copy Markdown
Contributor Author

stainless-app bot commented Apr 2, 2026

Note: this release PR has been open for more than 60 days. Until this PR is merged, we will temporarily stop pushing codegen updates due to changes to Stainless' codegen.

@stainless-app
Copy link
Copy Markdown
Contributor Author

stainless-app bot commented Apr 3, 2026

Note: this release PR has been open for more than 60 days. Until this PR is merged, we will temporarily stop pushing codegen updates due to changes to Stainless' codegen.

@stainless-app
Copy link
Copy Markdown
Contributor Author

stainless-app bot commented Apr 4, 2026

Note: this release PR has been open for more than 60 days. Until this PR is merged, we will temporarily stop pushing codegen updates due to changes to Stainless' codegen.

@stainless-app
Copy link
Copy Markdown
Contributor Author

stainless-app bot commented Apr 5, 2026

Note: this release PR has been open for more than 60 days. Until this PR is merged, we will temporarily stop pushing codegen updates due to changes to Stainless' codegen.

@stainless-app
Copy link
Copy Markdown
Contributor Author

stainless-app bot commented Apr 6, 2026

Note: this release PR has been open for more than 60 days. Until this PR is merged, we will temporarily stop pushing codegen updates due to changes to Stainless' codegen.

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.

0 participants