Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Pin wasm #787

Open
wants to merge 2 commits into
base: master
Choose a base branch
from
Open

Pin wasm #787

wants to merge 2 commits into from

Conversation

Kixunil
Copy link
Collaborator

@Kixunil Kixunil commented Mar 21, 2025

An attempt to solve the wasm CI issue. (But even if unsuccessful, this is still useful.)

Kixunil added 2 commits March 21, 2025 08:45
So far testing was was done unpinned however that risked randomly
breaking builds whenever a dependency changes by accident. There was a
note explicitly acknowledging lack of pinning but with no explanation
why that was the case. So it might be because the author didn't want to
bother and pinning can be implemented.
As with anything else, downloading a random version from crates risks
breaking CI. This change decreases the risk by pinning the crate but so
far makes *no attempts* at trying to update it in a cron job. It would
be definitely a nice addition later.
@apoelstra
Copy link
Member

Reminder that rustwasm/wasm-pack#1316 means that no matter how much you try to pin tooling, wasm-pack itself will still pull random broken stuff from the Internet and you can't tell it to stop.

@Kixunil
Copy link
Collaborator Author

Kixunil commented Mar 21, 2025

@apoelstra no, read the actual code. It does pass arguments (such as --locked) in case of wasm-pack build but not in case of wasm-pack install and we do use wasm-pack build here. Also cargo doesn't have ridiculous default in case of cargo build anyway, so passing --locked in that case is not needed.

(Of course, if anyone is running wasm-pack install, God help them, but thankfully it's not a problem in this repo nor mine.)

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