Checklist and coordination: Major upgrade to v3.0.0

[sagarpreet-chadha]

1. Bootstrap major version upgrade (noting Merged Bump bootstrap from 4.3.1 to 4.5.3 Bump bootstrap from 4.3.1 to 4.5.3 #645)

To do:

• complete this PR

• open a matching PR on plots2 for this new version #

• open an issue using the "release" template with this checklist with title Checklist and coordination for v0.0.0 major/minor/patch release (see semantic versioning)

• compile release notes below from corresponding release milestone

• update version number in package.json (ex #1695)

• finalize and merge to main branch (freeze merges to main branch until next step)

• merge, build and publish /dist/ files to stable (merges to main branch can resume for next release)

• create a release on GitHub and use features description + release notes from below

• tag version number branch (i.e. v3.0.0)

• publish tagged branch to npm (actually did from main branch -- @jywarren)

• publish to live github-pages demo (with bash script from /scripts/update_demo) (from within GitPod works well)

• close this issue!

[gitpod-io]

[sagarpreet-chadha]

@jywarren let's publish this :)

[jywarren]

At image-sequencer we've been refining a release checklist workflow which is quite strict. Could be interesting to see how we are doing the coordination leading up to a new release! publiclab/image-sequencer#1751 - it's actually stored as an issue template so we open a new issue for each, and go through the checklist.

Here, for example, one checklist item might be to create a corresponding issue in plots2 - also, if the checklist is an issue, then it can last after the PR is closed, for tasks that come after the PR. What do you think? No big deal for this one but just an idea.

[sagarpreet-chadha]

Oops I mistakenly committed 3.2.0 🙈

[sagarpreet-chadha]

Sure, we can use the checklist this time itself 👍

[jywarren]

Oh cool! Well it's a huge checklist and we don't need to do every step as we do in IS - but great! OK, this should be good then?

[sagarpreet-chadha]

Yes this is good to go 🚀

[jywarren]

Great! Let's make a github release too, just because we're calling this a major?

[jywarren]

I'll publish from the main branch to NPM, too!

[sagarpreet-chadha]

https://github.com/publiclab/PublicLab.Editor/releases/tag/v3.0

Already done using the create-release script 🙈

[jywarren]

Just noting:

ah, we skipped the build dist files step (thinking of NPM) but there haven't been any functional changes to that file since the last time it was built, so we should be OK: https://github.com/publiclab/PublicLab.Editor/commits/main
the dependabot updates may not all be baked in for upstream deps we compile in, but it's probably fine

indeed, nothing would have been compiled in now that I look at the specific commits. Browserify was updated but that's probably fine too.

[jywarren]

Published as v3.0.0!!! 🎉

https://www.npmjs.com/package/publiclab-editor

[sagarpreet-chadha]

Awesomeee 🎉