The current setup of the pull request pipeline means that the bump version steps will run several times (once for each parallel run). This PR modifies this pipeline into two separate jobs, so that the testing steps will run against each applicable version in parallel, and the bump version steps will run only once after all build jobs have completed successfully:
The build job runs the tests for all applicable Python versions in parallel
The bump-version job runs after the build job and bumps the version on a pull request to master
Type of change
What types of changes do you want to introduce to DrHeader?
[ ] Bugfix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change
[ ] Documentation Update
[ ] Test Update
[ ] Rules Update
[x] Other (please describe) - Actions update
Please ensure your pull request adheres to the following guidelines:
[ ] A Github Issue that explains the work.
[ ] The changes are in a branch that is reasonably up to date
[ ] Tests are provided to reasonably cover new or altered functionality.
[ ] Documentation is provided for the new or altered functionality.
[ ] You have the legal right to give us this code.
Proposed changes
The current setup of the pull request pipeline means that the bump version steps will run several times (once for each parallel run). This PR modifies this pipeline into two separate jobs, so that the testing steps will run against each applicable version in parallel, and the bump version steps will run only once after all build jobs have completed successfully:
Type of change
What types of changes do you want to introduce to DrHeader?
Please ensure your pull request adheres to the following guidelines: