From 22a11a0dc60a45977eb704047ae02e3f36f61947 Mon Sep 17 00:00:00 2001 From: adrians5j Date: Thu, 22 Oct 2026 12:59:05 +0200 Subject: [PATCH] fix(changelog): treat public API refactors as user-facing in triage The 6.6.0 run marked refactor PRs that change what project code imports or implements as internal, e.g. the background task handler shape (#5684 and its follow-ups), removal of the ContextPlugin class (#5428) and the @webiny/di 2.0 upgrade (#5969). Both prompts now say such changes are user-facing, and breaking ones go under Breaking Changes. Co-Authored-By: Claude Opus 5.5 --- scripts/generate-changelog.ts | 11 +++++++++++ 1 file changed, 11 insertions(+) diff --git a/scripts/generate-changelog.ts b/scripts/generate-changelog.ts index 903eae172..a95b9b6f8 100644 --- a/scripts/generate-changelog.ts +++ b/scripts/generate-changelog.ts @@ -258,6 +258,9 @@ a developer-facing changelog in MDX format from a list of merged pull requests. that a Webiny user never runs: CI workflows, the monorepo build, package publishing, release scripts, E2E and test infrastructure. If a PR title starts with \`chore\`, \`ci\`, \`test\`, \`deps\`, or \`refactor\` and the body contains no user-facing changes, skip it entirely. +- A refactor that changes an API developers import or implement (renamed or removed exports, + abstractions or packages, changed signatures, new task or handler shapes) is user-facing. Include + it, under \`## Breaking Changes\` when existing project code has to change. ## Tone and style @@ -432,6 +435,14 @@ Report two things through the \`report_triage\` tool. Admin app or the SDKs is user-facing even when it sounds like tooling. When in doubt, it is user-facing. + Webiny users are developers who write code against Webiny's packages: extensions, event + handlers, use cases, background tasks, GraphQL schema, DI implementations. A PR is user-facing, + whatever its commit type (\`refactor\` included), when it changes something that code imports, + implements or receives: an export, class, abstraction or package that is renamed or removed, a + method signature, the shape of a task, handler or context, a dependency they build on (such as + \`@webiny/di\`), or a new extension point. Breaking changes are always user-facing. A refactor is + internal only when everything it touches stays inside Webiny's own packages. + 2. Follow-up PRs: a PR that fixes, polishes or completes something another PR in this same release introduced. Because the release is not out yet, nobody ever ran into the problem the follow-up fixes, so it should not get its own changelog entry. Report the PR whose work it finishes as its