Skip to content

chore: make Assets the sole codeowner of core-backend - #10250

Open
Kriys94 wants to merge 1 commit into
mainfrom
chore/core-backend-assets-codeowners
Open

Kriys94 wants to merge 1 commit into
mainfrom
chore/core-backend-assets-codeowners

Conversation

@Kriys94

@Kriys94 Kriys94 commented Sep 15, 2026

Copy link
Copy Markdown
Contributor

Explanation

References

Checklist

  • I've updated the test suite for new or updated code as appropriate
  • I've updated documentation (JSDoc, Markdown, etc.) for new or updated code as appropriate
  • I've communicated my changes to consumers by updating changelogs for packages I've changed
  • I've introduced breaking changes in this PR and have prepared draft pull requests for clients and consumer packages to resolve them

Note

Low Risk
Metadata-only ownership changes; no application or runtime code is modified.

Overview
core-backend is no longer jointly owned with Core Platform for day-to-day package changes. Ownership is consolidated under the Assets team in the same places other packages declare owners.

Updates codeowners.ts so core-backend lists only @MetaMask/metamask-assets, moves it from Joint team ownership into the Assets Team section, and regenerates .github/CODEOWNERS to match (including listing Assets first on release metadata paths). teams.json now maps metamask/core-backend to team-assets only, dropping team-core-platform.

Core Platform remains a co-owner on core-backend release files (package.json, changelogs, tsconfig, typedoc) via the existing “Package Release related” rules that always add that team.

Reviewed by Cursor Bugbot for commit c107d81. Bugbot is set up for automated code reviews on this repo. Configure here.

@Kriys94
Kriys94 marked this pull request as ready for review September 15, 2026 14:33
@Kriys94
Kriys94 requested a review from a team as a code owner September 15, 2026 14:33
@Kriys94
Kriys94 deployed to default-branch September 15, 2026 14:33 — with GitHub Actions Active
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants