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
[](https://isitmaintained.com/project/reactive-firewall/multicast"Average time to resolve an issue")
16
+
[](https://isitmaintained.com/project/reactive-firewall/multicast"Percentage of issues still open")
17
+
18
+
## Configurable CI Variables
19
+
20
+
This section documents environment variables used across CI workflows to ensure consistency and
21
+
simplify maintenance.
22
+
23
+
### Python Version Variables
24
+
25
+
To standardize Python version management across all CI workflows, we use a set of environment
26
+
variables defined at the top of each workflow file. This approach centralizes version definitions
27
+
while maintaining separation between workflows, making future updates easier and ensuring
28
+
consistency.
29
+
30
+
#### Standard Python Version Variables
31
+
32
+
| Variable | Purpose | Example Value |
33
+
|----------|---------|---------------|
34
+
|`PYTHON_DEFAULT`| The default Python version used for single-version jobs |`"3.12"`|
35
+
|`PYTHON_OLD_MIN`| Oldest/minimum Python version for cross-python portability testing |`"3.10"`|
36
+
|`PYTHON_OLD_EXTRA`| Additional Python version for coverage testing |`"3.11"`|
37
+
|`PYTHON_EXPERIMENTAL`| Future/experimental Python version for optional testing |`"3.13"`|
38
+
39
+
#### Usage Examples
40
+
41
+
##### Setting up Python with the default version
42
+
43
+
```yaml
44
+
- uses: actions/setup-python@v5
45
+
with:
46
+
python-version: "${{ vars.PYTHON_DEFAULT }}"
47
+
```
48
+
49
+
##### Using matrix strategy for multi-version testing
0 commit comments