Refactored internal code

Refactored internal code

Updated spectral to 10.39.1

Updated spectral to 10.39.0

Published the component as an npm package, so code-native integrations can install it and call its actions, triggers and data sources from code with TypeScript types

Updated spectral to 10.34.1

• Added an optional Look-back Date input to the New and Updated Applications trigger for performing an initial sync of applications. The initial sync begins on the first recurrence and backfills every application with activity on or after the specified date, seeding each once and ignoring the trigger's filters; later recurrences are unaffected. Leave it empty to start from the first recurrence with no backfill
• Added opt-in batching to the New and Updated Applications trigger, dispatching each changed application individually or in configured batches so large backlogs drain in one recurrence; enabling it changes the shape a downstream step receives
• Updated the New and Updated Applications trigger to return at most 5,000 applications per recurrence when batching is off, so a larger backlog drains across later recurrences instead of in one execution

Restructured action inputs into structured objects for an improved configuration experience

• Create Candidate and Edit Candidate group their contact inputs into Contact Information; Edit Candidate additionally groups its optional name inputs into Name Information (Create Candidate's name inputs are required and stay flat)
• The list actions (List Candidates, List Applications, List Jobs, List Users, and List Attachments) group their created, updated, and last-activity date filters into Date Range Filters
• List Applications, List Attachments, List Users, and List Jobs group their record-ID filters into ID Filters
• Edit Application groups its source, referrer, recruiter, coordinator, and prospect IDs into an Assignment IDs structured object
• Reject Application groups its rejection email inputs into a Rejection Email structured object
• Grouped pagination inputs into a Pagination structured object across the list actions (breaking: input keys changed); update saved integration configurations to use the new nested keys:
  • List Jobs (Harvest v1/v2), List Candidates (Harvest v1/v2), List Applications (Harvest v1/v2), List Users (Harvest v1/v2): per_page → pagination.per_page, page → pagination.page
  • List Jobs, List Candidates, List Applications, List Users, List Attachments (Harvest v3): perPage → pagination.perPage, cursor → pagination.cursor; fetchAll stays a top-level input

• Added full Harvest v3 API support alongside the existing v1/v2 surface; the v1/v2 API sunsets on August 31, 2026, so existing actions keep working unchanged until then and their labels now carry a (Harvest v1/v2) suffix
• Added the OAuth 2.0 Client Credentials (Harvest V3) connection for the Harvest v3 API
• Added 25 v3 actions with clean labels: List/Get/Edit/Delete Application, the new Reject Application and Unreject Application (v3 moves rejection out of application edits), List/Get/Create/Edit/Delete Candidate, the new List/Create/Delete Attachment actions (v3 moves candidate attachments to a dedicated resource), List/Get/Create/Edit Job, List/Get/Create/Edit User, Activate User and Deactivate User (replacing v1 enable/disable), and a v3 Raw Request
• Added the v3 New and Updated Applications polling trigger using the last_activity_at[gte] filter with cursor-based pagination; the v1 trigger remains available as deprecated
• Added v3 data sources for applications, candidates, custom fields, departments, jobs, offices, users, and the new Fetch Rejection Reasons powering the Reject Application dropdown
• Changed the API Key connection label to API Key (Harvest v1/v2) — it only reaches the sunsetting v1/v2 API
• Added the deprecated v1 New and Updated Applications polling trigger using the Harvest API's last_activity_after filter, walking all paginated results and partitioning them into created and updated buckets based on each application's created_at and last_activity_at timestamps
• Changed the Secret Key trigger input to a masked password field to prevent the value from being exposed in plaintext within the configuration UI

Updated spectral version