Release/702.0.0

[MoMannn]

Explanation

Releases 0.7.0 version of @metamask/gator-permissions-controller.

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

Publishes @metamask/gator-permissions-controller 0.7.0, bumps monorepo to 702.0.0, and updates @metamask/signature-controller to depend on it.

• Release:
  • Bump root version to 702.0.0.
  • Publish @metamask/gator-permissions-controller@0.7.0:
    • Changelog: refresh permissions map after revocation; add submitDirectRevocation; move certain peer deps to direct deps.
    • Update changelog links and package.json version.
• Consumers:
  • Update @metamask/signature-controller dependency on @metamask/gator-permissions-controller to ^0.7.0.

^{Written by Cursor Bugbot for commit ce9d618. This will update automatically on new commits. Configure here.}

[mikesposito]

We are already using this package in both clients. Did you consider releasing a new stable version? i.e. 1.0.0?

[MoMannn]

There are still some breaking changes possible. I'm guessing a stable release will by start of next year when we move from flask build.

[mikesposito]

We can always release more breaking changes by releasing additional major versions. I'm pointing this out because for versions <1.0.0, every minor version can include breaking changes - which can make it harder when managing updates in clients.

Your call though.

[MoMannn]

Lets leave it like for now.