the notebook UI (PR #3228 [https://github.com/jupyter/notebook/pull/3228/]). Added a test on Travis CI to flag if symlinks are accidentally introduced in the future. This should prevent the issue that necessitated Typos fix (PR #2815 [https://github.com/jupyter/notebook/pull/2815/]). Rename and update license [ci skip] (PR #2810 [https://github.com/jupyter/notebook/pull/2810/]). Travis builds doc (PR #2808 [https://github following steps: pip install --upgrade setuptools pip git clone https://github.com/jupyter/notebook cd notebook pip install -e . If you are using a system-wide Python installation and you only want to

in the notebook UI (3228 [https://github.com/jupyter/notebook/pull/3228]). Added a test on Travis CI to flag if symlinks are accidentally introduced in the future. This should prevent the issue that necessitated 23]). Typos fix (2815 [https://github.com/jupyter/notebook/pull/2815]). Rename and update license [ci skip] (2810 [https://github.com/jupyter/notebook/pull/2810]). Travis builds doc (2808 [https://github following steps: pip install --upgrade setuptools pip git clone https://github.com/jupyter/notebook cd notebook pip install -e . If you are using a system-wide Python installation and you only want to

and/or build the JavaScript documentation using yuidoc. If you have node and yui-doc installed: $ cd ~/jupyter/notebook/notebook/static/notebook/js/ $ yuidoc . --server warn: (yuidoc): Failed to extract contributing docs to reflect changes to build process #6488 (@RRosio) • Fix Check Release/link_check CI Job #6485 (@RRosio) 64 Chapter 5. Changelog Jupyter Notebook Documentation, Release 6.5.1 5.5.3 5.1 5.10.2 Maintenance and upkeep improvements • Enforce labels on PRs #6235 (@blink1073) • Fix: CI error for python 3.6 & macOS #6215 (@penguinolog) 5.10.3 Other merged PRs • handle KeyError when

and/or build the JavaScript documentation using yuidoc. If you have node and yui-doc installed: $ cd ~/jupyter/notebook/notebook/static/notebook/js/ $ yuidoc . --server warn: (yuidoc): Failed to extract contributing docs to reflect changes to build process #6488 (@RRosio) • Fix Check Release/link_check CI Job #6485 (@RRosio) 5.4.3 Contributors to this release (GitHub contributors page for this release) (@tornaria) 5.9.2 Maintenance and upkeep improvements • Enforce labels on PRs #6235 (@blink1073) • Fix: CI error for python 3.6 & macOS #6215 (@penguinolog) 5.9.3 Other merged PRs • handle KeyError when get

and/or build the JavaScript documentation using yuidoc. If you have node and yui-doc installed: $ cd ~/jupyter/notebook/notebook/static/notebook/js/ $ yuidoc . --server warn: (yuidoc): Failed to extract contributing docs to reflect changes to build process #6488 (@RRosio) • Fix Check Release/link_check CI Job #6485 (@RRosio) 5.6.3 Contributors to this release (GitHub contributors page for this release) (@tornaria) 5.11.2 Maintenance and upkeep improvements • Enforce labels on PRs #6235 (@blink1073) • Fix: CI error for python 3.6 & macOS #6215 (@penguinolog) 5.11.3 Other merged PRs • handle KeyError when

and/or build the JavaScript documentation using yuidoc. If you have node and yui-doc installed: $ cd ~/jupyter/notebook/notebook/static/notebook/js/ $ yuidoc . --server warn: (yuidoc): Failed to extract contributing docs to reflect changes to build process #6488 (@RRosio) • Fix Check Release/link_check CI Job #6485 (@RRosio) 5.8.3 Contributors to this release (GitHub contributors page for this release) (@tornaria) 5.13.2 Maintenance and upkeep improvements • Enforce labels on PRs #6235 (@blink1073) • Fix: CI error for python 3.6 & macOS #6215 (@penguinolog) 5.13.3 Other merged PRs • handle KeyError when

and/or build the JavaScript documentation using yuidoc. If you have node and yui-doc installed: $ cd ~/jupyter/notebook/notebook/static/notebook/js/ $ yuidoc . --server warn: (yuidoc): Failed to extract contributing docs to reflect changes to build process #6488 (@RRosio) • Fix Check Release/link_check CI Job #6485 (@RRosio) 5.7.3 Contributors to this release (GitHub contributors page for this release) (@tornaria) 5.12.2 Maintenance and upkeep improvements • Enforce labels on PRs #6235 (@blink1073) • Fix: CI error for python 3.6 & macOS #6215 (@penguinolog) 5.12.3 Other merged PRs • handle KeyError when

com/jupyter/notebook/pull/6488] (@RRosio [https://github.com/RRosio]) Fix Check Release/link_check CI Job #6485 [https://github.com/jupyter/notebook/pull/6485] (@RRosio [https://github.com/RRosio]) Contributors #6235 [https://github.com/jupyter/notebook/pull/6235] (@blink1073 [https://github.com/blink1073]) Fix: CI error for python 3.6 & macOS #6215 [https://github.com/jupyter/notebook/pull/6215] (@penguinolog [https://github in the notebook UI (3228 [https://github.com/jupyter/notebook/pull/3228]). Added a test on Travis CI to flag if symlinks are accidentally introduced in the future. This should prevent the issue that necessitated

com/jupyter/notebook/pull/6488] (@RRosio [https://github.com/RRosio]) Fix Check Release/link_check CI Job #6485 [https://github.com/jupyter/notebook/pull/6485] (@RRosio [https://github.com/RRosio]) Contributors #6235 [https://github.com/jupyter/notebook/pull/6235] (@blink1073 [https://github.com/blink1073]) Fix: CI error for python 3.6 & macOS #6215 [https://github.com/jupyter/notebook/pull/6215] (@penguinolog [https://github in the notebook UI (3228 [https://github.com/jupyter/notebook/pull/3228]). Added a test on Travis CI to flag if symlinks are accidentally introduced in the future. This should prevent the issue that necessitated

com/jupyter/notebook/pull/6488] (@RRosio [https://github.com/RRosio]) Fix Check Release/link_check CI Job #6485 [https://github.com/jupyter/notebook/pull/6485] (@RRosio [https://github.com/RRosio]) Contributors #6235 [https://github.com/jupyter/notebook/pull/6235] (@blink1073 [https://github.com/blink1073]) Fix: CI error for python 3.6 & macOS #6215 [https://github.com/jupyter/notebook/pull/6215] (@penguinolog [https://github in the notebook UI (3228 [https://github.com/jupyter/notebook/pull/3228]). Added a test on Travis CI to flag if symlinks are accidentally introduced in the future. This should prevent the issue that necessitated