You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Zapier: Build, validate and upload a version from CI on a tag, and promote by hand #48
The CI workflow (.github/workflows/ci.yml) lints, builds and tests the Zapier app on each push and pull request. No workflow uploads a Zapier version. So nothing ties a live Zapier version to a commit, a tag or a CI run.
The n8n node already has a release workflow. .github/workflows/publish-n8n.yml runs on a tag n8n-v<version>. It checks that the tagged commit is on master and that the tag matches the package version, then it publishes.
What a developer can do today
Run yarn lint, yarn build and yarn test locally.
Run zapier validate and zapier push from a local machine with access to the Zapier integration.
Proposed change
Add .github/workflows/release-zapier.yml, in the same shape as publish-n8n.yml:
Run on a tag zapier-v<version>, for example zapier-v1.4.0.
Fail if the tagged commit is not on master.
Fail if the tag does not match version in the root package.json.
Run yarn install --frozen-lockfile, yarn lint, yarn build and yarn test.
Run zapier validate with a pinned version of zapier-platform-cli.
Run zapier push with a deploy key from a protected GitHub environment, for example the secret ZAPIER_DEPLOY_KEY.
Stop there. A person tests the new version in the Zapier editor, then runs zapier promote.
Document the release steps in CONTRIBUTING.md, next to the n8n steps.
Done when
A tag push uploads the version, and the run log shows zapier validate with no errors.
A tag that does not match package.json, or that is not on master, fails before the upload.
The workflow never runs zapier promote or zapier migrate.
Only the protected environment holds the deploy key.
CONTRIBUTING.md lists the release steps, and CHANGELOG.md has an entry for each released version.
#51 moved the Zapier app from zapier-platform-core 17.4.0 to 19.3.0. The built definition is the same, except for platformVersion. The next upload is the first one on platform 19, so two things need a check before it:
Use zapier-platform-cli 19 for the upload, and confirm its command name. The release steps in the README still say zapier push.
Platform 18 and later run on Node 22. Run the test suite on Node 22 before the upload.
The release workflow of this issue is a good place to pin both.
Activity
johnxie commentedon Nov 19, 2026
A note for the first release after #51.
#51 moved the Zapier app from
zapier-platform-core17.4.0 to 19.3.0. The built definition is the same, except forplatformVersion. The next upload is the first one on platform 19, so two things need a check before it:zapier-platform-cli19 for the upload, and confirm its command name. The release steps in the README still sayzapier push.The release workflow of this issue is a good place to pin both.