Bump rojopolis/spellcheck-github-actions from 0.26.0 to 0.36.0

[dependabot]

Bumps rojopolis/spellcheck-github-actions from 0.26.0 to 0.36.0.

Release notes

Sourced from rojopolis/spellcheck-github-actions's releases.

0.36.0, 2024-02-06, feature release, update not required

• With version 2.10 of PySpelling the action now supports the configuration of running jobs in parallel, see the documentation for PySpelling

• Docker image updated to Python 3.12.1 slim via PR #177 from @​dependabot. Release notes for Python 3.12.1

0.35.0

What's Changed

• Bump python from 3.11.5-slim-bullseye to 3.12.0-slim-bullseye by @​dependabot in rojopolis/spellcheck-github-actions#177

Full Changelog: rojopolis/spellcheck-github-actions@0.34.0...0.35.0

0.34.0

What's Changed

• Broken wheel build fix by @​jonasbn in rojopolis/spellcheck-github-actions#172
• Bump actions/checkout from 3 to 4 by @​dependabot in rojopolis/spellcheck-github-actions#171
• Bump python from 3.11.4-slim-bullseye to 3.11.5-slim-bullseye by @​dependabot in rojopolis/spellcheck-github-actions#170
• Bumped pyspelling to 2.9 and wcmatch to 2.5 (or higher) by @​jonasbn in rojopolis/spellcheck-github-actions#174

Full Changelog: rojopolis/spellcheck-github-actions@0.33.1...0.34.0

0.33.1, 2023-07-13, bug fix release, update not required

• 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

0.33.0

What's Changed

• [Snyk] Security upgrade python from 3.11.3-slim-bullseye to 3-slim-bullseye by @​jonasbn in rojopolis/spellcheck-github-actions#164

Full Changelog: rojopolis/spellcheck-github-actions@0.32.0...0.33.0

0.32.0, 2023-05-18, security patch release, update recommended

• @​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.

0.31.0, 2023-05-16, maintenance release, update not required

• Docker image updated to Python 3.11.3 slim via PR #152 from @​dependabot. Release notes for Python 3.11.3

... (truncated)

Changelog

Sourced from rojopolis/spellcheck-github-actions's changelog.

0.36.0, 2024-02-06, feature release, update not required

• With version 2.10 of PySpelling the action now supports the configuration of running jobs in parallel, see the documentation for PySpelling

• Docker image updated to Python 3.12.1 slim via PR #177 from Dependabot. Release notes for Python 3.12.1

0.35.0, 2023-11-16, maintenance release, update not required

• Docker image updated to Python 3.12.0 slim via PR #177 from Snyk. Release notes for Python 3.12.0

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.

• backrefs bumped from version 5.0.1 to 5.6.0, see release notes
• beautifulsoup4 bumped from version 4.9.3 to 4.12.2, see release notes
• lxml bumped from version 4.9.2 to 4.9.3, see release notes
• Markdown bumped from version 3.3.4 to 3.4.4, see release notes
• pymdown-extension bumped from version 10.0.1 to 10.4, see release notes
• PyYAML bumped from version 5.4.1 to 6.0.1, see release notes
• soupsieve bumped from version 2.2.1 to 2.5, see release notes

0.34.0, 2023-09-29, maintenance release, update not required

• 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:

• "Getting requirements to build wheel did not run successfully for sap aicore"
• "Getting requirements to build wheel did not run successfully exit code: 1"

They state somewhat the same and I have applied a fix via PR #172 now the Docker image can build again

0.33.1, 2023-07-13, bug fix release, update not required

• 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

0.33.0, 2023-06-16, maintenance release, update not required

• Docker image updated to Python 3.11.4 slim via PR #164 from Snyk. Release notes for Python 3.11.4

0.32.0, 2023-05-18, security patch release, update recommended

• @​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.

... (truncated)

Commits

• dbd2f1d Merge branch 'master' of github.com:rojopolis/spellcheck-github-actions
• 9fa1ede Bumped version in action description
• 28acf6b Preparing release 0.36.0
• 6d918b6 Merge pull request #195 from rojopolis/issue194
• dc0ebdb Added Table of Contents for easier navigating the documentation
• 36884e2 Bumped PySpelling to 2.10, introducing support for parallel jobs
• fe9c0e0 Merge pull request #191 from rojopolis/dependabot/docker/python-3.12.1-slim-b...
• e21c9cc Added extra words to local dictionary to make spellcheck pass
• 10561a6 Merge pull request #192 from rojopolis/dependabot/github_actions/actions/uplo...
• 99975da Bump actions/upload-artifact from 3 to 4
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

[coderabbitai]

Important

Auto Review Skipped

Bot user detected.

To trigger a single review, invoke the @coderabbitai review command.

Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

Share

• X
• Mastodon
• Reddit
• LinkedIn

---

Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>.
  • Generate unit-tests for this file.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai generate unit tests for this file.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai generate interesting stats about this repository from git and render them as a table.
  • @coderabbitai show all the console.log statements in this repository.
  • @coderabbitai read src/utils.ts and generate unit tests.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (invoked as PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger a review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai help to get help.

Additionally, you can add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.

CodeRabbit Configration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• The JSON schema for the configuration file is available here.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/coderabbit-overrides.v2.json

CodeRabbit Discord Community

Join our Discord Community to get help, request features, and share feedback.