Skip to content

Security bump SpiderMonkey to 140.10#744

Closed
sagudev wants to merge 4 commits into
servo:mainfrom
servo-bot:security-bump-esr140
Closed

Security bump SpiderMonkey to 140.10#744
sagudev wants to merge 4 commits into
servo:mainfrom
servo-bot:security-bump-esr140

Conversation

@sagudev
Copy link
Copy Markdown
Member

@sagudev sagudev commented Apr 29, 2026

Bump SpiderMonkey to 140.10 (changeset: a24e9e115e02794f72dab9ef6081244403b0183a)

Signed-off-by: servo-bot <ghbot+mozjs-sm-bump@servo.org>
Signed-off-by: servo-bot <ghbot+mozjs-sm-bump@servo.org>
Signed-off-by: servo-bot <ghbot+mozjs-sm-bump@servo.org>
Signed-off-by: servo-bot <ghbot+mozjs-sm-bump@servo.org>
@servo-bot servo-bot force-pushed the security-bump-esr140 branch from 4c79d9c to 037fc9d Compare April 29, 2026 04:41
Comment thread mozjs-sys/Cargo.toml
description = "System crate for the Mozilla SpiderMonkey JavaScript engine."
repository.workspace = true
version = "0.140.10-2"
version = "0.140.10-0"
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

In general how should we deal with such point version updates? Would it perhaps make sense to just go to 140.10.1-0 and drop the 0 major? All releases would still be "pre-release" from cargos standpoint, so we aren't really changing anything on the semver side.

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

That sounds pretty reasonable to me.

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

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

In general how should we deal with such point version updates? Would it perhaps make sense to just go to 140.10.1-0 and drop the 0 major? All releases would still be "pre-release" from cargos standpoint, so we aren't really changing anything on the semver side.

Hm, I guess you are right.

@jschwe
Copy link
Copy Markdown
Member

jschwe commented May 5, 2026

Manually merged via #745

@jschwe jschwe closed this May 5, 2026
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.

4 participants