Skip to content

Revert Release 21.0.0#939

Merged
georgewrmarshall merged 1 commit into
mainfrom
revert-release-21.0.0
Feb 25, 2026
Merged

Revert Release 21.0.0#939
georgewrmarshall merged 1 commit into
mainfrom
revert-release-21.0.0

Conversation

@georgewrmarshall

@georgewrmarshall georgewrmarshall commented Feb 25, 2026

Copy link
Copy Markdown
Contributor

Summary

Reverts Release 21.0.0 (#938) to redo the release without peer dependency updates that caused the release workflow to fail.

Issue

The release workflow failed with:

YN0028: The lockfile would have been modified by this install, which is explicitly forbidden.

This was caused by peer dependency updates in @metamask/design-system-react:

  • @metamask/design-system-tailwind-preset: ^0.6.0 → ^0.6.1
  • @metamask/design-tokens: ^8.1.0 → ^8.2.0

Resolution

This PR reverts the release merge to allow resubmission without the peer dependency changes. The new release will include:

  • ✅ Version bumps
  • ✅ Changelog updates
  • ❌ No peer dependency changes (to avoid yarn.lock modifications in CI)

Next Steps

After this revert is merged, a new Release 21.0.0 PR will be created with only the necessary version and changelog updates.

🤖 Generated with Claude Code

Co-Authored-By: Claude noreply@anthropic.com


Note

Low Risk
Release bookkeeping-only changes (versions/changelogs/peer dependency ranges) with no runtime code modifications; main risk is publishing/versioning confusion if merged out of sequence.

Overview
Reverts the prior 21.0.0 release metadata by rolling the monorepo version back to 20.0.0 and downgrading package versions for @metamask/design-system-react (0.9.00.8.0), @metamask/design-system-react-native (0.8.00.7.0), and @metamask/design-system-shared (0.2.00.1.3).

Removes the newly-added Unreleased changelog sections/compare links for those versions and reverts @metamask/design-system-react peer dependency bumps (@metamask/design-system-tailwind-preset and @metamask/design-tokens) back to their previous ranges.

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

This reverts commit adee3a9 to redo the release without peer
dependency updates that caused the release workflow to fail.

The release will be resubmitted with:
- Version bumps
- Changelog updates
- No peer dependency changes to avoid yarn.lock modifications

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude <noreply@anthropic.com>
@georgewrmarshall georgewrmarshall requested a review from a team as a code owner February 25, 2026 21:08
@georgewrmarshall georgewrmarshall enabled auto-merge (squash) February 25, 2026 21:09
@github-actions

Copy link
Copy Markdown
Contributor

📖 Storybook Preview

@georgewrmarshall georgewrmarshall merged commit dfdbf64 into main Feb 25, 2026
43 checks passed
@georgewrmarshall georgewrmarshall deleted the revert-release-21.0.0 branch February 25, 2026 21:33
georgewrmarshall added a commit that referenced this pull request Mar 3, 2026
## Summary

Reverts Release 21.0.0 (#938) to redo the release without peer
dependency updates that caused the release workflow to fail.

## Issue

The release workflow failed with:
```
YN0028: The lockfile would have been modified by this install, which is explicitly forbidden.
```

This was caused by peer dependency updates in
`@metamask/design-system-react`:
- `@metamask/design-system-tailwind-preset`: ^0.6.0 → ^0.6.1
- `@metamask/design-tokens`: ^8.1.0 → ^8.2.0

## Resolution

This PR reverts the release merge to allow resubmission without the peer
dependency changes. The new release will include:
- ✅ Version bumps
- ✅ Changelog updates  
- ❌ No peer dependency changes (to avoid yarn.lock modifications in CI)

## Next Steps

After this revert is merged, a new Release 21.0.0 PR will be created
with only the necessary version and changelog updates.

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude <noreply@anthropic.com>

Co-authored-by: Claude <noreply@anthropic.com>
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