You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This version of the PTB updates nox task `version:check`, see #441.
6
+
This requires file `noxconfig.py` of each project to specify the path to `version.py` in `Config.version_file`.
7
+
8
+
With this version of the PTB you can customize the arguments for `pyupgrade` in file `noxconfig.py`, see ticket #449 for details:
9
+
```python
10
+
pyupgrade_args = ("--py310-plus",)
11
+
```
12
+
13
+
## 📚 Documentation
14
+
* Updated getting_started.rst for allowing tag-based releases
15
+
16
+
## ✨ Features
17
+
18
+
*[#441](https://github.com/exasol/python-toolbox/issues/441): Switched nox task for `version:check` to use the config value of `version_file` to specify the location of the `version.py`
19
+
20
+
## 🐞 Bug Fixes
21
+
* Updated `python-environment` action to use space-separated values for extras
With #441, please ensure that the location of the `version.py` is given for `Config.version_file`,
6
-
which is specified in the `noxconfig.py`
7
-
8
-
With #449, it's possible to customize what arguments are being using with `pyupgrade`
9
-
via the `noxconfig.Config`:
10
-
```python
11
-
pyupgrade_args = ("--py310-plus",)
12
-
```
13
-
14
-
## 📚 Documentation
15
-
* Updated getting_started.rst for allowing tag-based releases
16
-
17
-
## ✨ Features
18
-
19
-
*[#441](https://github.com/exasol/python-toolbox/issues/441): Switched nox task for `version:check` to use the config value of `version_file` to specify the location of the `version.py`
0 commit comments