Releases
Versioned Deployment
Docs are deployed automatically when a release tag matching playwright-drupal-* is pushed (e.g. playwright-drupal-1.5.1). The GitHub Actions workflow strips the playwright-drupal- prefix and runs mike deploy --push --update-aliases 1.5.1 latest, committing versioned docs to the gh-pages branch. Deployed docs are available at https://lullabot.github.io/playwright-drupal/1.5.1/ and https://lullabot.github.io/playwright-drupal/latest/.
One-Time GitHub Pages Setup
Before the first versioned deployment, change the GitHub Pages source from "GitHub Actions" to "Deploy from a branch":
- Go to Settings → Pages
- Under Source, select Deploy from a branch
- Set branch to
gh-pagesand folder to/ (root) - Save
The gh-pages branch is created automatically by mike on first deployment.
Publishing a One-Off Alpha Release
Stable releases are handled automatically by release-please from main. To publish a one-off prerelease (e.g. to let someone test an unreleased change) without disturbing the latest dist-tag, publish manually from your workstation.
Prerequisites:
- Push access to the
@lullabot/playwright-drupalnpm package. - A granular access token from npmjs.com with publish permission on the package.
1. Authenticate npm with your token:
This writes the token to ~/.npmrc. npm login is now interactive/browser-based and won't accept a token directly, so setting _authToken is the standard path for automation-style tokens.
2. Check out a clean main and bump the version locally:
Do not commit or push the version bump — release-please manages versions in the repo. The bump only needs to exist in the working copy for npm publish to read.
3. Publish under the alpha dist-tag:
prepack runs npm run build automatically, so no separate build step is required. The --tag alpha flag is critical: without it, the prerelease would replace latest and become the default install.
4. Verify and clean up:
Consumers install the prerelease with npm install @lullabot/playwright-drupal@alpha.