Search by

caffeinalab / wp-vercel-builds

caffeina

There is no license information available for the latest version (3.3.0) of this package.

Are we there yet?

Package info

github.com/caffeinalab/wp-vercel-builds

Type:wordpress-plugin

pkg:composer/caffeinalab/wp-vercel-builds

Statistics

Installs: 14

Dependents: 0

Suggesters: 0

Stars: 1

Open Issues: 0

3.3.0 2026-11-16 20:41 UTC

This package is not auto-updated.

Last update: 2026-11-17 19:08:20 UTC


README


Logo

Are we there yet?

Install

  1. Run composer require "caffeinalab/wp-vercel-builds". Until the package is on Packagist, first add { "type": "vcs", "url": "https://github.com/caffeinalab/wp-vercel-builds" } to your composer.json repositories key
  2. Configure a Vercel webhook pointing to https://yoursite.com/wp-json/builds/update
  3. Define a constant VERCEL_SIGNATURE_KEY with the Vercel key created in Team > Settings > Webhooks
  4. Define a constant VERCEL_API_BEARER_TOKEN with the Vercel token created in Account > Tokens
  5. Activate the plugin and check out your dashboard tab

Hooks

  1. vercel_builds_capability, to set the capability to view the build dashboard. The badge will be viewable to anyone. default: manage_options
  2. vercel_builds_log_tag, to set the tag used to identify which logs to display in the admin dashboard. default: [build_error]
  3. vercel_builds_log_stream, to set the logstream used on Vercel. default: stderr

If you have multiple Vercel projects

Vercel currently has a limit of 20 configurable webhooks, which may not be enough for all your projects and environments. You can work around it by setting up a Lambda function on AWS (or equivalent) as the general webhook receiver for all your projects and proxy the request to the correct server.

A lambda.mjs file is included in the repo as an example of a possible implementation, but don't forget to:

  1. Configure the environment variable VERCEL_SIGNATURE with the value provided by Vercel
  2. Review the configuration array with all your projects and environments

Contents

  1. Polling on badge to quickly know the state of the latest build
  2. Can view builds, with their status, date and duration
  3. Can view custom build logs in case the build failed
  4. Customer-side debugging is possible by reviewing previous versions from the url
  5. The commit SHA is included to help spot any regression bug

Known Issues

  • Due to the absence of a queued deployment event, the following problems arise:
    1. Building status from a queued deployment may be overridden by the previous build's result until the queued deployment is completed
    2. A deployment which was created under the queued status will display its duration equal to the time in the queue + the effective build time

Roadmap

  1. Add a button to allow the customer to pin a previous deployment as production
  2. Someday, refactor for better code