docs(webkit): refresh GOVERNANCE_IMPLEMENTATION for release-please and the current CI pipeline - #820
Merged
Conversation
…d the current CI pipeline The doc (shipped to npm via files: docs) still described the semantic-release/.releaserc mechanism deleted by #798 and an 8-job CI. Rewritten against the current tree: publish-workflow d.ts generation, 12-job governance pipeline with main-only triggers, plain pnpm audit, current scripts/hooks/config locations, and a historical release-automation migration note.
paulo-sobrinho-azion
approved these changes
Jul 28, 2026
gdsantana
approved these changes
Jul 28, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Refreshes
packages/webkit/docs/GOVERNANCE_IMPLEMENTATION.md— the governance-tooling rationale doc that ships to npm (package.json#filesincludesdocs). It was a 2026-04 snapshot, resurrected by #768 after #741 deleted it, and had drifted from the tree on several load-bearing claims. Every statement in the refresh was verified against the current configs/workflows.What was stale → what it says now:
.d.ts-at-publish mechanism — claimed.releasercprepareCmd(semantic-release, deleted by ci: replace semantic-release with release-please (Release PR model) #798). Now: the publish workflow (package-webkit.yml) runsvue-tsc --declaration --emitDeclarationOnlyimmediately beforenpm publish, triggered by release-please'srelease: published.mainanddev. Now: the current 12-jobgovernance.yml(addslint-canary,smoke,tests×4 shards,visual×4 shards, each with a rationale subsection),main-only triggers, PR concurrency cancellation.pnpm audit --audit-level=high. Now: plainpnpm audit(any severity fails; accepted risks live aspnpm-workspace.yamloverrides).packages/webkit/eslint.config.jsis a one-line re-export) with hand-picked Vue rules rather than a spread preset; stylelint is the root.stylelintrc.jsononly; TS strictness is split acrosstsconfig.base.json+ the webkit tsconfig (which also drives publish-time declaration emit).webkit:*delegation scripts, the governance-gate scripts (catalog:check,size,pack:check,test:gate,authoring,doc-standards,smoke:consume), the Vitest browser-mode test scripts, and thecommit-msg/commitlint hook. The old "skip hooks with--no-verifyin emergencies" tip is replaced with the git-workflow prohibition.Closes #819 (the "refresh or delete" decision → refresh).
Notes
docstype — no release on its own). No new dependencies. Not breaking..releaserc-mention purge): this PR resolves theGOVERNANCE_IMPLEMENTATION.mdrow. The refreshed Migration Notes deliberately keep one past-tense mention of semantic-release/.releasercfor historical context — the same category asrelease-types.md's don't-do-this notes — so docs: purge dangling .releaserc / semantic-release mentions (release-please follow-up) #818's acceptance grep gains one intentional hit.