📜 Things to do when publishing the next Babel version

[nicolo-ribaudo]

I didn't know where to write these things that I should remember to do when releasing the next version, but I think that an issue in this repo is ok 😆

[nicolo-ribaudo]

✔️ Babel 7.2.3

• Test lerna 3?
• @babel/preset-env didn't get published last time ([lerna] Don't ignore .json data files in preset-env babel#9200)
• @babel/polyfill needs to be force-updated (Align polyfill regenerator runtime version babel#8618 (comment))
• unpkg returns 404 for @babel/standalone 7.2.2 (REPL still on 6.26.0 website#1901 (comment)) (seems to be working now?)

[nicolo-ribaudo]

✔️ Babel 7.2.4

• Figure out why @babel/standalone isn't minified (https://unpkg.com/@babel/standalone@7.2.3/babel.min.js)

[nicolo-ribaudo]

✔️ Babel 7.2.5

• @babel/polyfill hasn't been correctly published (@babel/polyfill was published yesterday without pushing browser.js babel#9227). This is for the same reason of 📜 Things to do when publishing the next Babel version #78 (comment): Lerna 3 doesn't run prepublish/postpublish by default, and when I fixed it I didn't force-publish @babel/polyfill but only standalone.

[nicolo-ribaudo]

✔️ Babel 7.3.0

• (NOTE: Only if @babel/helpers changed)
  Before publishing, run npx lerna changed to check if nicolo-ribaudo/lerna@ef2f1fc works. If it doesn't, @babel/runtime and @babel/runtime-corejs2 need to be force-published as always.
  NOTE: It didn't work.
• Instead of running lerna publish, run lerna version + lerna publish from-git to check if it would be possible in the future to run lerna publish from-git automatically from github.
  NOTE: --force-publish needs to be run with lerna version; --require-scripts with lerna publish.
• Force-publish @babel/types if needed (@babel/types wasn't released after being modified babel#9239), merge ([@babel/types] Moved generators related to babel-types into the babel-types package directory. babel#9245)
• new package:
  • make sure it has access public for scoped npm packages
  • correct npmignore (extra files)
  • check that new dependencies don't add too much size
  • check perf regressions
  • need a basic dogfood of Babel itself before release
  • possible to check proposal usage via repl url?

[nicolo-ribaudo]

✔️ Babel 7.3.2

• Merge Use a GitHub Action to generate the changelog babel#9434 and check if it works.
  NOTE: It doesn't work, because doesn't fire "push" for tags in public repos.

[nicolo-ribaudo]

✔️ Babel 7.3.3

• Merge Create a new release after a v*.*.* commit instead of the tag babel#9470 (already tested).
• Update typescript preset (Upgrade to @babel/preset-typescript to use @babel/plugin-transform-typescript@^7.3.2 babel#9497) (needs --force-publish)
• Run make new-version and then make publish

[nicolo-ribaudo]

✔️ Babel 7.3.4

• Update CHANGELOG.md using @babel-bot

[nicolo-ribaudo]

✔️ Babel 7.4.0

• Finally publish using a GitHub action (merge Publish to npm using a GitHub action babel#9588)
  • Add NPM_TOKEN to env vars

[nicolo-ribaudo]

✔️ Babel 7.4.3

• ⚠️ Be 100% sure that the github action has a valid npm token
• The "Publish to npm" action will not print anything for a long time (~15 mins). It's still working internally.

[nicolo-ribaudo]

✔️ Babel 7.4.4

• Check that @babel/polyfill is es5-compatible.
• Disable "publish to npm" from the GH action; it's too slow.

[nicolo-ribaudo]

✔️ Babel 7.5.0

• Merge the feature-7.5.0/fsharp-pipeline branch to master