Merge commit '6387bac4281ba1c4a8050cd055071615593d214c' into changes-0917

* commit '6387bac4281ba1c4a8050cd055071615593d214c': (78 commits)
  More consistent test optimization levels (mozilla#1317)
  ci: set minimal permissions on GitHub Workflows
  Compare all primitive value type wrappers by value
  Fixing formatting issues
  Treat String, ConsString, Boolean, and Double as value types
  setter function (from property descriptor) has to convert the args (see HtmlUnit#7) also
  use try-with-resource
  FIX: Wrap key and value for NativeJavaMap iterator
  Added more tests
  FIX: Wrap result of iterator
  BUG: for X of javaList does not work properly in strict mode
  removed obsolete LineSeparator
  Spotless
  Preserving cause, when a JavaException is rethrown in JavaScript
  fix ScriptException when bound functions are called inside Promise.then()
  test cases from mozilla#1242 fix taken from p-bakker's sugestion
  fix name property for bound functions (see issue mozilla#1297)
  Fix the condition for isResourceChanged
  Code Cleanup (mozilla#1295)
  ignore %c styling but count to not disturb further replacements
  ...

# Conflicts:
#	src/org/mozilla/javascript/NativeObject.java
#	testsrc/org/mozilla/javascript/tests/json/JsonParserTest.java

Author: johnspackman

.github/workflows/gradle.yml

@@ -6,6 +6,8 @@ on:
   pull_request:
     branches: [ master ]
 
+permissions: read-all
+
 jobs:
   build:
     runs-on: ubuntu-latest

.github/workflows/publish-github.yml

@@ -7,6 +7,7 @@ on:
     types: [published]
   # Allows to run this workflow manually from the Actions tab
   workflow_dispatch:
+permissions: read-all
 jobs:
   build:
     runs-on: ubuntu-latest

.github/workflows/publish-maven.yml

@@ -3,6 +3,7 @@ name: Publish to Maven Central
 on:
   # Allows to run this workflow manually from the Actions tab
   workflow_dispatch:
+permissions: read-all
 jobs:
   build:
     runs-on: ubuntu-latest

PGP_KEYS.txt

@@ -0,0 +1,12 @@
+Recent releases of Rhino are signed using the GPG key:
+
+greg+rhino@brail.org
+
+which may be found using GPG at keyserver.ubuntu.com.
+
+The fingerprint is below:
+
+pub   rsa3072 2022-01-04 [SC]
+      E9AF 5293 C334 C7C0 B583  227D 2F45 F85C DF08 2E68
+uid           [ unknown] Gregory Brail (Rhino Automated Builds) <greg+rhino@brail.org>
+sub   rsa3072 2022-01-04 [E]

README.md

@@ -10,22 +10,25 @@ Rhino is licensed under the [MPL 2.0](./LICENSE.txt).
 
 ## Releases
 
+The current release is <a href="https://github.com/mozilla/rhino/releases/tag/Rhino1_7_14_Release">Rhino 1.7.14</a>. Please see the [Release Notes](./RELEASE-NOTES.md).
+
+<details><summary>Releases</summary>
 <table>
-<tr><td><a href="https://github.com/mozilla/rhino/releases/tag/Rhino1_7R5_RELEASE">Rhino 1.7R5</a></td><td>January 29, 2015</td></tr>
-<tr><td><a href="https://github.com/mozilla/rhino/releases/tag/Rhino1_7_6_RELEASE">Rhino 1.7.6</a></td><td>April 15, 2015</td></tr>
-<tr><td><a href="https://github.com/mozilla/rhino/releases/tag/Rhino1_7_7_RELEASE">Rhino 1.7.7</a></td><td>June 17, 2015</td></tr>
-<tr><td><a href="https://github.com/mozilla/rhino/releases/tag/Rhino1_7_7_1_RELEASE">Rhino 1.7.7.1</a></td><td>February 2, 2016</td></tr>
-<tr><td><a href="https://github.com/mozilla/rhino/releases/tag/Rhino1_7_7_2_Release">Rhino 1.7.7.2</a></td><td>August 24, 2017</td></tr>
-<tr><td><a href="https://github.com/mozilla/rhino/releases/tag/Rhino1_7_8_Release">Rhino 1.7.8</a></td><td>January 22, 2018</td></tr>
-<tr><td><a href="https://github.com/mozilla/rhino/releases/tag/Rhino1_7_9_Release">Rhino 1.7.9</a></td><td>March 15, 2018</td></tr>
-<tr><td><a href="https://github.com/mozilla/rhino/releases/tag/Rhino1_7_10_Release">Rhino 1.7.10</a></td><td>April 9, 2018</td></tr>
-<tr><td><a href="https://github.com/mozilla/rhino/releases/tag/Rhino1_7_11_Release">Rhino 1.7.11</a></td><td>May 30, 2019</td></tr>
-<tr><td><a href="https://github.com/mozilla/rhino/releases/tag/Rhino1_7_12_Release">Rhino 1.7.12</a></td><td>January 13, 2020</td></tr>
-<tr><td><a href="https://github.com/mozilla/rhino/releases/tag/Rhino1_7_13_Release">Rhino 1.7.13</a></td><td>September 2, 2020</td></tr>
 <tr><td><a href="https://github.com/mozilla/rhino/releases/tag/Rhino1_7_14_Release">Rhino 1.7.14</a></td><td>January 6, 2022</td></tr>
+<tr><td><a href="https://github.com/mozilla/rhino/releases/tag/Rhino1_7_13_Release">Rhino 1.7.13</a></td><td>September 2, 2020</td></tr>
+<tr><td><a href="https://github.com/mozilla/rhino/releases/tag/Rhino1_7_12_Release">Rhino 1.7.12</a></td><td>January 13, 2020</td></tr>
+<tr><td><a href="https://github.com/mozilla/rhino/releases/tag/Rhino1_7_11_Release">Rhino 1.7.11</a></td><td>May 30, 2019</td></tr>
+<tr><td><a href="https://github.com/mozilla/rhino/releases/tag/Rhino1_7_10_Release">Rhino 1.7.10</a></td><td>April 9, 2018</td></tr>
+<tr><td><a href="https://github.com/mozilla/rhino/releases/tag/Rhino1_7_9_Release">Rhino 1.7.9</a></td><td>March 15, 2018</td></tr>
+<tr><td><a href="https://github.com/mozilla/rhino/releases/tag/Rhino1_7_8_Release">Rhino 1.7.8</a></td><td>January 22, 2018</td></tr>
+<tr><td><a href="https://github.com/mozilla/rhino/releases/tag/Rhino1_7_7_2_Release">Rhino 1.7.7.2</a></td><td>August 24, 2017</td></tr>
+<tr><td><a href="https://github.com/mozilla/rhino/releases/tag/Rhino1_7_7_1_RELEASE">Rhino 1.7.7.1</a></td><td>February 2, 2016</td></tr>
+<tr><td><a href="https://github.com/mozilla/rhino/releases/tag/Rhino1_7_7_RELEASE">Rhino 1.7.7</a></td><td>June 17, 2015</td></tr>
+<tr><td><a href="https://github.com/mozilla/rhino/releases/tag/Rhino1_7_6_RELEASE">Rhino 1.7.6</a></td><td>April 15, 2015</td></tr>
+<tr><td><a href="https://github.com/mozilla/rhino/releases/tag/Rhino1_7R5_RELEASE">Rhino 1.7R5</a></td><td>January 29, 2015</td></tr>
 </table>
+</details>
 
-[Release Notes](./RELEASE-NOTES.md) for recent releases.
 
 [Compatibility table](https://mozilla.github.io/rhino/compat/engines.html) which shows which advanced JavaScript
 features from ES6, and ES2016+ are implemented in Rhino.

RELEASE-STEPS.md

@@ -15,7 +15,7 @@ that's there).
 Now might be a good time to run "./gradlew publishToMavenLocal" and use the
 published JARs as a sanity check.
 
-## Update Compatibility Table
+## Update Native Compatibility Table
 
 The offial Kangax "compat table" now supports Rhino, but it's convenient
 to have our own that shows progress across all releases. Here's how to
@@ -33,8 +33,8 @@ Then, update the table:
 The resulting "index.html" can be copied into "docs/compat/engines.html" in 
 this repo.
 
-## Push the Release to GitHub
 
+## Push the Release to GitHub
 At this point, the current contents of your directory correspond to the 
 new release. Prepare a pull request containing the changes, submit it,
 and merge it -- the result will be that the head of the "master" branch
@@ -69,6 +69,71 @@ The Homebrew team for Mac does not necessarily pick up Rhino releases
 automatically. It may be necessary to submit a PR to the "homebrew/homebrew"
 repo in GitHub for a change to the file "Library/Formula/rhino.rb".
 
+## Update Kangax Compatibility Table
+
+Check out `kangax/compat-table` and prepare a pull request to describe
+support in the new version of Rhino. First, add a new environment for the
+version to `environments.json` like so:
+
+```json
+"rhino1_7_14": {
+  "full": "Rhino 1.7.14",
+  "short": "Rhino 1.7.14",
+  "family": "Rhino",
+  "platformtype": "engine",
+  "release": "2022-01-06",
+  "obsolete": true
+},
+```
+
+Copy the most recent rhino JAR into the directory as `rhino.jar`. Next, run
+`rhino.js`. This will produce a number of messages indicating that failing
+tests now pass, or that new tests now have recorded results:
+
+    **** data-es2016plus ****
+
+    data-es2016plus -> Error.cause property -> AggregateError.prototype lacks cause: test result out of date, res: true, actual: false
+
+Manually update each indicated `data-*.js` file with updated test data as
+indicated. For example, a test that failed in 1.7.13 and passed in 1.7.14
+would have a `res` section with the following diff:
+
+```javascript
+   res: {
+     babel6corejs2: false,
+     babel7corejs3: babel.corejs,
+     /* ... */
+     rhino1_7_13: false,
++    rhino1_7_14: true,
+   }
+```
+
+Rerun `rhino.js` and verify it produces no output. Then `npm run build` and
+submit your pull request.
+
+## Update Babel
+
+Once the `compat-table` changes are merged, check out `babel/babel` and prepare
+a pull request to enable support for `babel-preset-env` in the new release.
+
+* Update `COMPAT_TABLE_COMMIT` in `packages/babel-compat-data/scripts/download-compat-table.sh`
+to correspond to the merge commit in `compat-table`.
+* Run `make build-compat-data && make bootstrap && OVERWRITE=true yarn jest`.
+
+Then submit the resulting patch as a pull request to Babel.
+
+## Update core-js-compat
+
+Compatibility data for `core-js`, the `babel` polyfill engine, also needs to
+be updated.
+
+* Check out `zloirock/core-js` and run `npm install && npm run build-compat`.
+* Define the actual Rhino version in the `compat-rhino-prepare` task in `package.json`.
+* Run `npm run compat-rhino` and you will see the results of tests in the console.
+* Much like in `compat-table`, edit `packages/core-js-compat/src/data.mjs` to add a line
+`rhino: 1.7.[XX]` for any newly-passing test labeled as "not required".
+* Submit a pull request with changes.
+
 ## Prepare for Next Release
 
 Now it's time to move to the next "SNAPSHOT" release. Update gradle.properties,