Release 1.2.2

[dvvanessastoiber]

Release notes

• Fixes errors in charts without scales option (like pie) Fixes errors in charts without scales option (like pie) #14
• Sgratzl/deps Sgratzl/deps #16
• Sgratzl/scriptable Sgratzl/scriptable #17
• Sluger/15 test Sluger/15 test #18
• Fix plugin id to make this available on the awesome list. Fix plugin id to make this available on the awesome list. #21
• switch to esm.js to avoid problems with .mjs switch to esm.js to avoid problems with .mjs #22
• fix Center expanded parent node label #19 center group label fix #19 center group label #23
• update dependencies update dependencies #27
• Bump handlebars from 4.1.2 to 4.5.3 Bump handlebars from 4.1.2 to 4.5.3 #28
• add CODEOWNERS file add CODEOWNERS file #29
• Update LICENSE Update LICENSE #31
• Update README.md logo Update README.md logo #33
• Update author, homepage and license Update author, homepage and license #32
• changes for hasOwnerProperty changes for hasOwnerProperty #37

Checklists

Release preparation

• Create new release-x.x.x branch (based on develop branch)
• Collect changes and write release notes
• Draft release PR in GitHub that merges the release-x.x.x into the master branch

Release dependencies first

In case of dependent Phovea/TDP repositories follow dependency tree from the top:

• Release dependent repositories if they contain changes first before proceeding here
• Replace git dependencies in package.json with new version range (e.g., "phovea_core": "^2.3.1" when published on npm or "phovea_core": "github:datavisyn/tdp_core#semver:^8.0.0" for non-published repositories)
• Commit and push new dependencies
• Wait until build is successful
• Repeat with other repositories/dependencies or proceed with next section

Update version

• Check version numbers of dependencies again
• Check if build is successful
• Update this version number following semver
• Commit and push package.json with new version number
• Assign reviewer and wait for final review
• Merge this pull request into master branch
• Add release label (i.e., release: major, release: minor, or release: patch)

Publish npm release

The steps of this section are only necessary if the code is public and should be published to the npm registry.

• chmod -R o+w . in the cloned repository directory (to provide write access to the CircleCI Linux user)
• rm -rf dist && rm -rf build && rm -rf node_modules/ && rm -rf package-lock.json
• docker run -it -v $(pwd):/phovea circleci/node:12.13-buster-browsers /bin/bash and continue inside the container
• cd /phovea
• npm install
• npm run build to build the bundles
• npm login as caleydo-bot
• npm publish
• Check release on npmjs.com

Create GitHub release

• Draft a new release (Code -> Releases -> Draft a new release)
• Use new version number as tag (e.g., v2.3.1)
• Copy release notes
• Publish release

Prepeare next develop release

• Switch to develop branch
• Merge master branch into develop (git merge origin/master)
• Update version in package.json to <next patch version>-SNAPSHOT (e.g., 2.3.1 to 2.3.2-SNAPSHOT)
• Revert dependencies in package.json to develop branches (e.g., "phovea_core": "github:phovea/phovea_core#develop")
• Commit and push changes

🏁 Finish line

• Inform colleagues and customers about the release
• Celebrate the new release 🥳