HubSpot CLI, Node, and CI Preflight Checklist

CI failures are often planning failures disguised as command failures. Before a migration or upload workflow reaches CI, record the local HubSpot CLI version, local Node version, CI Node version, authenticated account strategy, and where secrets are stored.

Pin or document runtime versions where practical, but avoid unsupported version claims unless you have rechecked the current HubSpot CLI documentation. This page intentionally says 'check Node version' rather than asserting a specific Node requirement from memory.

Avoid relying on implicit account state in CI. A repeatable workflow should make the target account, environment variables, and upload command explicit enough for another developer to review without guessing.

Inventory the values CI needs, but do not paste tokens, client secrets, private keys, or account credentials into docs, tickets, or agent prompts. The handoff should say where secrets live, who owns them, and which environment uses them.

Review logs for accidental disclosure. A migration or upload workflow is not ready for client handoff if command output could expose OAuth secrets, tokens, or internal account IDs unnecessarily.

For agencies, separate client-facing evidence from internal build details. The client may need proof of version checks and source verification, not raw secret names or CI internals.

Before enabling an upload/deploy step, confirm the app classification and command path. A pipeline that uploads the wrong project path or target account can create confusion even if every command succeeds.

Add a source-check step to the release checklist: open HubSpot's current CLI reference and project commands docs before production deployment. This is especially important when a platform sunset or migration deadline is driving the work.

If a command changes or official docs differ from this local archive, follow the current official docs and update the checklist for future runs.