Skip to content

release: 2.3.2#249

Merged
sarahcstringer merged 2 commits intomainfrom
release-please--branches--main--changes--next
Oct 3, 2025
Merged

release: 2.3.2#249
sarahcstringer merged 2 commits intomainfrom
release-please--branches--main--changes--next

Conversation

@stainless-app
Copy link
Copy Markdown
Contributor

@stainless-app stainless-app Bot commented Oct 3, 2025

Automated Release PR

2.3.2 (2025-10-03)

Full Changelog: v2.3.2-rc2...v2.3.2


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

@sarahcstringer sarahcstringer changed the title release: 2.3.2-rc3 release: 2.3.2 Oct 3, 2025
@stainless-app
Copy link
Copy Markdown
Contributor Author

stainless-app Bot commented Oct 3, 2025

Release version edited manually

The Pull Request version has been manually set to 2.3.2 and will be used for the release.

If you instead want to use the version number 2.3.2-rc3 generated from conventional commits, just remove the label autorelease: custom version from this Pull Request.

@stainless-app stainless-app Bot force-pushed the release-please--branches--main--changes--next branch from 3acc5aa to 7a761e2 Compare October 3, 2025 20:12
Copy link
Copy Markdown

@hackerone-code hackerone-code Bot left a comment

Choose a reason for hiding this comment

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

HackerOne Code Security Review

🟢 Scan Complete: 2 Issue(s)
🟢 Validation Complete: Any Issues detected were validated by one of our engineers. None were determined to require immediate action.

Here's how the code changes were interpreted and info about the tools used for scanning.

📖 Summary of Changes The project has been updated from version 2.3.2-rc2 to 2.3.2, marking the final release. Changes include removing the release candidate suffix across multiple configuration files, updating installation instructions in the README, and making minor adjustments to the API, type handling, and documentation.
File Summary
.release-please-manifest.json The version number changed from "2.3.2-rc2" to "2.3.2", removing the release candidate (rc) suffix.
CHANGELOG.md The changelog shows the release of version 2.3.2, which includes minor updates to the API, internal type handling, and documentation. The changes primarily involve updating dependencies, adjusting type definitions, and making small improvements to the codebase.
README.md The primary change is in the installation instructions, where pip install --pre writer-sdk has been replaced with pip install writer-sdk, removing the --pre flag for package installation.
pyproject.toml The version number changed from "2.3.2-rc2" to "2.3.2", removing the release candidate (-rc2) suffix, indicating a final release version.
src/writerai/_version.py The version number changed from "2.3.2-rc2" to "2.3.2", removing the release candidate (-rc2) suffix.
ℹ️ Issues Detected

NOTE: These may not require action!

Below are unvalidated results from the Analysis Tools that ran during the latest scan for transparency. We investigate each of these for accuracy and relevance before surfacing them as a potential problem.

How will I know if something is a problem?
When validation completes, any concerns that warrant attention prior to merge will be posted as inline comments. These will show up in 2 ways:

  • Expert review (most cases): Issues will be posted by experts who manually reviewed and validated them. These are real HackerOne engineers (not bots) reviewing through an integrated IDE-like tool. You can communicate with them like any other reviewer. They'll stay assigned and get notified with commit & comment updates.
  • Automatically: In cases where our validation checks have highest confidence the problem is legitimate and urgent. These will include a description of contextual reasoning why & actionable next steps.
File & Line Issue
README.md Line 22 The change removes the --pre flag from pip install commands, which means users will now install the stable version instead of pre-release versions. This is not a security vulnerability but actually a security improvement, as pre-release versions may contain untested code or security issues.
CHANGELOG.md Line 3 This is a changelog file that documents version history and changes. It doesn't contain code that could introduce security vulnerabilities.
🧰 Analysis tools - [ ✅ ] [HackerOne AI Code Analysis](https://www.pullrequest.com/blog/harnessing-ai-to-pinpoint-security-hotspots-in-code-review-a-deep-dive/) - [ ✅ ] [HackerOne AI Code Validation](https://www.hackerone.com/blog/ai-triage-code-validation-security) - [ ✅ ] [semgrep](https://semgrep.dev?&utm_source=hackerone&utm_campaign=pullrequest) - [ ✅ ] rubocop - [ ✅ ] bandit

⏱️ Latest scan covered changes up to commit 7a761e2 (latest)

@sarahcstringer sarahcstringer merged commit 6e949c8 into main Oct 3, 2025
11 checks passed
@stainless-app
Copy link
Copy Markdown
Contributor Author

stainless-app Bot commented Oct 3, 2025

🤖 Release is at https://github.com/writer/writer-python/releases/tag/v2.3.2 🌻

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.

1 participant