Skip to content

HubSpot: Removing Support for Referencing Custom Object Types by Base Name #16584

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

Merged
merged 5 commits into from
May 12, 2025

Conversation

michelle0927
Copy link
Collaborator

@michelle0927 michelle0927 commented May 7, 2025

Resolves #16576

Looking through all the components, I see that we're already referring to custom objects by either the fullyQualifiedName or the objectTypeId. I updated the prop descriptions of objectType, objectSchema, and customObjectType to clarify what values can be entered.

Summary by CodeRabbit

  • Documentation
    • Improved descriptions for HubSpot object type properties, clarifying accepted values for custom objects.
  • Chores
    • Incremented version numbers for multiple HubSpot actions and sources.
    • Updated package version for the HubSpot integration.

Copy link

vercel bot commented May 7, 2025

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) Visit Preview May 9, 2025 4:08pm
pipedream-docs ⬜️ Ignored (Inspect) May 9, 2025 4:08pm
pipedream-docs-redirect-do-not-edit ⬜️ Ignored (Inspect) May 9, 2025 4:08pm

Copy link
Contributor

coderabbitai bot commented May 7, 2025

Walkthrough

This update consists primarily of incrementing version numbers across numerous HubSpot action and source components, as well as the package manifest. Additionally, descriptions for custom object type props were clarified in the HubSpot app component. No functional, logical, or structural changes were made to the codebase.

Changes

File(s) Change Summary
components/hubspot/actions/, components/hubspot/sources/ Incremented version numbers in exported default objects; no functional or logical changes.
components/hubspot/hubspot.app.mjs Clarified prop descriptions for objectType, objectSchema, and customObjectType to specify expected identifiers for custom objects. No code logic changes.
components/hubspot/package.json Updated package version from 1.2.1 to 1.2.2.

Assessment against linked issues

Objective Addressed Explanation
Remove support for referencing custom object types by base name; update code to use unique identifier only (#16576) Only prop descriptions were updated—no code changes to enforce or implement this requirement.

Poem

A hop, a skip, a version bump,
The HubSpot code gets a gentle jump.
Descriptions polished, numbers rise,
But logic’s unchanged—no surprise!
With every update, the garden grows,
Awaiting features the next PR sows.
🥕✨

Warning

There were issues while running some tools. Please review the errors and either fix the tool's configuration or disable the tool if it's a critical failure.

🔧 ESLint

If the error stems from missing dependencies, add them to the package.json file. For unrecoverable errors (e.g., due to private dependencies), disable the tool in the CodeRabbit configuration.

components/hubspot/sources/new-deal-in-stage/new-deal-in-stage.mjs

Oops! Something went wrong! :(

ESLint: 8.57.1

Error [ERR_MODULE_NOT_FOUND]: Cannot find package 'jsonc-eslint-parser' imported from /eslint.config.mjs
at packageResolve (node:internal/modules/esm/resolve:839:9)
at moduleResolve (node:internal/modules/esm/resolve:908:18)
at defaultResolve (node:internal/modules/esm/resolve:1038:11)
at ModuleLoader.defaultResolve (node:internal/modules/esm/loader:557:12)
at ModuleLoader.resolve (node:internal/modules/esm/loader:525:25)
at ModuleLoader.getModuleJob (node:internal/modules/esm/loader:246:38)
at ModuleJob._link (node:internal/modules/esm/module_job:126:49)

Tip

⚡️ Faster reviews with caching
  • CodeRabbit now supports caching for code and dependencies, helping speed up reviews. This means quicker feedback, reduced wait times, and a smoother review experience overall. Cached data is encrypted and stored securely. This feature will be automatically enabled for all accounts on May 16th. To opt out, configure Review - Disable Cache at either the organization or repository level. If you prefer to disable all data retention across your organization, simply turn off the Data Retention setting under your Organization Settings.

Enjoy the performance boost—your workflow just got faster.


📜 Recent review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between 380d4a3 and 974f11b.

📒 Files selected for processing (2)
  • components/hubspot/package.json (1 hunks)
  • components/hubspot/sources/new-deal-in-stage/new-deal-in-stage.mjs (1 hunks)
✅ Files skipped from review due to trivial changes (1)
  • components/hubspot/sources/new-deal-in-stage/new-deal-in-stage.mjs
🚧 Files skipped from review as they are similar to previous changes (1)
  • components/hubspot/package.json
⏰ Context from checks skipped due to timeout of 90000ms (3)
  • GitHub Check: pnpm publish
  • GitHub Check: Verify TypeScript components
  • GitHub Check: Publish TypeScript components
✨ Finishing Touches
  • 📝 Generate Docstrings

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

Support

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

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 generate docstrings to generate docstrings for this PR.
  • @coderabbitai generate sequence diagram to generate a sequence diagram of the changes in this 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.

@michelle0927 michelle0927 marked this pull request as ready for review May 7, 2025 18:23
Copy link
Contributor

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 0

🧹 Nitpick comments (3)
components/hubspot/hubspot.app.mjs (3)

83-87: Refine grammar and consistency in objectType description
The term "short-hand" is typically written as "shorthand". Consider updating:

  • Replace "short-hand" with "shorthand"
  • Optionally change "aka" to "also known as" for clarity

Example:

-description: "Watch for new events concerning the object type specified. For custom objects, this is the object's `fullyQualifiedName`, `objectTypeId`, or the short-hand custom object type name (aka `p_{object_name}`)"
+description: "Watch for new events concerning the object type specified. For custom objects, this is the object's `fullyQualifiedName`, `objectTypeId`, or the shorthand custom object type name (also known as `p_{object_name}`)"

101-105: Align objectSchema description style
To maintain consistency with other prop descriptions, consider:

  • Starting the sentence with "Watch for new events concerning objects…" to match the phrasing in objectType
  • Clarifying that objectSchema expects the custom object's objectTypeId

Example:

-description: "Watch for new events of objects with the specified custom schema. This is the `objectTypeId` of an object."
+description: "Watch for new events concerning objects of the specified custom schema. This prop expects the custom object's `objectTypeId`."

437-441: Refine grammar in customObjectType description
Similar to the objectType description, unify hyphenation and phrasing:

  • Change "short-hand" to "shorthand"
  • Replace "aka" with "also known as"

Example:

-description: "The type of custom object to create. This is the object's `fullyQualifiedName`, `objectTypeId`, or the short-hand custom object type name (aka `p_{object_name}`)"
+description: "The type of custom object to create. This is the object's `fullyQualifiedName`, `objectTypeId`, or the shorthand custom object type name (also known as `p_{object_name}`)"
📜 Review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between 6d66e61 and 380d4a3.

⛔ Files ignored due to path filters (1)
  • pnpm-lock.yaml is excluded by !**/pnpm-lock.yaml
📒 Files selected for processing (52)
  • components/hubspot/actions/add-contact-to-list/add-contact-to-list.mjs (1 hunks)
  • components/hubspot/actions/batch-create-or-update-contact/batch-create-or-update-contact.mjs (1 hunks)
  • components/hubspot/actions/create-associations/create-associations.mjs (1 hunks)
  • components/hubspot/actions/create-communication/create-communication.mjs (1 hunks)
  • components/hubspot/actions/create-company/create-company.mjs (1 hunks)
  • components/hubspot/actions/create-custom-object/create-custom-object.mjs (1 hunks)
  • components/hubspot/actions/create-deal/create-deal.mjs (1 hunks)
  • components/hubspot/actions/create-engagement/create-engagement.mjs (1 hunks)
  • components/hubspot/actions/create-lead/create-lead.mjs (1 hunks)
  • components/hubspot/actions/create-meeting/create-meeting.mjs (1 hunks)
  • components/hubspot/actions/create-or-update-contact/create-or-update-contact.mjs (1 hunks)
  • components/hubspot/actions/create-task/create-task.mjs (1 hunks)
  • components/hubspot/actions/create-ticket/create-ticket.mjs (1 hunks)
  • components/hubspot/actions/enroll-contact-into-workflow/enroll-contact-into-workflow.mjs (1 hunks)
  • components/hubspot/actions/get-associated-meetings/get-associated-meetings.mjs (1 hunks)
  • components/hubspot/actions/get-company/get-company.mjs (1 hunks)
  • components/hubspot/actions/get-contact/get-contact.mjs (1 hunks)
  • components/hubspot/actions/get-deal/get-deal.mjs (1 hunks)
  • components/hubspot/actions/get-file-public-url/get-file-public-url.mjs (1 hunks)
  • components/hubspot/actions/get-meeting/get-meeting.mjs (1 hunks)
  • components/hubspot/actions/search-crm/search-crm.mjs (1 hunks)
  • components/hubspot/actions/update-company/update-company.mjs (1 hunks)
  • components/hubspot/actions/update-contact/update-contact.mjs (1 hunks)
  • components/hubspot/actions/update-custom-object/update-custom-object.mjs (1 hunks)
  • components/hubspot/actions/update-deal/update-deal.mjs (1 hunks)
  • components/hubspot/actions/update-lead/update-lead.mjs (1 hunks)
  • components/hubspot/hubspot.app.mjs (3 hunks)
  • components/hubspot/package.json (1 hunks)
  • components/hubspot/sources/delete-blog-article/delete-blog-article.mjs (1 hunks)
  • components/hubspot/sources/new-company-property-change/new-company-property-change.mjs (1 hunks)
  • components/hubspot/sources/new-contact-property-change/new-contact-property-change.mjs (1 hunks)
  • components/hubspot/sources/new-custom-object-property-change/new-custom-object-property-change.mjs (1 hunks)
  • components/hubspot/sources/new-deal-in-stage/new-deal-in-stage.mjs (1 hunks)
  • components/hubspot/sources/new-deal-property-change/new-deal-property-change.mjs (1 hunks)
  • components/hubspot/sources/new-email-event/new-email-event.mjs (1 hunks)
  • components/hubspot/sources/new-email-subscriptions-timeline/new-email-subscriptions-timeline.mjs (1 hunks)
  • components/hubspot/sources/new-engagement/new-engagement.mjs (1 hunks)
  • components/hubspot/sources/new-event/new-event.mjs (1 hunks)
  • components/hubspot/sources/new-form-submission/new-form-submission.mjs (1 hunks)
  • components/hubspot/sources/new-note/new-note.mjs (1 hunks)
  • components/hubspot/sources/new-or-updated-blog-article/new-or-updated-blog-article.mjs (1 hunks)
  • components/hubspot/sources/new-or-updated-company/new-or-updated-company.mjs (1 hunks)
  • components/hubspot/sources/new-or-updated-contact/new-or-updated-contact.mjs (1 hunks)
  • components/hubspot/sources/new-or-updated-crm-object/new-or-updated-crm-object.mjs (1 hunks)
  • components/hubspot/sources/new-or-updated-custom-object/new-or-updated-custom-object.mjs (1 hunks)
  • components/hubspot/sources/new-or-updated-deal/new-or-updated-deal.mjs (1 hunks)
  • components/hubspot/sources/new-or-updated-line-item/new-or-updated-line-item.mjs (1 hunks)
  • components/hubspot/sources/new-or-updated-product/new-or-updated-product.mjs (1 hunks)
  • components/hubspot/sources/new-social-media-message/new-social-media-message.mjs (1 hunks)
  • components/hubspot/sources/new-task/new-task.mjs (1 hunks)
  • components/hubspot/sources/new-ticket-property-change/new-ticket-property-change.mjs (1 hunks)
  • components/hubspot/sources/new-ticket/new-ticket.mjs (1 hunks)
⏰ Context from checks skipped due to timeout of 90000ms (2)
  • GitHub Check: Publish TypeScript components
  • GitHub Check: Verify TypeScript components
🔇 Additional comments (52)
components/hubspot/package.json (2)

3-3: Approve version bump to 1.2.1. The patch version increment aligns with the coordinated updates across all HubSpot components in this PR.


1-23: Missing hubspot.app.mjs changes for prop descriptions. The PR objectives mention clarifying the objectType, objectSchema, and customObjectType descriptions in components/hubspot/hubspot.app.mjs, but those updates aren’t present here. Please confirm you’ve included that file or provide its contents so we can validate the intended documentation changes.

components/hubspot/actions/get-file-public-url/get-file-public-url.mjs (1)

7-7: Approve version bump to 0.0.17. This aligns with the package.json update and matches the increments applied to other HubSpot action modules.

components/hubspot/sources/new-email-subscriptions-timeline/new-email-subscriptions-timeline.mjs (1)

9-9: Approve version bump to 0.0.22. Version increment is consistent with the pattern across HubSpot source components in this PR.

components/hubspot/sources/new-or-updated-product/new-or-updated-product.mjs (1)

12-12: Approve version bump to 0.0.9. The patch increment matches the coordinated version updates for custom-object-related components.

components/hubspot/sources/new-or-updated-custom-object/new-or-updated-custom-object.mjs (1)

10-10: Approve version bump to 0.0.11. Consistent with other HubSpot sources and aligned with the overall package version bump.

components/hubspot/sources/new-note/new-note.mjs (1)

11-11: Version bump to 1.0.3 is correct
This aligns with the coordinated version updates across all HubSpot components in this PR.

components/hubspot/sources/new-ticket-property-change/new-ticket-property-change.mjs (1)

10-10: Version bump to 0.0.16 is correct
Consistent with the overall version refresh for HubSpot source components.

components/hubspot/sources/new-or-updated-blog-article/new-or-updated-blog-article.mjs (1)

10-10: Version bump to 0.0.9 is correct
Matches the PR’s broad version increment strategy.

components/hubspot/sources/new-social-media-message/new-social-media-message.mjs (1)

9-9: Version bump to 0.0.22 is correct
Follows the coordinated versioning approach across HubSpot components.

components/hubspot/actions/get-contact/get-contact.mjs (1)

9-9: Version bump to 0.0.17 is correct
Consistent version increment for HubSpot action components.

components/hubspot/actions/update-lead/update-lead.mjs (1)

10-10: Approve version bump to 0.0.9.
The version field has been correctly incremented from the prior "0.0.8" to "0.0.9" in line with the coordinated HubSpot component release.

components/hubspot/actions/create-deal/create-deal.mjs (1)

9-9: Approve version bump to 0.0.21.
The version number has been correctly updated from "0.0.20" to "0.0.21", matching the broader HubSpot integration rollout.

components/hubspot/sources/new-email-event/new-email-event.mjs (1)

11-11: Approve version bump to 0.0.25.
The version has been incremented from "0.0.24" to "0.0.25" to stay consistent with the cross-component version synchronization.

components/hubspot/actions/get-company/get-company.mjs (1)

9-9: Approve version bump to 0.0.17.
Updated from "0.0.16" to "0.0.17" as part of the HubSpot actions version alignment.

components/hubspot/actions/add-contact-to-list/add-contact-to-list.mjs (1)

7-7: Approve version bump to 0.0.17.
Version correctly moved from "0.0.16" to "0.0.17", consistent with the PR’s coordinated component upgrades.

components/hubspot/sources/new-or-updated-deal/new-or-updated-deal.mjs (1)

12-12: Approve version bump to 0.0.9
The component’s version has been correctly incremented to reflect a non-breaking, minor update.

components/hubspot/sources/new-engagement/new-engagement.mjs (1)

11-11: Approve version bump to 0.0.27
This patch-level version increment aligns with the rest of the HubSpot integration components and introduces no functional changes.

components/hubspot/sources/new-or-updated-company/new-or-updated-company.mjs (1)

12-12: Approve version bump to 0.0.9
The minor version has been bumped consistently with similar source components, with no logic modifications.

components/hubspot/sources/new-contact-property-change/new-contact-property-change.mjs (1)

10-10: Approve version bump to 0.0.17
The component version is correctly updated for a non-breaking change; functionality remains unchanged.

components/hubspot/sources/new-or-updated-contact/new-or-updated-contact.mjs (1)

12-12: Approve version bump to 0.0.9
This patch bump is consistent with the PR’s coordinated version updates and does not affect any behavior.

components/hubspot/sources/new-event/new-event.mjs (1)

11-11: Version bump only, no logic changes
The patch version has been correctly incremented from “0.0.25” to “0.0.26” to stay in sync with the other HubSpot components.

components/hubspot/actions/get-deal/get-deal.mjs (1)

9-9: Version bump only, no logic changes
The version has been updated from “0.0.16” to “0.0.17” without any functional or structural modifications.

components/hubspot/sources/new-ticket/new-ticket.mjs (1)

12-12: Version bump only, no logic changes
Updated the version from “0.0.21” to “0.0.22” consistently with the rest of the HubSpot source modules.

components/hubspot/sources/new-deal-in-stage/new-deal-in-stage.mjs (1)

10-10: Version bump only, no logic changes
Incremented version from “0.0.26” to “0.0.27” to align with the coordinated patch release.

components/hubspot/actions/create-or-update-contact/create-or-update-contact.mjs (1)

9-9: Version bump only, no logic changes
The action’s patch version is now “0.0.19” (from “0.0.18”), with no other changes to behavior.

components/hubspot/sources/new-or-updated-line-item/new-or-updated-line-item.mjs (1)

12-12: Approve version bump
The component version has been correctly incremented to "0.0.9", matching the coordinated release across HubSpot sources. No other changes detected.

components/hubspot/actions/create-communication/create-communication.mjs (1)

11-11: Approve version bump
The action version has been updated to "0.0.10" consistently with the PR-wide version increments. No functional changes observed.

components/hubspot/actions/create-meeting/create-meeting.mjs (1)

13-13: Approve version bump
The action version was correctly bumped to "0.0.2" in line with related meeting components. No logic or structure alterations.

components/hubspot/sources/new-deal-property-change/new-deal-property-change.mjs (1)

10-10: Approve version bump
Version has been incremented to "0.0.16" consistent with the deal-related components update. No other modifications present.

components/hubspot/actions/create-lead/create-lead.mjs (1)

12-12: Approve version bump
The lead creation action version is now "0.0.9", aligning with the coordinated HubSpot release. No functional changes detected.

components/hubspot/actions/batch-create-or-update-contact/batch-create-or-update-contact.mjs (1)

7-7: Consistent version bump
This change only increments the action’s version from 0.0.13 to 0.0.14 to align with the coordinated release. No logic or behavior was altered.

components/hubspot/sources/new-custom-object-property-change/new-custom-object-property-change.mjs (1)

9-9: Consistent version bump
The component version is updated from 0.0.6 to 0.0.7 without any functional changes, matching the PR’s coordinated versioning approach.

components/hubspot/actions/create-ticket/create-ticket.mjs (1)

9-9: Consistent version bump
Upgraded version from 0.0.11 to 0.0.12. No other modifications to props, methods, or logic.

components/hubspot/actions/get-associated-meetings/get-associated-meetings.mjs (1)

9-9: Consistent version bump
Version updated from 0.0.1 to 0.0.2 only. All existing logic and structure remain unchanged.

components/hubspot/actions/update-deal/update-deal.mjs (1)

10-10: Consistent version bump
Bumped version from 0.0.7 to 0.0.8. No other adjustments to functionality or exports.

components/hubspot/actions/get-meeting/get-meeting.mjs (1)

9-9: Patch version bump approved.

The component version has been correctly updated from "0.0.1" to "0.0.2" with no other modifications, aligning with the planned release.

components/hubspot/sources/new-form-submission/new-form-submission.mjs (1)

9-9: Patch version bump approved.

The version increment from "0.0.26" to "0.0.27" is consistent and introduces no functional changes.

components/hubspot/sources/delete-blog-article/delete-blog-article.mjs (1)

9-9: Patch version bump approved.

Updating the version from "0.0.21" to "0.0.22" correctly reflects a patch release without code changes.

components/hubspot/actions/create-engagement/create-engagement.mjs (1)

12-12: Patch version bump approved.

The component version update from "0.0.19" to "0.0.20" is correct and isolated to the version field.

components/hubspot/sources/new-or-updated-crm-object/new-or-updated-crm-object.mjs (1)

10-10: Patch version bump approved.

The version has been bumped from "0.0.21" to "0.0.22" as part of the coordinated release. No other changes detected.

components/hubspot/actions/create-custom-object/create-custom-object.mjs (1)

9-9: Version bump from 1.0.2 to 1.0.3
Matches the coordinated version increments across HubSpot components in this PR. No functional or structural changes introduced.

components/hubspot/sources/new-company-property-change/new-company-property-change.mjs (1)

10-10: Version bump from 0.0.14 to 0.0.15
Consistent with the PR’s batch update of HubSpot source components. No logic or export changes detected.

components/hubspot/actions/update-custom-object/update-custom-object.mjs (1)

9-9: Version bump from 1.0.2 to 1.0.3
Aligned with the coordinated version updates for HubSpot action components. No behavioral changes.

components/hubspot/actions/enroll-contact-into-workflow/enroll-contact-into-workflow.mjs (1)

7-7: Version bump from 0.0.16 to 0.0.17
Consistent minor version update across HubSpot actions; functionality remains unchanged.

components/hubspot/actions/create-task/create-task.mjs (1)

10-10: Version bump from 0.0.1 to 0.0.2
Part of the collective version bumps for HubSpot engagement components. No impact on logic or error handling.

components/hubspot/actions/update-company/update-company.mjs (1)

10-10: Version bump consistent with release strategy
The component version has been updated from 0.0.16 to 0.0.17, matching the coordinated minor release across HubSpot actions. No functional or structural changes detected.

components/hubspot/actions/create-company/create-company.mjs (1)

9-9: Version bump for create-company action
The version string was incremented from 0.0.20 to 0.0.21 in line with other HubSpot components. No other modifications; logic remains unaffected.

components/hubspot/actions/create-associations/create-associations.mjs (1)

8-8: Incremented component version
Updated from 1.0.2 to 1.0.3 to align with the overall release. This change is purely metadata—no impact on functionality.

components/hubspot/sources/new-task/new-task.mjs (1)

11-11: Source version increment
Bumped the source version from 1.0.2 to 1.0.3 in lockstep with the PR’s mass version updates. No functional code altered.

components/hubspot/actions/search-crm/search-crm.mjs (1)

19-19: Search CRM action version bump
Version updated from 1.0.2 to 1.0.3 to reflect the minor release. No logic or props changes introduced.

components/hubspot/actions/update-contact/update-contact.mjs (1)

9-11: Approve version bump to 0.0.18
The version increment aligns with the coordinated updates across HubSpot action and source components. No other functional or structural changes detected.

jcortes
jcortes previously approved these changes May 7, 2025
Copy link
Collaborator

@jcortes jcortes left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hi @michelle0927 lgtm!

@michelle0927
Copy link
Collaborator Author

/approve

@michelle0927 michelle0927 merged commit 2c752f6 into master May 12, 2025
11 checks passed
@michelle0927 michelle0927 deleted the issue-16576 branch May 12, 2025 16:56
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

[FEATURE] HubSpot: Removing Support for Referencing Custom Object Types by Base Name
2 participants