Add claude-3-5-sonnet-20241022 to anthropic models

[kieronlawson]

WHY

Adding latest claude 3.5 sonnet model (October 2024) to anthropic component.

Summary by CodeRabbit

• New Features
  • Introduced a new message model, "claude-3-5-sonnet-20241022," enhancing the options available for users.
• Updates
  • Updated the Chat API component version to "0.0.9" for improved performance.
  • Updated the package version to "0.0.11" for the @pipedream/anthropic package.

[vercel]

@kieronlawson is attempting to deploy a commit to the Pipedreamers Team on Vercel.

A member of the Team first needs to authorize it.

[vercel]

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

1 Skipped Deployment

Name	Status	Preview	Comments	Updated (UTC)
pipedream-docs-redirect-do-not-edit	⬜️ Ignored (Inspect)			Oct 31, 2024 0:12am

[coderabbitai]

Walkthrough

A new entry, "claude-3-5-sonnet-20241022", has been added to the MESSAGE_MODELS array in the module located at components/anthropic/actions/common/constants.mjs. This update expands the available message models, incorporating the latest version into the existing list. Additionally, the version numbers for the Chat API component and the package have been updated to "0.0.9" and "0.0.11" respectively.

Changes

File Path	Change Summary
components/anthropic/actions/common/constants.mjs	Added "claude-3-5-sonnet-20241022" to MESSAGE_MODELS array
components/anthropic/actions/chat/chat.mjs	Updated version from "0.0.8" to "0.0.9"
components/anthropic/package.json	Updated version from "0.0.10" to "0.0.11"

Possibly related PRs

• [ACTION] [COHERE] Chat #12624: The changes in this PR involve the introduction of a new chat action for the Cohere platform, which may relate to the overall chat functionality but does not directly connect to the specific update of the MESSAGE_MODELS array in the main PR.
• OpenAI - Add audio functionality to Chat action #14367: This PR adds audio functionality to the Chat action, which is a different enhancement unrelated to the addition of the new message model in the main PR.

Suggested labels

action, refactor

Poem

In the meadow where models play,
A new sonnet joins the fray,
Claude's latest, a charming sight,
With words that dance and take flight.
Hopping 'round with joy we sing,
Celebrating what changes bring! 🐇✨

---

Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>, please review it.
  • Generate unit testing code for this file.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai generate unit testing code for this file.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @coderabbitai read src/utils.ts and generate unit testing code.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  • @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.

[pipedream-component-development]

Thank you so much for submitting this! We've added it to our backlog to review, and our team has been notified.

[pipedream-component-development]

Thanks for submitting this PR! When we review PRs, we follow the Pipedream component guidelines. If you're not familiar, here's a quick checklist:

• Create components to address specific use cases whenever possible
• Component keys should follow the format app_name_slug-slugified-component-name
• Components should follow the standard directory structure
• Prefer Node.js client libraries to REST APIs
• When making API requests, handle pagination to ensure all data / events are processed
• Use secret props to capture sensitive data
• Props and methods should be defined in app files whenever possible
• Document methods with JS Docs
• Use optional props whenever possible, and set a default value where you can
• Use async options to accept user input wherever possible

[luancazarine]

Hi @kieronlawson, Thanks for your contribution! LGTM! Ready for QA!

[vunguyenhung]

Hi everyone, all test cases are passed! Ready for release!

Test report
https://vunguyenhung.notion.site/Add-claude-3-5-sonnet-20241022-to-anthropic-models-12dbf548bb5e81c99363e77c0a616b3d