master-zapier-plan-draft/research/zapier/raw/docs/integrations/news/2025/v18.0.6.md
George Lambert b4150c8250 Milestone 0: import zappier billing, Verae middleware, and Zapier research
Compose-ready workspace: packages/zappier (rate card, portal, Stripe),
packages/verae-zapier-middleware (timestamp + NATS), packages/verae-zapier
(CLI app), vendor/zapier-platform, and research/zapier vendor corpus.

Gate 0 structure checks pass. Product code and research are not yet wired.
2026-09-09 02:37:36 -04:00

1.2 KiB

Documentation Index

Fetch the complete documentation index at: https://docs.zapier.com/llms.txt Use this file to discover all available pages before exploring further.

What's changed in v18.0.6

Package manager detection from zapier build

Released: 2025-12-24

The zapier build command was harcoded to use npm install. As alternate package managers gain adoption, the zapier build command will respect your app's package manager of choice. It does this by checking the packageManager on the package.json file. If it is not defined, it will look for any relevant lock files. If still, none is defined, then will fallback to npm.

If you are familiar with using zapier build with the flag --skip-npm-install, this flag has been renamed to --skip-dep-install, but will continue to still work as an alias. In the future, we will remove the --skip-npm-install flag.

cli

  • 💅 CLI build respects the integration's package manager (#1216)

core

None!

schema

None!

misc

  • 🔨 Bump tmp from 0.2.4 to 0.2.5 (#1207)
  • 🔨 Bump form-data from 4.0.4 to 4.0.5 (#1208)