Right now I’ve launched model 0.35.0 of the GitHub Motion for doing spelling checking of your documentation and so forth. for which I’m the present maintainer.
This launch was prompted by a number of updates.
- Docker base picture bumped to Python 3.12.0
Which resulted in updates to a number of of the dependencies utilized by the core part PySpelling.
As well as I’m trying into the lengthy over due decommissioning of a number of older releases. They’ll at all times be rebuilt from supply on GitHub, however there isn’t a have to hold the Docker picture artifacts round.
The related variations are:
- 0.21.1
- 0.22.0
- 0.22.1
- 0.23.0
- 0.23.1
- 0.23.2
- 0.24.0
- 0.25.0
- 0.26.0
- 0.27.0
- 0.28.0
The sundown coverage is printed in the repository wiki.
I’m finding tasks utilizing these and evaluating whether or not a PR must be made.
I discover some attention-grabbing forks of the repository itself, the place I think about inquiring with the proprietor if they’ve adjustments that I might elevate upstream.
For the person forks and forks of forks of different repositories, I feel I’ll simply ignore them.
- They’ll replace from upstream (I test if upstream is updated for forks, however not forks of forks)
- Or they might begin utilizing Dependabot or related, some do however have dormant PRs.
Software program requires upkeep, similar to this motion. These releases aren’t so thrilling, however they’re mandatory with a view to be related.
