How to Release

Warning

Please check whether the test262-test passed all tests before release.

1. Rebase the dev branch into the main branch.
2. Check that all the CI tests are passed through GitHub Actions.
3. Merge the main branch with the dev branch.
4. Update the .mailmap file for new contributors.
5. Update the following files with the new version vX.X.X in the main branch.
   • ./README.md
   • ./build.sbt
   • ./src/main/scala/esmeta/package.scala
6. Add version tag vX.X.X:

   ESMETA_VERSION="vX.X.X"
   git tag $ESMETA_VERSION
   git push --tag origin $ESMETA_VERSION

7. Update gh-pages (ScalaDoc):

   sbt ghpagesPushSite

8. Create a new release by choosing a new tag, vX.X.X.
9. Click the Generate release notes to load the automated generated draft of the explanation.
10. Add contributors by copying and pasting the result of git shortlog -sn --no-merges vX.X.X..vX.X.X. For example, if the previous version is v0.1.0 and the new version is v0.2.0, the following notes should be added:

    Contributors

    The following list is automatically generated by git shortlog -sn --no-merges v0.1.0..v0.2.0:

        13	Jihyeok Park (jhnaldo)
         3	Doehyun Baek (doehyunbaek)
    

11. Copy and paste the content in the README.md file into the index.md file in the es-meta/es-meta.github.io repository to update the website.

Update CI in ecma262

1. Enter the cloned repository of ecma262.
2. Pull and check out to the main branch.
3. Update the .github/workflows/esmeta-typecheck.yml file (e.g., #3219).
4. Run the following command to update the esmeta-ignore.json file:

   esmeta tycheck -tycheck:log -tycheck:ignore=esmeta-ignore.json -tycheck:update-ignore

5. Create and push the commit.
6. Create pull request (e.g., #3219).