Update dependency org.mozilla:rhino to v1.8.0 #75
Loading…
Add table
Reference in a new issue
No description provided.
Delete branch "renovate/org.mozilla-rhino-1.x"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
This PR contains the following updates:
1.7.13
->1.8.0
Release Notes
mozilla/rhino (org.mozilla:rhino)
v1.8.0
January 2, 2025
Rhino 1.8.0 contains some significant changes, so we're incrementing the final version number for the first time in a very long time. Here are a few highlights:
Thanks to all who contributed -- we had 24 contributors to this release, with some new contributors who added significant capabilities. Please keep the contributions and attention coming!
v1.7.15
May 3, 2024
Highlights of this release include:
This release includes committs from 29 different committers. Thanks to you all for your help!
v1.7.14
January 6, 2022
Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR was generated by Mend Renovate. View the repository job log.
Copied from https://github.com/antville/helma/pull/39#issuecomment-1554574060:
Currently throwing exception trying to access cleanly installed welcome app:
The Rhino commit causing the exception is
73a8b29d79
– found viagit bisect
.A work-around is patching MemberBox.java with an NP check:
Digging deeper, there is a weird inconsistency between
Context.emptyArgs
andScriptRuntime.emptyArgs
: although the former is set to the latter in Context.java and ScriptRuntime.java, resp., both are not the same in JavaMembers.java:At this point,
Context.emptyArgs
is indeednull
, whileScriptRuntime.emptyArgs
is not! This can be used as an alternative work-around here:It begs the question if this is a Rhino issue, or if there is some Helma code causing this…
Edited/Blocked Notification
Renovate will not automatically rebase this PR, because it does not recognize the last commit author and assumes somebody else may have edited the PR.
You can manually request rebase by checking the rebase/retry box above.
⚠️ Warning: custom changes will be lost.
The NPE issue described in https://github.com/mozilla/rhino/issues/1477 is fixed – including rhino-all.jar and so far Helma works with Rhino 1.8 as well.