I have just uploaded version 0.30.0 of the Spellcheck GitHub action to the GitHub Marketplace and DockerHub.
The core component PySpelling has been updated with several fixes and the base Docker images has also been updated.
It was my hope that one of the fixes in PySpelling addressed issue #121, but that does not seem to be the case after some testing, so the problem is possibly deep in the bowels of aspell.
As mentioned in the release announcement for 0.29.0, I prefer baby steps to moon landings, so this is pretty light weight, but if something breaks, the changes are few, problems hopefully easier to pinpoint and rolling back will not be a hassle.
Version 0.30.0 is available on the GitHub marketplace and will be supported for the next 365 days.
Which leads me to that I need to address the end of life for the versions:
- 0.21.0
- 0.21.1
- 0.22.0
- 0.22.1
I have not dug into how actively these versions are put to use, but it will probably require a few PRs.
Change log for 0.30.0
0.30.0, 2023-02-20, maintenance release, update not required
- PySpelling updated from version 2.8.1 to 2.8.2, including several fixes
- FIX: Ensure that Aspell actually uses the encoding passed to it for dictionaries.
- FIX: Use a disallow list for problematic or unsupported arguments to the underlying spell checker instead of using a more restrictive allow list.
- FIX: Fix logic bug in JavaScript filter.
Lifted from the release notes for PySpelling
Docker image updated to Python 3.11.2 slim via PR #142 from @dependabot. Release notes for Python 3.11.2
Top comments (0)