Release 0.4.1

[nrbgt]

• on dev
  • merge all outstanding PRs
    • Add Tint and Colorize #131
    • Add basic WrapperBase.root property #135
  • ensure CHANGELOG.md is up-to-date
  • ensure the versions have been bumped
    • run doit preflight:release
  • ensure a last-minute
    • run doit audit
  • validate on ReadTheDocs
    • https://readthedocs.org/projects/ipyforcegraph/builds/21915971/
• wait for a successful build of dev
  • https://github.com/jupyrdf/ipyforcegraph/actions/runs/6177917255
• download the dist archive and unpack somewhere
• create a new release through the GitHub UI
  • pick a new release name to go with the version of real (or imaginary) force
    • pure bending
  • paste in the relevant CHANGELOG.md entries
  • upload the artifacts
  • upload distribution to package repositories

    cd dist
    twine upload *.tar.gz *.whl
    npm login
    npm publish jupyrdf-jupyter-forcegraph-$VERSION.tgz
    npm logout

    • https://www.npmjs.com/package/@jupyrdf/jupyter-forcegraph/v/0.4.1
    • https://pypi.org/project/ipyforcegraph/0.4.1/#files
• postmortem
  • handle conda-forge feedstock tasks
    • ipyforcegraph 0.4.1 conda-forge/ipyforcegraph-feedstock#21
    • https://anaconda.org/conda-forge/ipyforcegraph/files?version=0.4.1
  • merge dev into main
    • Update from dev after 0.4.1 #136
  • create postmortem PR from main targeting dev
    • Postmortem 0.4.1 #137
    • bump to next development version
    • bump the CACHE_EPOCH
    • rebuild yarn.lock
    • rebuild .github/locks
      • run doit env:lock
      • run rm -rf .github/locks
      • from a clean command prompt
        • 🐧source envs/lock/bin/activate
        • 🪟 call envs/lock/Scripts/activate.bat
      • commit the new locks
    • update release procedures with lessons learned in
      .github/ISSUE_TEMPLATE/release.md