Jupyterlab-ui-profiler

Latest version: v0.2.2

Safety actively analyzes 682471 Python packages for vulnerabilities to keep your Python projects secure.

Scan your dependencies

Page 2 of 2

0.1.5

**Please uninstall the old version before upgrading.** This is necessary because with this release the extension was moved to `jupyterlab` namespace.

([Full Changelog](https://github.com/jupyterlab/ui-profiler/compare/v0.1.4...59e2b4d9172df6c9865e1563c0421037fb850b10))

Enhancements made

- Allow to add code to run before invoking completer [24](https://github.com/jupyterlab/ui-profiler/pull/24) ([krassowski](https://github.com/krassowski))
- Add stop button [20](https://github.com/jupyterlab/ui-profiler/pull/20) ([krassowski](https://github.com/krassowski))
- Simplify tab scenarios options for easier setup [19](https://github.com/jupyterlab/ui-profiler/pull/19) ([krassowski](https://github.com/krassowski))

Bugs fixed

- Fix for completer benchmark in CM6 (Lab 4.0) [23](https://github.com/jupyterlab/ui-profiler/pull/23) ([krassowski](https://github.com/krassowski))
- Do not sort reference timing array but its copy [13](https://github.com/jupyterlab/ui-profiler/pull/13) ([krassowski](https://github.com/krassowski))

Maintenance and upkeep improvements

- Allow jupyter-server v2 [22](https://github.com/jupyterlab/ui-profiler/pull/22) ([krassowski](https://github.com/krassowski))
- Update types for tabs scenario [21](https://github.com/jupyterlab/ui-profiler/pull/21) ([krassowski](https://github.com/krassowski))
- Migrate to `jupyterlab` npm namespace [16](https://github.com/jupyterlab/ui-profiler/pull/16) ([krassowski](https://github.com/krassowski))

Documentation improvements

- Fix docs typos, remove style comment [12](https://github.com/jupyterlab/ui-profiler/pull/12) ([krassowski](https://github.com/krassowski))

Contributors to this release

([GitHub contributors page for this release](https://github.com/jupyterlab/ui-profiler/graphs/contributors?from=2022-12-18&to=2022-12-28&type=c))

[github-actions](https://github.com/search?q=repo%3Ajupyterlab%2Fui-profiler+involves%3Agithub-actions+updated%3A2022-12-18..2022-12-28&type=Issues) | [krassowski](https://github.com/search?q=repo%3Ajupyterlab%2Fui-profiler+involves%3Akrassowski+updated%3A2022-12-18..2022-12-28&type=Issues)

0.1.4

([Full Changelog](https://github.com/jupyterlab/ui-profiler/compare/v0.1.3...f2b4a4443b5fff366359abc6a293274829e81491))

Enhancements made

- Implement simple time measurement benchmark [1](https://github.com/jupyterlab/ui-profiler/pull/1) ([krassowski](https://github.com/krassowski))

Bugs fixed

- Fix re-opening of main area widget [3](https://github.com/jupyterlab/ui-profiler/pull/3) ([krassowski](https://github.com/krassowski))
- Fix form data loss on change of benchmarks/scenarios [2](https://github.com/jupyterlab/ui-profiler/pull/2) ([krassowski](https://github.com/krassowski))

Maintenance and upkeep improvements

- Add missing `test:update` [11](https://github.com/jupyterlab/ui-profiler/pull/11) ([krassowski](https://github.com/krassowski))
- Second attempt to fix galata action [10](https://github.com/jupyterlab/ui-profiler/pull/10) ([krassowski](https://github.com/krassowski))
- Install jupyterlab for playwright update [9](https://github.com/jupyterlab/ui-profiler/pull/9) ([krassowski](https://github.com/krassowski))
- Add yarn.lock [7](https://github.com/jupyterlab/ui-profiler/pull/7) ([krassowski](https://github.com/krassowski))
- Add enforce-label check [6](https://github.com/jupyterlab/ui-profiler/pull/6) ([krassowski](https://github.com/krassowski))
- Fix jupyter-releaser CI check by moving hooks to `pyproject.toml` [5](https://github.com/jupyterlab/ui-profiler/pull/5) ([krassowski](https://github.com/krassowski))

Documentation improvements

- User-facing documentation [8](https://github.com/jupyterlab/ui-profiler/pull/8) ([krassowski](https://github.com/krassowski))

Contributors to this release

([GitHub contributors page for this release](https://github.com/jupyterlab/ui-profiler/graphs/contributors?from=2022-12-06&to=2022-12-18&type=c))

[github-actions](https://github.com/search?q=repo%3Ajupyterlab%2Fui-profiler+involves%3Agithub-actions+updated%3A2022-12-06..2022-12-18&type=Issues) | [krassowski](https://github.com/search?q=repo%3Ajupyterlab%2Fui-profiler+involves%3Akrassowski+updated%3A2022-12-06..2022-12-18&type=Issues)


Making a new release of jupyterlab-ui-profiler

The extension can be published to `PyPI` and `npm` manually or using the [Jupyter Releaser](https://github.com/jupyter-server/jupyter_releaser).

Manual release

Python package

This extension can be distributed as Python
packages. All of the Python
packaging instructions in the `pyproject.toml` file to wrap your extension in a
Python package. Before generating a package, we first need to install `build`.

bash
pip install build twine hatch


Bump the version using `hatch`. By default this will create a tag.
See the docs on [hatch-nodejs-version](https://github.com/agoose77/hatch-nodejs-version#semver) for details.

bash
hatch version <new-version>


To create a Python source package (`.tar.gz`) and the binary package (`.whl`) in the `dist/` directory, do:

bash
python -m build


> `python setup.py sdist bdist_wheel` is deprecated and will not work for this package.

Then to upload the package to PyPI, do:

bash
twine upload dist/*


NPM package

To publish the frontend part of the extension as a NPM package, do:

bash
npm login
npm publish --access public


Automated releases with the Jupyter Releaser

The extension repository should already be compatible with the Jupyter Releaser.

Check out the [workflow documentation](https://github.com/jupyter-server/jupyter_releaser#typical-workflow) for more information.

Here is a summary of the steps to cut a new release:

- Fork the [`jupyter-releaser` repo](https://github.com/jupyter-server/jupyter_releaser)
- Add `ADMIN_GITHUB_TOKEN`, `PYPI_TOKEN` and `NPM_TOKEN` to the Github Secrets in the fork
- Go to the Actions panel
- Run the "Draft Changelog" workflow
- Merge the Changelog PR
- Run the "Draft Release" workflow
- Run the "Publish Release" workflow

Publishing to `conda-forge`

If the package is not on conda forge yet, check the documentation to learn how to add it: https://conda-forge.org/docs/maintainer/adding_pkgs.html

Otherwise a bot should pick up the new version publish to PyPI, and open a new PR on the feedstock repository automatically.

Page 2 of 2

© 2024 Safety CLI Cybersecurity Inc. All Rights Reserved.