Skip to content

release: 0.1.0#2

Closed
stainless-app[bot] wants to merge 3 commits intomainfrom
release-please--branches--main--changes--next--components--morphik
Closed

release: 0.1.0#2
stainless-app[bot] wants to merge 3 commits intomainfrom
release-please--branches--main--changes--next--components--morphik

Conversation

@stainless-app
Copy link
Copy Markdown
Contributor

@stainless-app stainless-app bot commented Jul 17, 2025 •
edited
Loading

Automated Release PR

0.1.0 (2025-07-17)

Full Changelog: v0.0.1...v0.1.0

Features

  • api: update via SDK Studio (c78d82e)

Chores

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

@jazzberry-ai
Copy link
Copy Markdown

jazzberry-ai bot commented Jul 17, 2025 •
edited
Loading

Bug Report

Name Severity Example test case Description
Incomplete release environment checks High Run the bin/check-release-environment script. The bin/check-release-environment script does not perform any checks and always returns a success status, even if the environment is not properly configured for releases.

Comments? Email us.

@stainless-app stainless-app bot force-pushed the release-please--branches--main--changes--next--components--morphik branch from 6b90905 to c78d82e Compare July 17, 2025 01:12
@jazzberry-ai
Copy link
Copy Markdown

jazzberry-ai bot commented Jul 17, 2025 •
edited
Loading

Bug Report

Name Severity Example test case Description
Inactive Release Doctor Critical Run the release doctor workflow. The check-release-environment script does not perform any checks, so the release doctor workflow is effectively disabled.
Missing NPM Publishing Critical Create a new release. The CI workflow does not include steps for publishing the package to npm, so new releases will not be automatically published.

Comments? Email us.

@stainless-app stainless-app bot changed the title release: 0.0.1-alpha.1 release: 0.1.0 Jul 17, 2025
@jazzberry-ai
Copy link
Copy Markdown

jazzberry-ai bot commented Jul 17, 2025 •
edited
Loading

Bug Report

Name Severity Example test case Description
check-release-environment always succeeds Medium Run the script. It will always exit with code 0. The check-release-environment script initializes an empty errors array and never adds any errors to it. Consequently, the script always reports that the environment is ready for release, even if there are issues.
release-please bumps minor version on pre-release Low Create a release PR when the current version is 0.0.1. It will bump the version to 0.1.0-alpha.0 The versioning is set to "prerelease" and prerelease is set to true. Also, "bump-minor-pre-major": true and "bump-patch-for-minor-pre-major": false. This configuration means that the release-please will bump the minor version when creating a pre-release, but it won't bump the patch version if the major version has not been released yet.
npm publish is disabled Low Run npm publish. The command will exit with code 1 and an error message. The scripts/publish-npm.sh script was replaced by a message that prevents publishing via npm publish. Publishing should now be done via yarn build && (cd dist; yarn publish).

Comments? Email us.

@stainless-app
Copy link
Copy Markdown
Contributor Author

stainless-app bot commented Jul 17, 2025 •
edited
Loading

🧪 Testing

To try out this version of the SDK, run:

npm install 'https://pkg.stainless.com/s/morphik-typescript/c78d82e75024b26adcc311693f8b49ef4ef9f2dc/dist.tar.gz'

Expires: Sat, 16 Aug 2025 01:13:25 GMT

@stainless-app stainless-app bot force-pushed the release-please--branches--main--changes--next--components--morphik branch from c0ea29b to c78d82e Compare July 17, 2025 01:12
@jazzberry-ai
Copy link
Copy Markdown

jazzberry-ai bot commented Jul 17, 2025 •
edited
Loading

Bug Report

Name Severity Example test case Description
Ineffective Release Environment Check High Run bin/check-release-environment without setting any environment variables. The bin/check-release-environment script does not perform any checks to ensure the release environment is properly configured. This can lead to releases being triggered even if required environment variables or dependencies are missing.

Comments? Email us.

@jazzberry-ai
Copy link
Copy Markdown

jazzberry-ai bot commented Jul 17, 2025 •
edited
Loading

Bug Report

Name Severity Example test case Description
Release Doctor Workflow Ineffective Critical Run the release doctor workflow. The check-release-environment script is a no-op, so the workflow always passes, even if the release environment is misconfigured.

Comments? Email us.

@stainless-app stainless-app bot closed this Jul 17, 2025
@stainless-app stainless-app bot deleted the release-please--branches--main--changes--next--components--morphik branch July 17, 2025 01:22
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

No reviews

Assignees

No one assigned

Labels

autorelease: pending

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

0 participants