Releases: DataDog/riot
Releases · DataDog/riot
0.19.0
What's Changed
- ci: fix readthedocs build by @majorgreys in #218
- feat: support 3.12 and drop support for 2.7 virtual environments by @majorgreys in #220
0.18.0
New Features
- Add support for CPython 3.12
0.17.7
0.17.6
0.17.5
Bug Fixes
- pin
pip<23.2
to avoid breaking change impacting pip-tools for Python 3.7
0.17.4
0.17.3
Fixes an issue in which riot generated a requirements lockfile for a Venv instance other than the one it was running tests for. This behavior was happening due to logic that skipped Venv instances with pkgs == None while preparing the environment, but not while running tests. The fix is to stop riot from ignoring pkgs-less Venvs in all cases.
v0.17.2
Bug Fixes
- Avoid using latests versions of
virtualenv
since it has dropped support for Python 2.7.
0.17.1
fix: change how Venvs are hashed (#203) * use the full_pkg_str as the basis for Venv hashes because the hash of self can change between requirements installation and pythonpath creation, self is no longer a suitable hash key self.full_pkg_str does not change during a single run of riot, so it is a better hash key * change hasher in the correct place * release note * include py in hash * change expected hashes in tests * Update releasenotes/notes/stable-hash-63389fa04cca60ab.yaml Co-authored-by: Zachary Groves <32471391+ZStriker19@users.noreply.github.com> * avoid hash collisions by including env name in hash seed * update hash expectations in tests * delete release note --------- Co-authored-by: Zachary Groves <32471391+ZStriker19@users.noreply.github.com>
0.17.0
New Features
- Adds the
riot requirements <hash>
command, which uses pip-compile to generate a requirements lockfile for venv identified by the hash - Adds the
-c/--recompile-requirements
flag toriot run
. When set, this flag causes the requirements.txt lockfile and the venv itself to be regenerated. When omitted, the requirements lockfile is only built if it does not already exist.