Yury Semikhatsky
24e68fa41d
devops: do not use npm token ( #1076 )
...
https://github.com/microsoft/playwright/issues/37495
2025-09-24 15:22:10 -07:00
Yury Semikhatsky
e50322731b
devops: merge canary publishing workflow into publish.yml ( #1075 )
...
Reference https://github.com/microsoft/playwright/issues/37495
2025-09-24 14:54:43 -07:00
Max Schmitt
4a7be8de75
devops: migrate to OIDC NPM publishing ( #1068 )
...
https://github.com/microsoft/playwright/issues/37495
2025-09-22 16:19:16 +02:00
Max Schmitt
38f0222d0e
devops: fix publishing ( #1021 )
...
Fixes
https://github.com/microsoft/playwright-mcp/actions/runs/17521002811/job/49764720465
Fixes https://github.com/microsoft/playwright-mcp/issues/1014
2025-09-08 16:43:04 +02:00
Yury Semikhatsky
6171abd277
devops: get extension version from package.json, not tag ( #1000 )
2025-09-04 14:21:14 -07:00
Yury Semikhatsky
92554abfd1
devops: extension publishing job ( #888 )
2025-08-15 10:25:46 -07:00
Max Schmitt
f5b68dc590
devops(docker): enhance Docker image publishing with ORAS end-of-life tagging ( #641 )
...
This tags the images we publish as EOL immediately in order to get
excluded from the image scanning. Like we do upstream in
microsoft/playwright.
2025-07-07 23:08:12 +02:00
Max Schmitt
950d0d1d34
devops: fix Docker publishing ( #369 )
2025-05-07 11:46:33 +02:00
Max Schmitt
35e6c49d7c
devops: publish Docker image to :latest as well ( #365 )
...
We don't do that for normal Playwright because we expect the user to
mount/add/copy their own Playwright folder and there the version has to
match. In this case publishing to `:latest` seems fine since its a
isolated product.
2025-05-07 11:14:05 +02:00
Max Schmitt
23a2e5fee7
devops: add Docker publishing ( #356 )
2025-05-06 23:14:41 +02:00
Yury Semikhatsky
0d6bb2f547
devops: add bots for other browsers/platforms ( #174 )
2025-04-15 13:16:56 -07:00
Pavel Feldman
6891a525b3
chore: add npx install step to the publish workflow ( #178 )
2025-04-14 20:09:38 -07:00
Max Schmitt
128e75b9f4
devops: fix npm publishing due to proverance ( #112 )
...
Like
[upstream](3ad5c2731a/.github/workflows/publish_release_npm.yml (L15)https://docs.npmjs.com/generating-provenance-statements#example-github-actions-workflow ).
2025-04-02 00:37:13 +02:00
Max Schmitt
88fbf50841
devops: use --provenance when publishing to NPM ( #83 )
...
Similar to how we do it upstream:
e2c8163b14/utils/publish_all_packages.sh (L97)https://docs.npmjs.com/generating-provenance-statements
2025-03-29 19:17:54 +01:00
Pavel Feldman
af522dca5f
chore: lint and test prior to publishing
2025-03-28 13:43:44 -07:00
Max Schmitt
878b46588b
devops: add NPM publishing ( #4 )
...
Requires the `NPM_TOKEN` secret to be set.
2025-03-27 18:08:43 +01:00
