Skip to content

release: 0.3.1#12

Open
stainless-app[bot] wants to merge 2 commits intomainfrom
release-please--branches--main--changes--next--components--hypeman
Open

release: 0.3.1#12
stainless-app[bot] wants to merge 2 commits intomainfrom
release-please--branches--main--changes--next--components--hypeman

Conversation

@stainless-app
Copy link
Copy Markdown
Contributor

@stainless-app stainless-app bot commented Apr 9, 2026

Automated Release PR

0.3.1 (2026-04-09)

Full Changelog: v0.3.0...v0.3.1

Chores

  • internal: codegen related update (335e04d)

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


Note

Low Risk
Low risk: primarily a version bump and changelog update, with a small tweak to readEnv that only affects handling of empty/whitespace-only env var values.

Overview
Bumps the library version to 0.3.1 across release metadata (package.json, lockfile, manifest, src/version.ts) and adds the 0.3.1 changelog entry.

Adjusts readEnv to return undefined when an env var resolves to an empty string after trimming (for both Node process.env and Deno Deno.env.get).

Reviewed by Cursor Bugbot for commit b6b4010. Bugbot is set up for automated code reviews on this repo. Configure here.

@stainless-app
Copy link
Copy Markdown
Contributor Author

stainless-app bot commented Apr 9, 2026

🧪 Testing

To try out this version of the SDK:

npm install 'https://pkg.stainless.com/s/hypeman-typescript/335e04dd5938e5b26b47a8f55bf7311661a0d9a5/dist.tar.gz'

Expires at: Sat, 09 May 2026 10:21:36 GMT
Updated at: Thu, 09 Apr 2026 10:21:36 GMT

Copy link
Copy Markdown

@cursor cursor bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Cursor Bugbot has reviewed your changes and found 1 potential issue.

Fix All in Cursor

❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.

Reviewed by Cursor Bugbot for commit b6b4010. Configure here.

export const readEnv = (env: string): string | undefined => {
if (typeof (globalThis as any).process !== 'undefined') {
return (globalThis as any).process.env?.[env]?.trim() ?? undefined;
return (globalThis as any).process.env?.[env]?.trim() || undefined;
Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Nullish coalescing replaced with logical OR changes semantics

Low Severity

Changing ?? to || causes readEnv to return undefined for environment variables that are set to an empty string or whitespace, since empty string is falsy. The function's docstring says it returns undefined only when the variable "doesn't exist or cannot be accessed," but an empty-string env var does exist and is accessible — so || makes the function contradict its own documented contract. While the downstream effect on apiKey validation may be benign, any caller relying on distinguishing "set to empty" from "not set" will silently get incorrect results.

Additional Locations (1)
Fix in Cursor Fix in Web

Reviewed by Cursor Bugbot for commit b6b4010. Configure here.

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