Skip to content

Conversation

@vados-cosmonic
Copy link
Contributor

No description provided.

@tschneidereit
Copy link
Member

Should we wait for a release including bytecodealliance/wizer#136?

@vados-cosmonic
Copy link
Contributor Author

We certainly could -- are you able to ensure a release of wizer, @tschneidereit ? I'm not a maintainer on that project so not sure how freqeuently it will get released. We've been behind on versions for a while though so I don't see anything wrong with updating now and later when a new version is released.

@tschneidereit
Copy link
Member

We can get a Wizer release out pretty quickly, yes

@vados-cosmonic
Copy link
Contributor Author

OK, in that case let's get that released and then I'll update this PR to go to the new version!

@vados-cosmonic vados-cosmonic changed the title chore(deps): update wizer to ^9.0.0 chore(deps): update wizer to ^10.0.0 Aug 28, 2025
@vados-cosmonic vados-cosmonic force-pushed the chore(deps)=update-wizer branch from d475f04 to 8576f56 Compare August 28, 2025 09:39
@vados-cosmonic
Copy link
Contributor Author

Hey @tschneidereit this should be ready to go with the upstream wizer 10.0.0 release

Copy link
Member

@tschneidereit tschneidereit left a comment

Choose a reason for hiding this comment

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

🥳

@vados-cosmonic vados-cosmonic merged commit 0dd34de into bytecodealliance:main Aug 28, 2025
16 checks passed
@vados-cosmonic vados-cosmonic deleted the chore(deps)=update-wizer branch August 28, 2025 11:35
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