chore: update SDK settings

Author: stainless-app[bot]

.github/workflows/publish-npm.yml

@@ -0,0 +1,32 @@
+# This workflow is triggered when a GitHub release is created.
+# It can also be run manually to re-publish to NPM in case it failed for some reason.
+# You can run this workflow by navigating to https://www.github.com/uselemma/sdk-typescript/actions/workflows/publish-npm.yml
+name: Publish NPM
+on:
+  workflow_dispatch:
+
+  release:
+    types: [published]
+
+jobs:
+  publish:
+    name: publish
+    runs-on: ubuntu-latest
+
+    steps:
+      - uses: actions/checkout@v4
+
+      - name: Set up Node
+        uses: actions/setup-node@v3
+        with:
+          node-version: '20'
+
+      - name: Install dependencies
+        run: |
+          yarn install
+
+      - name: Publish to NPM
+        run: |
+          bash ./bin/publish-npm
+        env:
+          NPM_TOKEN: ${{ secrets.LEMMA_NPM_TOKEN || secrets.NPM_TOKEN }}

.github/workflows/release-doctor.yml

@@ -18,4 +18,5 @@ jobs:
         run: |
           bash ./bin/check-release-environment
         env:
+          NPM_TOKEN: ${{ secrets.LEMMA_NPM_TOKEN || secrets.NPM_TOKEN }}
 

.stats.yml

@@ -1,4 +1,4 @@
 configured_endpoints: 49
 openapi_spec_url: https://storage.googleapis.com/stainless-sdk-openapi-specs/lemma%2Flemma-dc1b1744bf9a13daa82065ecf5dc75e3870d611ab3fabf2b0f91a7b36815b2a4.yml
 openapi_spec_hash: ae1eb47bf32f7b2c225338a245298e02
-config_hash: 007eb8f554a4ea9f6c7d98488fb3a849
+config_hash: 4a6c48034b76c35207964d66524a0a15

CONTRIBUTING.md

@@ -55,12 +55,12 @@ $ cd sdk-typescript
 # With yarn
 $ yarn link
 $ cd ../my-package
-$ yarn link lemma
+$ yarn link lemma-node
 
 # With pnpm
 $ pnpm link --global
 $ cd ../my-package
-$ pnpm link -—global lemma
+$ pnpm link -—global lemma-node
 ```
 
 ## Running tests
@@ -91,3 +91,17 @@ To format and fix all lint issues automatically:
 ```sh
 $ yarn fix
 ```
+
+## Publishing and releases
+
+Changes made to this repository via the automated release PR pipeline should publish to npm automatically. If
+the changes aren't made through the automated pipeline, you may want to make releases manually.
+
+### Publish with a GitHub workflow
+
+You can release to package managers by using [the `Publish NPM` GitHub action](https://www.github.com/uselemma/sdk-typescript/actions/workflows/publish-npm.yml). This requires a setup organization or repository secret to be set up.
+
+### Publish manually
+
+If you need to manually release a package, you can run the `bin/publish-npm` script with an `NPM_TOKEN` set on
+the environment.

README.md

@@ -1,6 +1,6 @@
 # Lemma TypeScript API Library
 
-[![NPM version](<https://img.shields.io/npm/v/lemma.svg?label=npm%20(stable)>)](https://npmjs.org/package/lemma) ![npm bundle size](https://img.shields.io/bundlephobia/minzip/lemma)
+[![NPM version](<https://img.shields.io/npm/v/lemma-node.svg?label=npm%20(stable)>)](https://npmjs.org/package/lemma-node) ![npm bundle size](https://img.shields.io/bundlephobia/minzip/lemma-node)
 
 This library provides convenient access to the Lemma REST API from server-side TypeScript or JavaScript.
 
@@ -11,19 +11,16 @@ It is generated with [Stainless](https://www.stainless.com/).
 ## Installation
 
 ```sh
-npm install git+ssh://git@github.com:uselemma/sdk-typescript.git
+npm install lemma-node
 ```
 
-> [!NOTE]
-> Once this package is [published to npm](https://www.stainless.com/docs/guides/publish), this will become: `npm install lemma`
-
 ## Usage
 
 The full API of this library can be found in [api.md](api.md).
 
 <!-- prettier-ignore -->
 ```js
-import Lemma from 'lemma';
+import Lemma from 'lemma-node';
 
 const client = new Lemma({
   bearerToken: process.env['LEMMA_BEARER_TOKEN'], // This is the default and can be omitted
@@ -40,7 +37,7 @@ This library includes TypeScript definitions for all request params and response
 
 <!-- prettier-ignore -->
 ```ts
-import Lemma from 'lemma';
+import Lemma from 'lemma-node';
 
 const client = new Lemma({
   bearerToken: process.env['LEMMA_BEARER_TOKEN'], // This is the default and can be omitted
@@ -63,7 +60,7 @@ Request parameters that correspond to file uploads can be passed in many differe
 
 ```ts
 import fs from 'fs';
-import Lemma, { toFile } from 'lemma';
+import Lemma, { toFile } from 'lemma-node';
 
 const client = new Lemma();
 
@@ -192,7 +189,7 @@ The log level can be configured in two ways:
 2. Using the `logLevel` client option (overrides the environment variable if set)
 
 ```ts
-import Lemma from 'lemma';
+import Lemma from 'lemma-node';
 
 const client = new Lemma({
   logLevel: 'debug', // Show all log messages
@@ -220,7 +217,7 @@ When providing a custom logger, the `logLevel` option still controls which messa
 below the configured level will not be sent to your logger.
 
 ```ts
-import Lemma from 'lemma';
+import Lemma from 'lemma-node';
 import pino from 'pino';
 
 const logger = pino();
@@ -289,7 +286,7 @@ globalThis.fetch = fetch;
 Or pass it to the client:
 
 ```ts
-import Lemma from 'lemma';
+import Lemma from 'lemma-node';
 import fetch from 'my-fetch';
 
 const client = new Lemma({ fetch });
@@ -300,7 +297,7 @@ const client = new Lemma({ fetch });
 If you want to set custom `fetch` options without overriding the `fetch` function, you can provide a `fetchOptions` object when instantiating the client or making a request. (Request-specific options override client options.)
 
 ```ts
-import Lemma from 'lemma';
+import Lemma from 'lemma-node';
 
 const client = new Lemma({
   fetchOptions: {
@@ -317,7 +314,7 @@ options to requests:
 <img src="https://raw.githubusercontent.com/stainless-api/sdk-assets/refs/heads/main/node.svg" align="top" width="18" height="21"> **Node** <sup>[[docs](https://github.com/nodejs/undici/blob/main/docs/docs/api/ProxyAgent.md#example---proxyagent-with-fetch)]</sup>
 
 ```ts
-import Lemma from 'lemma';
+import Lemma from 'lemma-node';
 import * as undici from 'undici';
 
 const proxyAgent = new undici.ProxyAgent('http://localhost:8888');
@@ -331,7 +328,7 @@ const client = new Lemma({
 <img src="https://raw.githubusercontent.com/stainless-api/sdk-assets/refs/heads/main/bun.svg" align="top" width="18" height="21"> **Bun** <sup>[[docs](https://bun.sh/guides/http/proxy)]</sup>
 
 ```ts
-import Lemma from 'lemma';
+import Lemma from 'lemma-node';
 
 const client = new Lemma({
   fetchOptions: {
@@ -343,7 +340,7 @@ const client = new Lemma({
 <img src="https://raw.githubusercontent.com/stainless-api/sdk-assets/refs/heads/main/deno.svg" align="top" width="18" height="21"> **Deno** <sup>[[docs](https://docs.deno.com/api/deno/~/Deno.createHttpClient)]</sup>
 
 ```ts
-import Lemma from 'npm:lemma';
+import Lemma from 'npm:lemma-node';
 
 const httpClient = Deno.createHttpClient({ proxy: { url: 'http://localhost:8888' } });
 const client = new Lemma({

bin/check-release-environment

@@ -2,6 +2,10 @@
 
 errors=()
 
+if [ -z "${NPM_TOKEN}" ]; then
+  errors+=("The NPM_TOKEN secret has not been set. Please set it in either this repository's secrets or your organization secrets")
+fi
+
 lenErrors=${#errors[@]}
 
 if [[ lenErrors -gt 0 ]]; then

eslint.config.mjs

@@ -25,7 +25,7 @@ export default tseslint.config(
         {
           patterns: [
             {
-              regex: '^lemma(/.*)?',
+              regex: '^lemma-node(/.*)?',
               message: 'Use a relative import, not a package import.',
             },
           ],

jest.config.ts

@@ -7,8 +7,8 @@ const config: JestConfigWithTsJest = {
     '^.+\\.(t|j)sx?$': ['@swc/jest', { sourceMaps: 'inline' }],
   },
   moduleNameMapper: {
-    '^lemma$': '<rootDir>/src/index.ts',
-    '^lemma/(.*)$': '<rootDir>/src/$1',
+    '^lemma-node$': '<rootDir>/src/index.ts',
+    '^lemma-node/(.*)$': '<rootDir>/src/$1',
   },
   modulePathIgnorePatterns: [
     '<rootDir>/ecosystem-tests/',

package.json

@@ -1,5 +1,5 @@
 {
-  "name": "lemma",
+  "name": "lemma-node",
   "version": "0.0.1",
   "description": "The official TypeScript library for the Lemma API",
   "author": "Lemma <>",

scripts/build

@@ -8,7 +8,7 @@ node scripts/utils/check-version.cjs
 
 # Build into dist and will publish the package from there,
 # so that src/resources/foo.ts becomes <package root>/resources/foo.js
-# This way importing from `"lemma/resources/foo"` works
+# This way importing from `"lemma-node/resources/foo"` works
 # even with `"moduleResolution": "node"`
 
 rm -rf dist; mkdir dist
@@ -42,8 +42,8 @@ node scripts/utils/postprocess-files.cjs
 
 # make sure that nothing crashes when we require the output CJS or
 # import the output ESM
-(cd dist && node -e 'require("lemma")')
-(cd dist && node -e 'import("lemma")' --input-type=module)
+(cd dist && node -e 'require("lemma-node")')
+(cd dist && node -e 'import("lemma-node")' --input-type=module)
 
 if [ -e ./scripts/build-deno ]
 then