From 845b56d1aff175d30be528655ffa02a5bc793ac3 Mon Sep 17 00:00:00 2001 From: Peter Burns Date: Mon, 7 Oct 2024 15:55:14 -0700 Subject: [PATCH] Add release instructions based on what dfreedm and I figured out. --- RELEASING.md | 16 ++++++++++++++++ 1 file changed, 16 insertions(+) create mode 100644 RELEASING.md diff --git a/RELEASING.md b/RELEASING.md new file mode 100644 index 000000000..951074f4d --- /dev/null +++ b/RELEASING.md @@ -0,0 +1,16 @@ +## How to release a new version of Polymer + +- `npm ci` +- `npm i -g np` +- `npx gulp update-version` +- Update CHANGELOG.md +- Edit package.json back to the previous version so that `np` can be the one + to bump the version. +- `np --yolo --preview` + - Ensures that you have permission, does a final check of all the steps. +- `npm pack` and diff the tgz's contents against the previous version's. + We release a new version of Polymer rarely enough that it's worth it to be + careful. +- `np --yolo` +- After it completes successfully it will open the GitHub releases page for + your new version. Edit the changelist there to remove irrelevent entries and publish.