Adding info prop to 'upcoming-event-alert'

[GTFalcao]

No need for QA, just merge when approved

Summary by CodeRabbit

• Improvements

  • Added informational alert to Google Calendar upcoming event alerts explaining API key requirements and available polling alternatives.

• Chores

  • Updated component versions.

_{✏️ Tip: You can customize this high-level summary in your review settings.}

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

2 Skipped Deployments

Project	Deployment	Preview	Comments	Updated (UTC)
pipedream-docs	Ignored			Dec 10, 2025 6:15pm
pipedream-docs-redirect-do-not-edit	Ignored			Dec 10, 2025 6:15pm

[coderabbitai]

Walkthrough

Version bumps applied to the Google Calendar component package and upcoming-event-alert source. A new informational alert property has been added to the upcoming-event-alert source configuration to inform users about API key requirements and alternative polling-based source options.

Changes

Cohort / File(s)	Summary
Package version update components/google_calendar/package.json	Incremented package version from 0.6.0 to 0.6.1
Source component updates components/google_calendar/sources/upcoming-event-alert/upcoming-event-alert.mjs	Bumped source version from 0.1.0 to 0.1.1 and added a new public pollingInfo alert-type prop providing informational content about Pipedream API key requirements and alternative polling source option

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

Pre-merge checks and finishing touches

❌ Failed checks (1 warning)

Check name	Status	Explanation	Resolution
Description check	⚠️ Warning	The PR description lacks the required 'WHY' section from the template and provides only a dismissive statement instead of explaining the purpose or rationale for the changes.	Provide a detailed 'WHY' section explaining the motivation, benefits, and rationale for adding the pollingInfo alert prop to the upcoming-event-alert source.

✅ Passed checks (2 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title accurately describes the main change: adding an info prop to the upcoming-event-alert source component, which aligns with the summary showing a new pollingInfo prop added.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

✨ Finishing touches

• 📝 Generate docstrings

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch google-calendar-info-prop

---

📜 Recent review details

Configuration used: CodeRabbit UI

Review profile: ASSERTIVE

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between dd65b8e and 45646f2.

📒 Files selected for processing (2)

• components/google_calendar/package.json (1 hunks)
• components/google_calendar/sources/upcoming-event-alert/upcoming-event-alert.mjs (1 hunks)

⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (4)

• GitHub Check: Verify TypeScript components
• GitHub Check: Publish TypeScript components
• GitHub Check: pnpm publish
• GitHub Check: Lint Code Base

🔇 Additional comments (2)

components/google_calendar/package.json (1)

3-3: Package version bump aligns with scoped change

Patch version bump from 0.6.0 to 0.6.1 is appropriate for adding a non-breaking informational prop to a single source; nothing else in the manifest needs adjustment.

components/google_calendar/sources/upcoming-event-alert/upcoming-event-alert.mjs (1)

9-19: Alert prop addition and version bump look correct

• Bumping the source version to 0.1.1 matches the non-breaking UI/config addition.
• The new pollingInfo alert prop is well-structured and clearly explains the API key requirement and polling alternative, without impacting runtime behavior.

No changes requested.

---

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[luancazarine]

Hi @GTFalcao, LGTM! Ready for QA!

[vunguyenhung]

For Integration QA:

• Source Test Report: https://www.notion.so/Adding-info-prop-to-upcoming-event-alert-Sources-2c6bf548bb5e81f79374c23b6d8f87e8

[vunguyenhung]

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

Test reports

• Adding info prop to 'upcoming-event-alert' - Sources: https://www.notion.so/Adding-info-prop-to-upcoming-event-alert-Sources-2c6bf548bb5e81f79374c23b6d8f87e8