Summary
Upstream Gutenberg changes in @wordpress/blocks, @wordpress/data, and adjacent TypeScript surfaces can quietly invalidate assumptions in wp-typia.
We should introduce a recurring watch so we do not only notice relevant upstream changes opportunistically.
Goals
Establish a lightweight recurring review of Gutenberg TypeScript changes that matter to wp-typia.
Make the output actionable instead of just collecting links.
Acceptance Criteria
Define the cadence for the upstream watch (weekly or biweekly).
Decide the implementation path: scheduled GitHub Action, external automation, or another repeatable mechanism.
Track relevant upstream PRs/issues affecting:
Block registration types (@wordpress/blocks)
Block editor component types (@wordpress/block-editor)
Data store types (@wordpress/data)
Generated-project dependency compatibility
Track @wordpress/blocks version bumps and evaluate whether scaffolded template dependency pins (@wordpress/blocks: "^15.2.0") should be updated to stay aligned with the locally owned type facade from Own block registration TypeScript surface in @wp-typia/block-types #279
Capture the outcome in a durable format (issue, issue comment, summary artifact, or equivalent).
Document ownership and the expected follow-up path when action is needed.
Seed References
Notes
A useful first version can be read-only and triage-oriented as long as it makes necessary follow-up visible in this repo.
Summary
Upstream Gutenberg changes in
@wordpress/blocks,@wordpress/data, and adjacent TypeScript surfaces can quietly invalidate assumptions inwp-typia.We should introduce a recurring watch so we do not only notice relevant upstream changes opportunistically.
Goals
wp-typia.Acceptance Criteria
@wordpress/blocks)@wordpress/block-editor)@wordpress/data)@wordpress/blocksversion bumps and evaluate whether scaffolded template dependency pins (@wordpress/blocks: "^15.2.0") should be updated to stay aligned with the locally owned type facade from Own block registration TypeScript surface in @wp-typia/block-types #279.Seed References
Notes
A useful first version can be read-only and triage-oriented as long as it makes necessary follow-up visible in this repo.