Skip to content
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

chore: Release v0.6.3 #1034

Merged
merged 2 commits into from
Dec 18, 2024
Merged

chore: Release v0.6.3 #1034

merged 2 commits into from
Dec 18, 2024

Conversation

tushar-composio
Copy link
Collaborator

@tushar-composio tushar-composio commented Dec 18, 2024

No description provided.

Copy link

vercel bot commented Dec 18, 2024

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name Status Preview Comments Updated (UTC)
composio ✅ Ready (Inspect) Visit Preview 💬 Add feedback Dec 18, 2024 11:15am

Copy link
Contributor

@ellipsis-dev ellipsis-dev bot left a comment

Choose a reason for hiding this comment

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

👍 Looks good to me! Reviewed everything up to 38becfc in 11 seconds

More details
  • Looked at 386 lines of code in 18 files
  • Skipped 0 files when reviewing.
  • Skipped posting 1 drafted comments based on config settings.
1. python/plugins/langgraph/setup.py:15
  • Draft comment:
    There's a typo in the description: "LnagGraph" should be "LangGraph".
  • Reason this comment was not posted:
    Confidence changes required: 50%
    The PR updates the version numbers across multiple files, which is expected for a version bump. However, there is a typo in the description of the LangGraph plugin.

Workflow ID: wflow_0MbkzN81AYvBMGaD


You can customize Ellipsis with 👍 / 👎 feedback, review rules, user-specific overrides, quiet mode, and more.

Copy link

Walkthrough

This pull request updates the Composio platform from version 0.6.2 to 0.6.3. The changes are primarily focused on updating version numbers across various setup and configuration files to ensure consistency and compatibility with the new release. Key updates include:

  • Core package version updates in __version__.py and setup.py.
  • Dockerfile adjustments to reflect the new composio-core version.
  • Multiple plugin setup files updated to align with the new version requirements for composio_core, composio_openai, and composio_langchain dependencies.

These modifications are straightforward, ensuring the system's integrity and functionality with the new version.

Changes

File(s) Summary
python/composio/__version__.py, python/setup.py Updated core package version from 0.6.2 to 0.6.3.
python/dockerfiles/Dockerfile Updated composio-core version in pip install command to 0.6.3.
python/plugins/autogen/setup.py, python/plugins/camel/setup.py, python/plugins/google/setup.py, python/plugins/griptape/setup.py, python/plugins/llamaindex/setup.py, python/plugins/lyzr/setup.py, python/plugins/openai/setup.py, python/plugins/praisonai/setup.py Updated package version and composio_core dependency to 0.6.3.
python/plugins/claude/setup.py, python/plugins/julep/setup.py, python/plugins/phidata/setup.py Updated package version and composio_openai dependency to 0.6.3.
python/plugins/crew_ai/setup.py, python/plugins/langgraph/setup.py, python/swe/setup.py Updated package version and dependencies to composio_langchain and composio_langgraph 0.6.3.

🔗 Related PRs

Instructions

Emoji Descriptions:

  • ⚠️ Potential Issue - May require further investigation.
  • 🔒 Security Vulnerability - Fix to ensure system safety.
  • 💻 Code Improvement - Suggestions to enhance code quality.
  • 🔨 Refactor Suggestion - Recommendations for restructuring code.
  • ℹ️ Others - General comments and information.

Interact with the Bot:

  • Send a message or request using the format:
    @bot + *your message*
Example: @bot Can you suggest improvements for this code?
  • Help the Bot learn by providing feedback on its responses.
    @bot + *feedback*
Example: @bot Do not comment on `save_auth` function !

Execute a command using the format:

@bot + */command*

Example: @bot /updateCommit

Available Commands:

  • /updateCommit ✨: Apply the suggested changes and commit them (or Click on the Github Action button to apply the changes !)
  • /updateGuideline 🛠️: Modify an existing guideline.
  • /addGuideline ➕: Introduce a new guideline.

Tips for Using @bot Effectively:

  • Specific Queries: For the best results, be specific with your requests.
    🔍 Example: @bot summarize the changes in this PR.
  • Focused Discussions: Tag @bot directly on specific code lines or files for detailed feedback.
    📑 Example: @bot review this line of code.
  • Managing Reviews: Use review comments for targeted discussions on code snippets, and PR comments for broader queries about the entire PR.
    💬 Example: @bot comment on the entire PR.

Need More Help?

📚 Visit our documentation for detailed guides on using Entelligence.AI.
🌐 Join our community to connect with others, request features, and share feedback.
🔔 Follow us for updates on new features and improvements.

@shreysingla11
Copy link
Collaborator

Code Review Summary

Changes Overview

  • Version bump from 0.6.2 to 0.6.3 across core package and plugins
  • SWE kit version bump from 0.3.3 to 0.3.4
  • All dependency ranges updated consistently

Issues Found

  1. Missing CHANGELOG.md update
    • The release process requires updating CHANGELOG.md with release notes
    • No changelog entry found for version 0.6.3

Recommendations

  1. Add CHANGELOG.md entry for v0.6.3 as per release process
  2. Consider using automated tools for version management to ensure consistency
  3. Document the changes and improvements in this release for user reference

Code Quality: ✅ Good

  • Version updates are consistent across all files
  • Dependencies are properly maintained with correct version ranges
  • No breaking changes or bugs introduced

Please update the PR to include the required changelog documentation before merging.

Copy link
Contributor

@ellipsis-dev ellipsis-dev bot left a comment

Choose a reason for hiding this comment

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

👍 Looks good to me! Incremental review on 895fbc4 in 13 seconds

More details
  • Looked at 283 lines of code in 16 files
  • Skipped 0 files when reviewing.
  • Skipped posting 1 drafted comments based on config settings.
1. python/scripts/bump.py:68
  • Draft comment:
    The comment suggests using a minor version bump for breaking changes, which is against semantic versioning principles. Consider using a major version bump for breaking changes once past v1.0.
  • Reason this comment was not posted:
    Confidence changes required: 50%
    The PR updates the version constraints for dependencies from "<=0.6.3" to "<0.7.0". This is a good practice as it allows for minor version updates without breaking changes. However, the comment in the bump.py script suggests that the bump type is set to minor due to breaking changes in minor releases, which is not ideal. This should be addressed in the future to follow semantic versioning properly.

Workflow ID: wflow_ohWjvwDRbwYflVDh


You can customize Ellipsis with 👍 / 👎 feedback, review rules, user-specific overrides, quiet mode, and more.

Comment on lines +75 to +82
def _bump_setups(bump_type: BumpType, latest_core_version: VersionInfo) -> None:
cwd = Path.cwd()
for setup in (
cwd / "setup.py",
cwd / "swe" / "setup.py",
*(cwd / "plugins").glob("**/setup.py"),
):
_bump_setup(file=setup, bump_type=bump_type)
_bump_setup(setup, bump_type, latest_core_version)

Choose a reason for hiding this comment

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

⚠️ Potential Issue:

Ensure Proper Usage of New Parameter in Function
The function _bump_setups has been modified to include a new parameter latest_core_version. However, the current diff does not show how this parameter is being utilized within the function. This omission can lead to logical errors if the parameter is not used correctly or if the function calls are not updated to pass this new parameter.

Actionable Steps:

  • Review Function Calls: Ensure that all calls to _bump_setups are updated to include the latest_core_version parameter.
  • Verify Parameter Usage: Check that latest_core_version is used appropriately within the function to achieve the intended functionality.
  • Testing: After making these changes, conduct thorough testing to ensure that the function behaves as expected with the new parameter.

By addressing these points, you can prevent potential runtime errors and ensure the function operates correctly. 🛠️


Comment on lines 129 to 141
content = content.replace(f'__version__ = "{version}"', f'__version__ = "{update}"')
file.write_text(content, encoding="utf-8")
print(f"Bumped {file} to {update}")
return update


def bump(bump_type: BumpType) -> None:
for _bump in (_bump_setups, _bump_dockerfiles, _bump_init):
_bump(bump_type=bump_type)
latest_core_version = _bump_init(bump_type=bump_type)
_bump_setups(bump_type=bump_type, latest_core_version=latest_core_version)
_bump_dockerfiles(bump_type=bump_type)


if __name__ == "__main__":

Choose a reason for hiding this comment

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

⚠️ Potential Issue:

Review of Version Bumping Logic Change
The recent changes in the bump function introduce a new variable latest_core_version and modify the sequence of operations for version bumping. This change could potentially lead to logical errors if latest_core_version is not correctly determined or applied across all necessary files.

Recommendations:

  • Verify Logic: Ensure that latest_core_version is accurately determined in _bump_init and that it is correctly used in _bump_setups. This will prevent any inconsistencies in version management.
  • Testing: Conduct thorough testing to ensure that the new sequence does not introduce any errors or inconsistencies. This includes unit tests and integration tests to cover all scenarios.
  • Documentation: Update any relevant documentation to reflect the changes in the version bumping process, ensuring that future developers understand the new logic.

Potential Risks:

  • If latest_core_version is not correctly applied, it could lead to mismatched versions across different files, causing deployment issues.

By addressing these points, you can ensure a smooth transition to the new version bumping logic. 🛠️


@tushar-composio tushar-composio merged commit 61e5fd4 into master Dec 18, 2024
22 of 24 checks passed
@tushar-composio tushar-composio deleted the release/v0.6.3 branch December 18, 2024 11:35
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants