fix: reorder options for clarity and consistency

[fizikiukas]

Summary by CodeRabbit

• Refactor
  • Reordered available operation options in the Reach configuration; functionality and defaults remain unchanged.
• Chores
  • Bumped package version to 1.0.15.

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

[coderabbitai]

📝 Walkthrough

Walkthrough

Reordered two Reach operation options in the Hostinger API node and updated package metadata: package version bumped and top-level npm dependency overrides added to package.json. No functional signatures or exported API changes.

Changes

Cohort / File(s)	Summary
Reach operation options nodes/hostingerApi/HostingerApi.node.ts	Reordered the Reach operation options array: moved List Contacts and List Segments entries to the end of the options. Functionality and default (listContacts) unchanged.
Package manifest update package.json	Bumped version from 1.0.14 to 1.0.15 and added a top-level overrides section specifying versions for n8n-workflow transitive deps: form-data (^4.0.4) and lodash (^4.17.23).

Estimated code review effort

🎯 3 (Moderate) | ⏱️ ~20 minutes

🚥 Pre-merge checks | ✅ 2 | ❌ 1

❌ Failed checks (1 inconclusive)

Check name	Status	Explanation	Resolution
Title check	❓ Inconclusive	The pull request title references reordering options for clarity, but the changeset also includes a version bump and npm overrides in package.json that are not mentioned in the title.	Clarify whether the title should cover the version bump and npm overrides, or if those changes were incidental to the main objective of reordering options.

✅ Passed checks (2 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

---

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

[coderabbitai]

Actionable comments posted: 0

🧹 Nitpick comments (1)

nodes/hostingerApi/HostingerApi.node.ts (1)

420-423: Reconsider placing the default option first.

The default operation is listContacts (line 425), but it's now positioned near the end of the dropdown. Standard UX practice places default options first for better visibility and user expectation. Consider either:

• Moving "List Contacts" back to the first position, or
• Changing the default to a more contextually appropriate operation if "List Contacts" shouldn't be the primary action

</review_comment_end>

📜 Review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 1679ec1 and 784ed10.

📒 Files selected for processing (1)

• nodes/hostingerApi/HostingerApi.node.ts (1 hunks)