Skip to content

Conversation

@tuna1207
Copy link
Member

@tuna1207 tuna1207 commented Nov 13, 2025

Explanation

Minor releases of shield-controller

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, highlighting breaking changes as necessary
  • I've prepared draft pull requests for clients and consumer packages to resolve any breaking changes

Note

Publishes shield-controller 2.1.0 adding latency metrics and updates monorepo version to 676.0.0.

  • Packages:
    • @metamask/shield-controller v2.1.0
      • Added latency metrics in Shield coverage responses.
      • Updated changelog entries and links.
    • Monorepo package.json: version bumped to 676.0.0.

Written by Cursor Bugbot for commit 4d83b16. This will update automatically on new commits. Configure here.

@tuna1207 tuna1207 added team-web3auth area-shield Transaction Shield labels Nov 13, 2025
@tuna1207 tuna1207 marked this pull request as ready for review November 13, 2025 09:07
@tuna1207 tuna1207 requested review from a team as code owners November 13, 2025 09:07
@chaitanyapotti chaitanyapotti enabled auto-merge (squash) November 13, 2025 09:08
@chaitanyapotti chaitanyapotti merged commit 9b84201 into main Nov 13, 2025
282 checks passed
@chaitanyapotti chaitanyapotti deleted the release/676.0.0 branch November 13, 2025 09:10
Prithpal-Sooriya added a commit that referenced this pull request Nov 13, 2025
Prithpal-Sooriya added a commit that referenced this pull request Nov 13, 2025
This reverts commit 9b84201.

## Explanation

This release used an invalid commit name (Relase/676.0.0) so the publish
CI script did not run.
Reverting and will add this back as a fast follow.

<!--
Thanks for your contribution! Take a moment to answer these questions so
that reviewers have the information they need to properly understand
your changes:

* What is the current state of things and why does it need to change?
* What is the solution your changes offer and how does it work?
* Are there any changes whose purpose might not obvious to those
unfamiliar with the domain?
* If your primary goal was to update one package but you found you had
to update another one along the way, why did you do so?
* If you had to upgrade a dependency, why did you do so?
-->

## References

<!--
Are there any issues that this pull request is tied to?
Are there other links that reviewers should consult to understand these
changes better?
Are there client or consumer pull requests to adopt any breaking
changes?

For example:

* Fixes #12345
* Related to #67890
-->

## Checklist

- [x] I've updated the test suite for new or updated code as appropriate
- [x] I've updated documentation (JSDoc, Markdown, etc.) for new or
updated code as appropriate
- [x] I've communicated my changes to consumers by [updating changelogs
for packages I've
changed](https://github.com/MetaMask/core/tree/main/docs/contributing.md#updating-changelogs),
highlighting breaking changes as necessary
- [x] I've prepared draft pull requests for clients and consumer
packages to resolve any breaking changes

<!-- CURSOR_SUMMARY -->
---

> [!NOTE]
> Rolls back release versions (core to 675.0.0, shield-controller to
2.0.0) and updates shield-controller changelog accordingly.
> 
> - **Versions**:
>   - Roll back root `package.json` from `676.0.0` to `675.0.0`.
> - Roll back `packages/shield-controller/package.json` from `2.1.0` to
`2.0.0`.
> - **Changelog (`packages/shield-controller/CHANGELOG.md`)**:
>   - Remove `2.1.0` section; keep its entry under `Unreleased`.
>   - Update compare links to reference `2.0.0` and drop `2.1.0` link.
> 
> <sup>Written by [Cursor
Bugbot](https://cursor.com/dashboard?tab=bugbot) for commit
b9b1b52. This will update automatically
on new commits. Configure
[here](https://cursor.com/dashboard?tab=bugbot).</sup>
<!-- /CURSOR_SUMMARY -->
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants