@@ -332,7 +332,7 @@ we can use a feature called **build matrices**
332332which really shows the value of using CI to test at scale.
333333
334334Suppose the intended users of our software use either Ubuntu, Mac OS, or Windows,
335- and have Python versions 3.10 through 3.12 installed,
335+ and have Python versions 3.11 through 3.13 installed,
336336and we want to support all of these.
337337Assuming we have a suitable test suite,
338338it would take a considerable amount of time to set up testing platforms
@@ -363,7 +363,7 @@ jobs:
363363 strategy:
364364 matrix:
365365 os: ["ubuntu-latest", "macos-latest", "windows-latest"]
366- python-version: ["3.10 ", "3.11 ", "3.12 "]
366+ python-version: ["3.11 ", "3.12 ", "3.13 "]
367367
368368 # Here we add the reference to the os matrix values
369369 runs-on: ${{ matrix.os }}
@@ -391,7 +391,7 @@ jobs:
391391
392392The `{{ }}` are used
393393as a means to reference configuration values from the matrix.
394- This way, every possible permutation of Python versions 3.10 through 3.12
394+ This way, every possible permutation of Python versions 3.11 through 3.13
395395with the latest versions of Ubuntu, Mac OS and Windows operating systems
396396will be tested, and we can expect 9 build jobs in total.
397397We can also use this in the `name` key of the step to accurately reflect what it is doing
0 commit comments