Gmail - bump new-email-received version

[michelle0927]

Summary by CodeRabbit

• New Features
  • Updated the Gmail package to version 0.1.8, enhancing compatibility and performance.
  • Upgraded the "New Email Received" component to version 0.1.5, ensuring improved functionality.

[vercel]

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

3 Skipped Deployments

Name	Status	Preview	Comments	Updated (UTC)
docs-v2	⬜️ Ignored (Inspect)			Sep 27, 2024 4:18pm
pipedream-docs	⬜️ Ignored (Inspect)			Sep 27, 2024 4:18pm
pipedream-docs-redirect-do-not-edit	⬜️ Ignored (Inspect)			Sep 27, 2024 4:18pm

[coderabbitai]

Walkthrough

This pull request updates the version of the @pipedream/gmail package from 0.1.7 to 0.1.8 and the version of the "New Email Received" component from 0.1.4 to 0.1.5. No additional changes to functionality, dependencies, or structure are present in the affected files.

Changes

File	Change Summary
components/gmail/package.json	Version updated from 0.1.7 to 0.1.8
components/gmail/sources/new-email-received/new-email-received.mjs	Version updated from 0.1.4 to 0.1.5

Possibly related PRs

• Gmail - Update verify-client-id #13959: Updates the version of the @pipedream/gmail package in package.json, related to the main PR.
• Gmail - Improve New Email Received event shape #13992: Updates the version of @pipedream/gmail and includes a version update for the new-email-received.mjs file, relevant to the main PR.
• Gmail - parse name & email in parsedHeaders #14111: Updates the version of the @pipedream/gmail package in package.json, aligning with the version increment in the main PR.

🐰 In the garden, changes bloom,
New versions hop, dispelling gloom.
Gmail's package, fresh and bright,
New emails dance in morning light.
With every update, joy we find,
A leap of progress, sweet and kind! 🌼

---

📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL

📥 Commits

Files that changed from the base of the PR and between 08b948b and 475b1ac.

📒 Files selected for processing (2)

• components/gmail/package.json (1 hunks)
• components/gmail/sources/new-email-received/new-email-received.mjs (1 hunks)

✅ Files skipped from review due to trivial changes (2)

• components/gmail/package.json
• components/gmail/sources/new-email-received/new-email-received.mjs

---

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.