Open nicolo-ribaudo opened 5 years ago
@babel/preset-env
didn't get published last time (https://github.com/babel/babel/pull/9200)@babel/polyfill
needs to be force-updated (https://github.com/babel/babel/pull/8618#issuecomment-448245039)@babel/standalone
7.2.2 (https://github.com/babel/website/issues/1901#issuecomment-448572603) (seems to be working now?)@babel/standalone
isn't minified (https://unpkg.com/@babel/standalone@7.2.3/babel.min.js)@babel/polyfill
hasn't been correctly published (https://github.com/babel/babel/issues/9227). This is for the same reason of https://github.com/babel/notes/issues/78#issuecomment-448968023: Lerna 3 doesn't run prepublish/postpublish by default, and when I fixed it I didn't force-publish @babel/polyfill
but only standalone.@babel/helpers
changed)
Before publishing, run npx lerna changed
to check if nicolo-ribaudo/lerna@ef2f1fcd3e2dba9b1c320d265f66768c5e2e1750 works. If it doesn't, @babel/runtime
and @babel/runtime-corejs2
need to be force-published as always.
NOTE: It didn't work.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
.@babel/types
if needed (babel/babel#9239), merge (https://github.com/babel/babel/pull/9245)--force-publish
)make new-version
and then make publish
CHANGELOG.md
using @babel-bot NPM_TOKEN
to env vars@babel/polyfill
is es5-compatible.feature-7.5.0/fsharp-pipeline
branch to master
@babel/eslint-plugin
(https://github.com/babel/babel/pull/11933 updates usage in README)@babel/runtime-*
(@babel/helpers
is not changed)@babel/core
(#11974 does not touch the contents of @babel/core
)@babel/runtime-*
(The only @babel/helpers
change comment-only: https://github.com/babel/babel/pull/11953)package.json
due to Yarn 2 workspace:
protocol, except the following:
@babel/cli
, @babel/core
, @babel/generator
, @babel/helper-transform-fixture-runner
and @babel/plugin-transform-runtime
, @babel/polyfill
, @babel/register
, @babel/types
make new-version
publish
@babel/plugin-syntax-module-attributes
npm deprecate @babel/plugin-syntax-module-attributes "@babel/plugin-syntax-module-attributes is renamed as @babel/plugin-syntax-import-assertions, please check syntax updates and install the new syntax plugin"
make new-version
, run:
git pull --rebase
yarn release-tool version -f @babel/cli -f @babel/compat-data -f @babel/core -f @babel/eslint-parser -f @babel/eslint-plugin -f @babel/eslint-plugin-development-internal -f @babel/eslint-shared-fixtures -f @babel/eslint-tests -f @babel/generator -f @babel/helper-bindify-decorators -f @babel/helper-builder-react-jsx-experimental -f @babel/helper-call-delegate -f @babel/helper-compilation-targets -f @babel/helper-create-class-features-plugin -f @babel/helper-create-regexp-features-plugin -f @babel/helper-explode-assignable-expression -f @babel/helper-explode-class -f @babel/helper-member-expression-to-functions -f @babel/helper-module-transforms -f @babel/helper-remap-async-to-generator -f @babel/helper-replace-supers -f @babel/helper-transform-fixture-test-runner -f @babel/helper-validator-option -f @babel/parser -f @babel/plugin-proposal-class-static-block -f @babel/plugin-proposal-export-namespace-from -f @babel/plugin-proposal-function-bind -f @babel/plugin-proposal-logical-assignment-operators -f @babel/plugin-proposal-nullish-coalescing-operator -f @babel/plugin-proposal-numeric-separator -f @babel/plugin-proposal-optional-chaining -f @babel/plugin-syntax-class-static-block -f @babel/plugin-syntax-import-assertions -f @babel/plugin-syntax-module-string-names -f @babel/plugin-transform-modules-systemjs -f @babel/plugin-transform-react-jsx-development -f @babel/plugin-transform-runtime -f @babel/plugin-transform-typescript -f @babel/polyfill -f @babel/preset-env -f @babel/preset-typescript -f @babel/register -f @babel/runtime -f @babel/runtime-corejs2 -f @babel/runtime-corejs3 -f @babel/standalone -f @babel/traverse -f @babel/types
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 :laughing: