Skip to content

fix: correct initial version of @metamask/network-connection-banner-controller - #9436

Merged
cryptodev-2s merged 1 commit into
mainfrom
fix/network-connection-banner-controller-initial-version
Jul 8, 2026
Merged

fix: correct initial version of @metamask/network-connection-banner-controller#9436
cryptodev-2s merged 1 commit into
mainfrom
fix/network-connection-banner-controller-initial-version

Conversation

@cryptodev-2s

@cryptodev-2s cryptodev-2s commented Jul 8, 2026

Copy link
Copy Markdown
Contributor

Explanation

The package was merged in #9041 with an initial version of 0.1.0. New packages should start at 0.0.0 (that's what the create-package template sets). This bumps it back down so the first release goes out correctly.

References

Follow up to #9041

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 highlighted breaking changes using the "BREAKING" category above as appropriate
  • I've prepared draft pull requests for cross repository changes as appropriate

Note

Low Risk
Only package.json version metadata changes; no runtime or API behavior is affected.

Overview
Aligns @metamask/network-connection-banner-controller with the monorepo convention for new packages by changing version in package.json from 0.1.0 to 0.0.0, matching the create-package template and other unreleased packages.

This is a metadata-only fix so the first automated release can version the package correctly after it was introduced with the wrong starting version in #9041.

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

@cryptodev-2s
cryptodev-2s requested a review from a team as a code owner July 8, 2026 21:41
@cryptodev-2s cryptodev-2s self-assigned this Jul 8, 2026
@cryptodev-2s
cryptodev-2s requested a review from mcmire July 8, 2026 21:42
@cryptodev-2s
cryptodev-2s enabled auto-merge July 8, 2026 21:42

@mcmire mcmire left a comment

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM.

…to 0.0.0

New packages start at 0.0.0 per the create-package template. #9041 shipped it at 0.1.0 by mistake.
@cryptodev-2s
cryptodev-2s force-pushed the fix/network-connection-banner-controller-initial-version branch from 095ed74 to 08e6c20 Compare July 8, 2026 22:12
@cryptodev-2s
cryptodev-2s added this pull request to the merge queue Jul 8, 2026
Merged via the queue into main with commit 0b0e1b7 Jul 8, 2026
421 checks passed
@cryptodev-2s
cryptodev-2s deleted the fix/network-connection-banner-controller-initial-version branch July 8, 2026 22:18
cryptodev-2s added a commit that referenced this pull request Jul 8, 2026
…ontroller (#9436)

## Explanation

The package was merged in #9041 with an initial version of `0.1.0`. New
packages should start at `0.0.0` (that's what the `create-package`
template sets). This bumps it back down so the first release goes out
correctly.

## References

Follow up to #9041

## 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 highlighted breaking changes using the "BREAKING" category
above as appropriate
- [x] I've prepared draft pull requests for cross repository changes as
appropriate

<!-- CURSOR_SUMMARY -->
---

> [!NOTE]
> **Low Risk**
> Only `package.json` version metadata changes; no runtime or API
behavior is affected.
> 
> **Overview**
> Aligns `@metamask/network-connection-banner-controller` with the
monorepo convention for new packages by changing **`version`** in
`package.json` from **`0.1.0`** to **`0.0.0`**, matching the
`create-package` template and other unreleased packages.
> 
> This is a metadata-only fix so the first automated release can version
the package correctly after it was introduced with the wrong starting
version in #9041.
> 
> <sup>Reviewed by [Cursor Bugbot](https://cursor.com/bugbot) for commit
08e6c20. Bugbot is set up for automated
code reviews on this repo. Configure
[here](https://www.cursor.com/dashboard/bugbot).</sup>
<!-- /CURSOR_SUMMARY -->
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