Google Calendar - new-or-updated-event-instant update

[michelle0927]

Limits historical events emitted in the deploy hook to events from withing the previous month.

Summary by CodeRabbit

• New Features
  • Google Calendar “New or Updated Event (Instant)” now limits initial seed to the past month, reducing noise and speeding up first-time setup while preserving normal runtime behavior.
• Chores
  • Bumped Google Calendar component version to 0.5.10.
  • Updated “New or Updated Event (Instant)” source version to 0.1.16.

[vercel]

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

3 Skipped Deployments

Project	Deployment	Preview	Comments	Updated (UTC)
docs-v2	⬜️ Ignored			Aug 12, 2025 8:07pm
pipedream-docs	⬜️ Ignored			Aug 12, 2025 8:07pm
pipedream-docs-redirect-do-not-edit	⬜️ Ignored			Aug 12, 2025 8:07pm

[coderabbitai]

Walkthrough

Version bumps for the Google Calendar component and its “New or Updated Event (Instant)” source. The source’s deploy hook now seeds events from only the past month by adding a timeMin parameter to the initial listEvents call. Runtime behavior for ongoing event detection remains unchanged.

Changes

Cohort / File(s)	Summary of changes
Google Calendar package metadata components/google_calendar/package.json	Bumped package version 0.5.9 → 0.5.10; no other fields changed.
Google Calendar source: new-or-updated-event-instant components/google_calendar/sources/new-or-updated-event-instant/new-or-updated-event-instant.mjs	Source version 0.1.15 → 0.1.16; deploy() adds timeMin (past month) for initial seed listEvents; runtime listEvents unchanged.

Sequence Diagram(s)

sequenceDiagram
  participant User
  participant Source (Deploy)
  participant Google Calendar API

  User->>Source (Deploy): Initialize source
  Source (Deploy)->>Google Calendar API: listEvents(timeMin = now - 1 month)
  Google Calendar API-->>Source (Deploy): Events (seed set)
  Source (Deploy)->>User: Emit up to 25 most recently updated

Loading

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~8 minutes

Poem

I twitch my ears at version’s chime,
A tiny hop through calendar time—
Seed the month, not ages past,
Freshest carrots fetched at last.
0.1.16, I thump with cheer,
Updates nibble, crystal clear. 🥕

✨ Finishing Touches

• 📝 Generate Docstrings

🧪 Generate unit tests

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch google_calendar-source-update

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ 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.
  • 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.
• 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 the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

CodeRabbit Commands (Invoked using PR/Issue comments)

Type @coderabbitai help to get the list of available commands.

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

Status, Documentation and Community

• Visit our Status Page to check the current availability of CodeRabbit.
• 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.

[coderabbitai]

Actionable comments posted: 1

📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 26bbe6a and b980c56.

⛔ Files ignored due to path filters (1)

• pnpm-lock.yaml is excluded by !**/pnpm-lock.yaml

📒 Files selected for processing (2)

• components/google_calendar/package.json (1 hunks)
• components/google_calendar/sources/new-or-updated-event-instant/new-or-updated-event-instant.mjs (2 hunks)

🔇 Additional comments (2)

components/google_calendar/package.json (1)

3-3: Version bump aligns with source changes. LGTM.

The patch version increment to 0.5.10 is appropriate and consistent with the source update.

components/google_calendar/sources/new-or-updated-event-instant/new-or-updated-event-instant.mjs (1)

11-11: Source version bump is correct.

Incrementing to 0.1.16 reflects the deploy-time behavior change. No concerns.