Jupyter-events

Latest version: v0.10.0

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

Scan your dependencies

Page 3 of 3

0.2.0

([Full Changelog](https://github.com/jupyter/jupyter_events/compare/v0.1.0...88acd8ec613fe7d2aa6fcaf07158275989dc5dfd))

Enhancements made

- Add new EventSchema and SchemaRegistry API [4](https://github.com/jupyter/jupyter_events/pull/4) ([Zsailer](https://github.com/Zsailer))
- Add redactionPolicies field to Jupyter Event schemas [2](https://github.com/jupyter/jupyter_events/pull/2) ([Zsailer](https://github.com/Zsailer))

Contributors to this release

([GitHub contributors page for this release](https://github.com/jupyter/jupyter_events/graphs/contributors?from=2022-05-31&to=2022-08-11&type=c))

[kevin-bates](https://github.com/search?q=repo%3Ajupyter%2Fjupyter_events+involves%3Akevin-bates+updated%3A2022-05-31..2022-08-11&type=Issues) | [Zsailer](https://github.com/search?q=repo%3Ajupyter%2Fjupyter_events+involves%3AZsailer+updated%3A2022-05-31..2022-08-11&type=Issues)

0.1.0

Making a Jupyter Events Release

Using `jupyter_releaser`

The recommended way to make a release is to use [`jupyter_releaser`](https://jupyter-releaser.readthedocs.io/en/latest/get_started/making_release_from_repo.html).

Note that we must use manual versions since Jupyter Releaser does not
yet support "next" or "patch" when dev versions are used.

Manual Release

To create a manual release, perform the following steps:

Set up

bash
pip install hatch twine
git pull origin $(git branch --show-current)
git clean -dffx


Update the version and apply the tag

bash
echo "Enter new version"
read new_version
hatch version ${new_version}
git tag -a ${new_version} -m "Release ${new_version}"


Build the artifacts

bash
rm -rf dist
hatch build


Publish the artifacts to pypi

bash
twine check dist/*
twine upload dist/*

Page 3 of 3

© 2024 Safety CLI Cybersecurity Inc. All Rights Reserved.