chore(deps): update rojopolis/spellcheck-github-actions action to v0.35.0 #274
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
0.27.0
->0.35.0
Release Notes
rojopolis/spellcheck-github-actions (rojopolis/spellcheck-github-actions)
v0.35.0
Compare Source
Bumping to Python 3.12.0 slim, introduced a number of dependency updates, not all were required, but I have decided to update quite a few, since the Docker image is rebuilt anyway.
v0.34.0
Compare Source
Bumped the core component PySpelling to version 2.9, together with wcmatch, bumped to version 2.5, all via PR #174 bu @jonasbn
Docker image updated to Python 3.11.5 slim via PR #170 from Snyk. Release notes for Python 3.11.5
Added constraint for
requirements.txt
since one of the dependencies does not support Cython version 3.I found two guides to fixing the problem:
They state somewhat the same and I have applied a fix via PR #172 now the Docker image can build again
v0.33.1
Compare Source
An update is recommended if you are using the
output_file
parameter, since the output file handling was shielding the propagation of the status of the actual spellcheck.The issue was observed in #166 reported by @nlhomme, where the action was reporting success, even though the spellcheck was failing.
The bug information was lifted into a new issue #167 and was addressed in PR #168 by @jonasbn
v0.33.0
Compare Source
v0.32.0
Compare Source
@dependabot raised an alert for the used dependency: pymdown-extensions. The vulnerability is labelled as CVE-2023-32309. The issue has been present in pymdown-extensions since version 1.5.0 and is patched in version 10.0.
Snyk has provided a patch via PR #158, which has been tested and no regressions has been observed, even with a version leap for pymdown-extensions. from version 8.2 to 10.0. The GitHub Action has been updated to use the patched version, even though there are no direct use of the vulnerable code in the action, but we do not want to be the source of a vulnerability.
pymdown-extensions was increased to version 10.0.1, since a bug fix was released to follow up on the security patch.
v0.31.0
Compare Source
v0.30.0
Compare Source
PySpelling updated from version 2.8.1 to 2.8.2, including several fixes
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
v0.29.0
Compare Source
Docker image updated to Python 3.11.1 slim via PR #139 from @dependabot. Release notes for Python 3.11.1
lxml bumped to version 4.9.1 from 4.9.1 to get the build to work, without jumping through too many hoops. We prefer relying on wheel instead of building from source, since
lxml
can become quite a time sinkv0.28.0
Compare Source
Configuration
📅 Schedule: Branch creation - "before 4am on Monday" (UTC), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR has been generated by Mend Renovate. View repository job log here.