From 9e88bcd64ec421cff63739aa5c86c4f25b57a0a8 Mon Sep 17 00:00:00 2001 From: "Tommy D. Rossi" Date: Thu, 5 Feb 2026 22:26:47 +0100 Subject: [PATCH] agents --- AGENTS.md | 2 ++ PLAYWRITER_AGENTS.md | 2 ++ 2 files changed, 4 insertions(+) diff --git a/AGENTS.md b/AGENTS.md index 5ff7ba0..b981eb5 100644 --- a/AGENTS.md +++ b/AGENTS.md @@ -187,6 +187,8 @@ ignore everything that is outside of playwright/packages/playwright-core in the for our playwright fork notice the types.d.ts are generated from markdown files, so adding new APIs require updating those and not the actual source files unfortunately +EVERY update to playwright code that changes its api or behaviour MUST be followed by a bump in version and update in playwright-core/CHANGELOG.md file. on release of the playwriter package then the playwright-core package must be released first, always using `pnpm publish` command. + ### submodule setup the playwright submodule should always stay on branch `playwriter`. never switch to main or other branches. diff --git a/PLAYWRITER_AGENTS.md b/PLAYWRITER_AGENTS.md index 6a472d9..2e02b31 100644 --- a/PLAYWRITER_AGENTS.md +++ b/PLAYWRITER_AGENTS.md @@ -185,6 +185,8 @@ ignore everything that is outside of playwright/packages/playwright-core in the for our playwright fork notice the types.d.ts are generated from markdown files, so adding new APIs require updating those and not the actual source files unfortunately +EVERY update to playwright code that changes its api or behaviour MUST be followed by a bump in version and update in playwright-core/CHANGELOG.md file. on release of the playwriter package then the playwright-core package must be released first, always using `pnpm publish` command. + ### submodule setup the playwright submodule should always stay on branch `playwriter`. never switch to main or other branches.