chore: pre-commit autoupdate (#4523)

Co-authored-by: pre-commit-ci[bot] <66853113+pre-commit-ci[bot]@users.noreply.github.com>

Author: pre-commit-ci[bot]

.pre-commit-config.yaml

@@ -10,13 +10,13 @@ repos:
         # rustfmt handles rust files, and in some snapshots we expect trailing spaces.
         exclude: '.*\.(rs|snap)$'
   - repo: https://github.com/crate-ci/typos
-    rev: v1.21.0
+    rev: v1.22.0
     hooks:
       - id: typos
         # https://github.com/crate-ci/typos/issues/347
         pass_filenames: false
   - repo: https://github.com/rbubley/mirrors-prettier
-    rev: v3.2.5
+    rev: v3.3.0
     hooks:
       - id: prettier
         additional_dependencies:
@@ -25,7 +25,7 @@ repos:
           # https://github.com/PRQL/prql/issues/3078
           - prettier-plugin-go-template
   - repo: https://github.com/astral-sh/ruff-pre-commit
-    rev: v0.4.5
+    rev: v0.4.7
     hooks:
       - id: ruff
         args: [--fix]
@@ -45,7 +45,7 @@ repos:
       - id: clippy
         stages: [manual]
   - repo: https://github.com/rhysd/actionlint
-    rev: v1.7.0
+    rev: v1.7.1
     hooks:
       - id: actionlint
   - repo: https://github.com/tcort/markdown-link-check

CHANGELOG.md

@@ -1141,8 +1141,8 @@ below in this release).
 
 **Documentation**:
 
-[This release, the changelog only contains a subset of documentation
-improvements]
+[This release, the changelog only contains a subset of
+documentation improvements]
 
 - Add docs on aliases in
   [Select](https://prql-lang.org/book/reference/stdlib/transforms/select.html)

prqlc/prqlc/tests/integration/dbs/README.md

@@ -47,8 +47,8 @@ Tests are by default run on all the DBs with `SupportLevel::Supported`.
 
 If you also want to test on a DB that is not yet at this support level like
 `MSSQL`, simply add `# mssql:test` on top of your query.\
-If you want to ignore one of the supported DBs like `sqlite`, simply add `# sqlite:skip`
-on top of your query.
+If you want to ignore one of the supported DBs like `sqlite`, simply add
+`# sqlite:skip` on top of your query.
 
 ## Data
 

web/book/src/project/contributing/development.md

@@ -7,8 +7,7 @@ editing, and testing PRQL's compiler code in two minutes:
 
 - Install
   [`rustup` & `cargo`](https://doc.rust-lang.org/cargo/getting-started/installation.html).
-- [Optional but highly recommended] Install `cargo-insta`, our testing
-  framework:
+- [Optional but highly recommended] Install `cargo-insta`, our testing framework:
 
   ```sh
   cargo install cargo-insta
@@ -474,8 +473,9 @@ Currently we release in a semi-automated way:
 
 3. After merging, go to
    [Draft a new release](https://github.com/PRQL/prql/releases/new){{footnote: Only
-       maintainers have access to this page.}}, copy the changelog entry into the
-   release description{{footnote: Unfortunately GitHub's markdown parser
+       maintainers have access to this page.}},
+   copy the changelog entry into the release
+   description{{footnote: Unfortunately GitHub's markdown parser
         interprets linebreaks as newlines. I haven't found a better way of
         editing the markdown to look reasonable than manually editing the text
         or asking LLM to help.}}, enter the tag to be created, and hit

web/book/src/reference/stdlib/date.md

@@ -5,9 +5,9 @@ These are all the functions defined in the `date` module:
 ### `to_text`
 
 Converts a date into a text.\
-Since there are many possible date representations, `to_text` takes a `format` parameter
-that describes thanks to [specifiers](#date--time-format-specifiers) how the date
-or timestamp should be structured.
+Since there are many possible date representations, `to_text` takes a `format`
+parameter that describes thanks to [specifiers](#date--time-format-specifiers)
+how the date or timestamp should be structured.
 
 ```admonish info
 Since all RDBMS have different ways to format dates and times, PRQL **requires an explicit dialect** to be specified

web/website/content/posts/2023-02-02-one-year/_index.md

@@ -30,9 +30,8 @@ Language design & development in the last year have been focused on these areas:
 - fundamentals of how [functions](https://github.com/PRQL/prql/issues/444) and
   pipelines are [evaluated](#define-functional-semantics).
 
-- small quality-of-life language features (e.g. syntax for [f-strings, dates,
-  coalesce operator](https://prql-lang.org/book/reference/syntax/
-  [case](https://github.com/PRQL/prql/issues/504)),
+- small quality-of-life language features (e.g. syntax for [f-strings,
+  dates, coalesce operator](https://prql-lang.org/book/reference/syntax/ [case](https://github.com/PRQL/prql/issues/504)),
 
 PRQL is now in a state where it can greatly improve the developer experience for
 writing complex analytical queries, but it does require a bit of fiddling to set