Bump crate-ci/typos from 1.21.0 to 1.22.9

[dependabot[bot]]

Bumps crate-ci/typos from 1.21.0 to 1.22.9.

Release notes

Sourced from crate-ci/typos's releases.

v1.22.9

[1.22.9] - 2024-06-22

Fixes

• Stop correcting reoccurrence

v1.22.8

[1.22.8] - 2024-06-21

Features

• (action) Add Arm, Mac support

v1.22.7

[1.22.7] - 2024-06-12

Fixes

• Remove Linux arm64 binary support

v1.22.6

[1.22.6] - 2024-06-12

v1.22.5

[1.22.5] - 2024-06-12

Features

• Linux arm64 binaries

v1.22.4

[1.22.4] - 2024-06-10

• Correct adventerous as adventurous instead of adventures
• Correct manifestion as manifestation instead of manifesto
• Correct manifestior as manifestation instead of manifesto

v1.22.3

[1.22.3] - 2024-06-07

Fixes

• Don't correct arbitral

v1.22.2

[1.22.2] - 2024-06-07

v1.22.1

[1.22.1] - 2024-06-05

... (truncated)

Changelog

Sourced from crate-ci/typos's changelog.

[1.22.9] - 2024-06-22

Fixes

• Stop correcting reoccurrence

[1.22.8] - 2024-06-21

Features

• (action) Add Arm, Mac support

[1.22.7] - 2024-06-12

Fixes

• Remove Linux arm64 binary support

[1.22.6] - 2024-06-12

[1.22.5] - 2024-06-12

Features

• Linux arm64 binaries

[1.22.4] - 2024-06-10

Fixes

• Correct adventerous as adventurous instead of adventures
• Correct manifestion as manifestation instead of manifesto
• Correct manifestior as manifestation instead of manifesto

[1.22.3] - 2024-06-07

Fixes

• Don't correct arbitral

[1.22.2] - 2024-06-07

[1.22.1] - 2024-06-05

• In golang, flate is a valid term from the stdlib

[1.22.0] - 2024-06-03

Fixes

... (truncated)

Commits

• c16dc8f chore: Release
• c7ac1f9 chore: Release
• b34586c docs: Update changelog
• ceaed5b Merge pull request #1044 from epage/reoccurrence
• 038802d fix(dict): Don't correct reoccurrence
• dde4786 chore: Release
• 85d76b5 docs: Update changelog
• ab67cbb Merge pull request #1040 from dyc3/action-support-mac-arm
• 89fad31 feat[ci]: add support for mac and arm systems to the github action
• ff76542 chore(deps): Update Rust Stable to v1.79 (#1035)
• 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 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)

[github-actions[bot]]

Review checklist

This checklist is meant to assist creators of PRs (to let them know what reviewers will typically look for) and reviewers (to guide them in a structured review process). Items do not need to be checked explicitly for a PR to be eligible for merging.

Purpose and scope

• [ ] The PR has a single goal that is clear from the PR title and/or description.
• [ ] All code changes represent a single set of modifications that logically belong together.
• [ ] No more than 500 lines of code are changed or there is no obvious way to split the PR into multiple PRs.

Code quality

• [ ] The code can be understood easily.
• [ ] Newly introduced names for variables etc. are self-descriptive and consistent with existing naming conventions.
• [ ] There are no redundancies that can be removed by simple modularization/refactoring.
• [ ] There are no leftover debug statements or commented code sections.
• [ ] The code adheres to our conventions and style guide, and to the Julia guidelines.

Documentation

• [ ] New functions and types are documented with a docstring or top-level comment.
• [ ] Relevant publications are referenced in docstrings (see example for formatting).
• [ ] Inline comments are used to document longer or unusual code sections.
• [ ] Comments describe intent ("why?") and not just functionality ("what?").
• [ ] If the PR introduces a significant change or new feature, it is documented in NEWS.md with its PR number.

Testing

• [ ] The PR passes all tests.
• [ ] New or modified lines of code are covered by tests.
• [ ] New or modified tests run in less then 10 seconds.

Performance

• [ ] There are no type instabilities or memory allocations in performance-critical parts.
• [ ] If the PR intent is to improve performance, before/after time measurements are posted in the PR.

Verification

• [ ] The correctness of the code was verified using appropriate tests.
• [ ] If new equations/methods are added, a convergence test has been run and the results are posted in the PR.

Created with :heart: by the Trixi.jl community.