Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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
Add prebuilt mozjs archive CI #454
Add prebuilt mozjs archive CI #454
Changes from 13 commits
6aef1eb
ad84256
c5bf7c2
d3e69ac
7c1b25a
a29f3a0
83793f4
d150367
0737a22
0b3f0b5
9790c30
2e0efed
3c94562
a8370a3
2076043
d84ff44
3800976
dee33e6
72f6675
94afc62
713e84e
495e7e5
b154d0a
3241ac0
8d7ed20
fb6869e
a58bfe9
21f9113
3809e36
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This could be problematic, if we have two updates in a day (it happens sometimes), so using commit hash might be better, but I don't know how we could bake this info in for #450. Can we get dependency commit hash using cargo without baking it in.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Rusty_v8 does this using
CARGO_PKG_VERSION
:https://github.com/denoland/rusty_v8/blob/9dd629e1c3c50fbbe70435ed50f6f09e9b69d7bb/build.rs#L320
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
CARGO_PKG_VERSION
seems like a better approach. I also hope this repo can provide version release again.I'll update release job to use mozjs_sys's
CARGO_PKG_VERSION
, and it will skip the release if the version is already exist.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think
CARGO_PKG_VERSION
is actually the only way to go and because we moved all .c* files to mozjs-sys, the only thing that needs versions bumps ismozjs-sys
when there are any C/C++ file changes.It would be nice to make CI check for this too, but I think this can be done as a followup if (ever) needed. For now I think it would be enough if we test always latest release on push to main (instead of testing release only if it's new).