-
Notifications
You must be signed in to change notification settings - Fork 0
release: 2.8.0 #302
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
release: 2.8.0 #302
Conversation
|
⏳ I'm reviewing this pull request for security vulnerabilities and code quality issues. I'll provide an update when I'm done |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Important
Looks good to me! 👍
Reviewed everything up to e832731 in 39 seconds. Click for details.
- Reviewed
74lines of code in6files - Skipped
0files when reviewing. - Skipped posting
6draft comments. View those below. - Modify your settings and rules to customize what types of comments Ellipsis leaves. And don't forget to react with 👍 or 👎 to teach Ellipsis.
1. .release-please-manifest.json:1
- Draft comment:
Version bump updated to 2.8.0 in the release manifest. This is consistent with other version declarations; ensure that all generated release files align. - Reason this comment was not posted:
Confidence changes required:0%<= threshold50%None
2. CHANGELOG.md:3
- Draft comment:
Changelog entry for 2.8.0 is added with the new feature entry. Verify the release date and details align with expectations. - Reason this comment was not posted:
Confidence changes required:0%<= threshold50%None
3. package.json:3
- Draft comment:
Package version updated to 2.8.0. This ensures consistency with the release manifest and changelog. - Reason this comment was not posted:
Confidence changes required:0%<= threshold50%None
4. packages/mcp-server/package.json:2
- Draft comment:
MCP server package version updated to 2.8.0. All version references appear consistent. - Reason this comment was not posted:
Confidence changes required:0%<= threshold50%None
5. packages/mcp-server/src/server.ts:29
- Draft comment:
Updated version to 2.8.0 and enabled the logging capability by adding 'logging: {}' to the capabilities. Ensure that the logging functionality is properly supported whenever the corresponding environment variable is set. - Reason this comment was not posted:
Confidence changes required:0%<= threshold50%None
6. src/version.ts:1
- Draft comment:
Version constant updated to 2.8.0. This maintains consistency across the codebase. - Reason this comment was not posted:
Confidence changes required:0%<= threshold50%None
Workflow ID: wflow_9L8qKBDwKNhqq5xy
You can customize by changing your verbosity settings, reacting with 👍 or 👎, replying to comments, or adding code review rules.
|
🧪 Testing |
|
✅ I finished the code review, and didn't find any security or code quality issues. |
e832731 to
e98a089
Compare
d495f25 to
c0d1022
Compare
d4ec2a5 to
e9e8777
Compare
5a06c3d to
00cb972
Compare
1d5db84 to
e2fdc8b
Compare
58c77d0 to
3237c3b
Compare
ef7d1db to
dae9b0f
Compare
2d34f99 to
1120737
Compare
1120737 to
815c62d
Compare
… validation issues
815c62d to
1f600f7
Compare
1f600f7 to
24c431f
Compare
520bf1a to
021ca69
Compare
021ca69 to
5e0d023
Compare
5e0d023 to
22a232b
Compare
22a232b to
b2b80e2
Compare
b2b80e2 to
98a1b22
Compare
98a1b22 to
234d6eb
Compare
234d6eb to
6c15cbc
Compare
6c15cbc to
cc40153
Compare
cc40153 to
af54af8
Compare
af54af8 to
540992a
Compare
540992a to
8ef0c4e
Compare
8ef0c4e to
44b6844
Compare
|
Important Review skippedBot user detected. To trigger a single review, invoke the You can disable this status message by setting the Comment |
44b6844 to
465c411
Compare
465c411 to
4c250f9
Compare
Automated Release PR
2.8.0 (2025-12-02)
Full Changelog: v2.7.4...v2.8.0
Features
streamableHTTPApp(c79c312)Bug Fixes
Performance Improvements
Chores
compilerOptions.baseUrlfrom tsconfig.json (1174a7f)docs_searchtool at other URLs (29f1271)Documentation
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