chore: Release v0.6.11.post1

[tushar-composio]

🔍 Review Summary

Updated version numbers in setup.py and Dockerfile to 0.6.11.post1 across the project.

Original Description

[!IMPORTANT]
Update composio package and plugins to version 0.6.11.post1 and adjust dependencies accordingly.

• Version Update:
  • Update __version__ in __version__.py to 0.6.11.post1.
  • Update version in setup.py for composio_core, swekit, and all plugins to 0.6.11.post1.
  • Update Dockerfile to install composio-core[all]==0.6.11.post1.
• Dependencies:
  • Update composio_core dependency in plugins' setup.py to >=0.6.11,<0.7.0.

^{This description was created by for 4cc8629. It will automatically update as commits are pushed.}

[vercel]

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	Jan 3, 2025 9:14am

[ellipsis-dev]

👍 Looks good to me! Reviewed everything up to 4cc8629 in 16 seconds

More details

• Looked at 341 lines of code in 18 files
• Skipped 0 files when reviewing.
• Skipped posting 1 drafted comments based on config settings.

1. python/plugins/crew_ai/setup.py:12

• Draft comment:
  The version constraint for composio_langchain should be updated to >=0.6.11,<0.7.0 to maintain consistency with other plugins.
• Reason this comment was not posted:
  Comment did not seem useful.

Workflow ID: wflow_1KvdbssHlKYAXhOz

---

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

[entelligence-ai-pr-reviews]

Walkthrough

Version updates across multiple setup.py files and Dockerfile to 0.6.11.post1.

🔗 Related PRs

• feat: update types with BE and release rc for v0.5 #1082: Refactor backend types and update API methods to comply with new specifications, including function renaming and model updates.
• fix: bring eslint + TS issues to zero #1013: The pull request aims to enhance code quality and type safety by enforcing stricter ESLint rules, refactoring code to replace any types, and improving error handling for better maintainability and robustness.
• feat: decrease bundle size, eslint and ts issues to zero  #1032: The update optimizes the Composio JS SDK by automating version updates, reducing bundle size by disabling source maps, and enhancing documentation for future tasks.
• ci: run every 12 hours, and tag me on failure #1041: The pull request introduces automated testing via scheduled GitHub Actions and enhances Slack notifications for test failures, improving CI/CD pipeline reliability and communication.

Entelligence.ai can learn from your feedback. Simply add 👍 / 👎 emojis to teach it your preferences. More shortcuts below

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 !

[shreysingla11]

I've reviewed the changes in this PR. Here's my assessment:

This is a version bump PR that updates version numbers across multiple files from v0.6.11 to v0.6.11.post1. The changes are consistent and follow semantic versioning practices.

Key changes:

1. Core package version updated to 0.6.11.post1
2. All plugin packages version updated to match core
3. Dependency constraints updated to require composio_core>=0.6.11
4. Dockerfile updated to use new version
5. Swekit package version updated from 0.3.12 to 0.3.12.post1

Suggestions for improvement:

1. Consider adding a CHANGELOG.md entry to document what necessitated this post-release
2. Consider using a tool like bump2version to automate version bumps across files
3. Consider adding a GitHub Action to verify version consistency across all files

Overall, the changes look correct and maintain consistency across the codebase. This appears to be a standard post-release version bump to address a minor issue found after the 0.6.11 release.