Skip to content

Conversation

@smol-ninja
Copy link
Member

Do we need a new npm release (3.0.2)? IMO thats not necessary since its the release page that people often look for changelogs.

@smol-ninja
Copy link
Member Author

I also had to pin foundry version to v1.3.6 because the new stable release has been breaking forge fmt (atleast). You can run foundryup -i v1.3.6 locally in case you accidentally upgrade it on your machine.

@PaulRBerg
Copy link
Member

PaulRBerg commented Oct 15, 2025

Do we need a new npm release (3.0.2)?

No

I also had to pin foundry version to v1.3.6

foundry-rs/foundry#5133

Copy link
Member

@PaulRBerg PaulRBerg left a comment

Choose a reason for hiding this comment

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

LGTM, merging

@PaulRBerg PaulRBerg merged commit 0c3ea98 into main Oct 15, 2025
10 checks passed
@PaulRBerg PaulRBerg deleted the docs/changelog branch October 15, 2025 09:40
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.

3 participants