Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Republish components for Doppler, Fullenrich, & Parsehub #14744

Merged
merged 4 commits into from
Nov 29, 2024

Conversation

js07
Copy link
Contributor

@js07 js07 commented Nov 26, 2024

WHAT

Bump the versions for following components to republish them:

  • Doppler Marketing Automation Add or Update Subscriber
  • Doppler Marketing Automation Unsubscribe Email
  • Fullenrich Enrich Contact
  • Fullenrich Get Enrichment Result
  • Parsehub Get Data for a Run
  • Parsehub Get Project Details
  • Parsehub Run Parsehub Project

WHY

These components failed to publish to the Pipedream registry when initially pushed to the master branch. For a list of actions and sources in the Pipedream registry for each app, see their app pages:

Summary by CodeRabbit

Release Notes

  • New Features

    • Incremented version numbers for various actions and packages within the marketing automation and enrichment components, ensuring users have access to the latest updates.
  • Bug Fixes

    • Updated filtering logic in the unsubscribe action to exclude already unsubscribed email addresses, improving the accuracy of unsubscription requests.
  • Documentation

    • Version updates documented for all affected components, reflecting the latest changes in package versions.

Copy link

vercel bot commented Nov 26, 2024

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) Nov 26, 2024 10:13pm
pipedream-docs ⬜️ Ignored (Inspect) Nov 26, 2024 10:13pm
pipedream-docs-redirect-do-not-edit ⬜️ Ignored (Inspect) Nov 26, 2024 10:13pm

Copy link
Contributor

coderabbitai bot commented Nov 26, 2024

Walkthrough

The changes in this pull request primarily involve updating the version numbers of various actions and packages within the doppler_marketing_automation and parsehub components. The version increments from "0.0.1" to "0.0.2" are consistent across multiple action files, while the package.json files for both components reflect an update from "0.2.0" to "0.2.1" and "0.1.0" to "0.1.1" respectively. Additionally, a modification to the filter function in the unsubscribe-email action is noted.

Changes

File Change Summary
components/doppler_marketing_automation/actions/add-update-subscriber/add-update-subscriber.mjs Version updated from "0.0.1" to "0.0.2".
components/doppler_marketing_automation/actions/unsubscribe-email/unsubscribe-email.mjs Version updated from "0.0.1" to "0.0.2"; filter function modified to check status not equal to "unsubscribed".
components/doppler_marketing_automation/package.json Version updated from "0.2.0" to "0.2.1".
components/fullenrich/actions/enrich-contact/enrich-contact.mjs Version updated from "0.0.1" to "0.0.2".
components/fullenrich/actions/get-enrichment-result/get-enrichment-result.mjs Version updated from "0.0.1" to "0.0.2".
components/fullenrich/package.json Version updated from "0.1.0" to "0.1.1".
components/parsehub/actions/get-data-run/get-data-run.mjs Version updated from "0.0.1" to "0.0.2".
components/parsehub/actions/get-project/get-project.mjs Version updated from "0.0.1" to "0.0.2".
components/parsehub/actions/run-project/run-project.mjs Version updated from "0.0.1" to "0.0.2".
components/parsehub/package.json Version updated from "0.1.0" to "0.1.1".

Possibly related PRs

Suggested labels

bug, actions

Suggested reviewers

  • jcortes
  • lcaresia

🐰 "In the meadow where bunnies play,
Version numbers hop and sway.
From '0.0.1' to '0.0.2',
A leap of change, so fresh and new!
With every update, we grow and thrive,
In the world of code, we come alive!" 🐇


📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL

📥 Commits

Reviewing files that changed from the base of the PR and between e8e6374 and c510205.

📒 Files selected for processing (10)
  • components/doppler_marketing_automation/actions/add-update-subscriber/add-update-subscriber.mjs (1 hunks)
  • components/doppler_marketing_automation/actions/unsubscribe-email/unsubscribe-email.mjs (1 hunks)
  • components/doppler_marketing_automation/package.json (1 hunks)
  • components/fullenrich/actions/enrich-contact/enrich-contact.mjs (1 hunks)
  • components/fullenrich/actions/get-enrichment-result/get-enrichment-result.mjs (1 hunks)
  • components/fullenrich/package.json (1 hunks)
  • components/parsehub/actions/get-data-run/get-data-run.mjs (1 hunks)
  • components/parsehub/actions/get-project/get-project.mjs (1 hunks)
  • components/parsehub/actions/run-project/run-project.mjs (1 hunks)
  • components/parsehub/package.json (1 hunks)
✅ Files skipped from review due to trivial changes (9)
  • components/doppler_marketing_automation/actions/add-update-subscriber/add-update-subscriber.mjs
  • components/doppler_marketing_automation/package.json
  • components/fullenrich/actions/enrich-contact/enrich-contact.mjs
  • components/fullenrich/actions/get-enrichment-result/get-enrichment-result.mjs
  • components/fullenrich/package.json
  • components/parsehub/actions/get-data-run/get-data-run.mjs
  • components/parsehub/actions/get-project/get-project.mjs
  • components/parsehub/actions/run-project/run-project.mjs
  • components/parsehub/package.json
🔇 Additional comments (2)
components/doppler_marketing_automation/actions/unsubscribe-email/unsubscribe-email.mjs (2)

7-7: LGTM: Version bump aligns with republishing objective

The version increment from 0.0.1 to 0.0.2 is appropriate for this republishing effort.


Line range hint 15-15: LGTM: Improved input validation

The filter condition status != "unsubscribed" is a good addition that prevents attempting to unsubscribe already unsubscribed emails. This improves the user experience by only showing relevant email options in the dropdown.


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
🪧 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.

@js07 js07 marked this pull request as ready for review November 27, 2024 17:18
@vunguyenhung
Copy link
Collaborator

Since they're already tested. I'll move this to ready for release immediately

@vunguyenhung
Copy link
Collaborator

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

Test report
https://vunguyenhung.notion.site/Republish-components-for-Doppler-Fullenrich-Parsehub-14cbf548bb5e8112b7f2f9a5a4db1925

@vunguyenhung vunguyenhung merged commit 72b131c into master Nov 29, 2024
11 checks passed
@vunguyenhung vunguyenhung deleted the republish-doppler-fullenrich-parsehub-components branch November 29, 2024 01:24
@coderabbitai coderabbitai bot mentioned this pull request Dec 11, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Development

Successfully merging this pull request may close these issues.

3 participants