chore: version 7.12.0

.github/workflows/codeql-analysis.yml

@@ -9,8 +9,8 @@ on:
     - cron: '30 15 * * 4'
 
 env:
-  QT_VERSION: 5.15.2
-  QT_MODULES: qtnetworkauth
+  QT_VERSION: 6.6.3
+  QT_MODULES: qtmultimedia qtimageformats qtnetworkauth qtshadertools
 
 jobs:
   analyze:
@@ -28,32 +28,24 @@ jobs:
 
     steps:
       - name: Checkout repository
-        uses: actions/checkout@v2
-
-      - name: Cache Qt
-        id: cache-qt
-        if: matrix.language == 'cpp'
-        uses: actions/cache@v1
-        with:
-          path: ../Qt
-          key: ${{ runner.os }}-${{ matrix.arch }}-QtCache-${{ env.QT_VERSION }}-${{ env.QT_MODULES }}
+        uses: actions/checkout@v4
 
       - name: Install Qt
         if: matrix.language == 'cpp'
-        uses: jurplel/install-qt-action@v2
+        uses: jurplel/install-qt-action@v3
         with:
-          cached: ${{ steps.cache-qt.outputs.cache-hit }}
+          cache: true
           version: ${{ env.QT_VERSION }}
           modules: ${{ env.QT_MODULES }}
 
       - name: Initialize CodeQL
-        uses: github/codeql-action/init@v1
+        uses: github/codeql-action/init@v2
         with:
           languages: ${{ matrix.language }}
           config-file: ./.github/codeql/codeql-config.yml
 
       - name: Autobuild
-        uses: github/codeql-action/autobuild@v1
+        uses: github/codeql-action/autobuild@v2
 
       - name: Perform CodeQL Analysis
-        uses: github/codeql-action/analyze@v1
+        uses: github/codeql-action/analyze@v2

.github/workflows/docs.yml

@@ -19,29 +19,26 @@ jobs:
 
     steps:
       - name: Checkout
-        uses: actions/checkout@v3
+        uses: actions/checkout@v4
 
       - name: Install Python
-        uses: actions/setup-python@v4
+        uses: actions/setup-python@v5
         with:
           python-version: '3.11'
 
       - run: echo "cache_id=$(date --utc '+%V')" >> $GITHUB_ENV
 
-      - uses: actions/cache@v3
+      - uses: actions/cache@v4
         with:
           key: mkdocs-material-${{ env.cache_id }}
           path: .cache
           restore-keys: |
             mkdocs-material-
 
       - name: Install Python dependencies
-        run: pip install mkdocs-material==9.2.0b3 mkdocs-awesome-pages-plugin mkdocs-macros-plugin mkdocs-git-revision-date-localized-plugin mkdocs-glightbox
+        run: pip install mkdocs-material==9.5 mkdocs-awesome-pages-plugin mkdocs-macros-plugin mkdocs-git-revision-date-localized-plugin mkdocs-glightbox
 
-      - name: Patch blog dates to support datetimes
-        run: sed -i 's|date.fromisoformat|datetime.fromisoformat|' $(pip show mkdocs-material | grep Location | cut -d ' ' -f 2)/material/plugins/blog/plugin.py
-
-      - name: Deploy to Github Pages
+      - name: Deploy to GitHub Pages
         run: mkdocs gh-deploy --force
         env:
           GITHUB_TOKEN: ${{secrets.GITHUB_TOKEN}}

.github/workflows/sources.yml

@@ -16,7 +16,12 @@ jobs:
 
     steps:
       - name: Checkout
-        uses: actions/checkout@v2
+        uses: actions/checkout@v4
+
+      - name: Install Node.js
+        uses: actions/setup-node@v4
+        with:
+          node-version: 16
 
       - name: Install sites dependencies
         working-directory: src/sites
@@ -33,7 +38,7 @@ jobs:
         run: ./scripts/package-sources.sh
 
       - name: Upload artifacts
-        uses: actions/upload-artifact@v2
+        uses: actions/upload-artifact@v4
         with:
           name: sources
           path: |
@@ -48,13 +53,13 @@ jobs:
 
     steps:
       - name: Download artifacts
-        uses: actions/download-artifact@v2
+        uses: actions/download-artifact@v4
         with:
           name: sources
 
       - name: Get date for body
         id: date
-        run: echo "::set-output name=date::$(date +'%Y-%m-%d %H:%M:%S %Z')"
+        run: echo "date=$(date +'%Y-%m-%d %H:%M:%S %Z')" >> $GITHUB_OUTPUT
 
       - name: Upload result
         uses: ncipollo/release-action@v1
@@ -67,12 +72,12 @@ jobs:
           prerelease: true
           artifacts: metadata.json,sources_packages/*.zip
           body: |
-            Automatically uploaded by Github actions.
+            Automatically uploaded by GitHub actions.
 
             **Head:** ${{ github.sha }}
             **Date:** ${{ steps.date.outputs.date }}
 
-      - uses: geekyeggo/delete-artifact@v1
+      - uses: geekyeggo/delete-artifact@v4
         with:
           failOnError: false
           name: sources

.github/workflows/tag-databases.yml

@@ -12,7 +12,12 @@ jobs:
 
     steps:
       - name: Checkout
-        uses: actions/checkout@v2
+        uses: actions/checkout@v4
+
+      - name: Install dependencies
+        run: |
+          sudo apt update
+          sudo apt install fuse libopengl0 libegl1
 
       - name: Download Nightly
         uses: dsaltares/fetch-gh-release-asset@master
@@ -25,14 +30,10 @@ jobs:
         run: |
           mv Grabber_nightly-x86_64.AppImage Grabber.AppImage
           sudo chmod +x Grabber.AppImage
-          ./Grabber.AppImage --appimage-extract
-          cp -r squashfs-root/usr/share/Grabber/* .
           touch settings.ini
 
       - name: Generate tag databases
-        uses: GabrielBB/xvfb-action@v1
-        with:
-          run: ./scripts/generate-tag-databases.sh
+        run: QT_QPA_PLATFORM=offscreen ./scripts/generate-tag-databases.sh
 
       - name: Get date for release body
         id: date

CONTRIBUTING.md

@@ -18,7 +18,7 @@ This section guides you through submitting an enhancement suggestion, including
 
 Start by [a search](https://github.com/Bionus/imgbrd-grabber/issues?q=is%3Aissue) to see if your idea was not already suggested. If so, you add information to it if you feel it could help, bump it or simply add a :+1: reaction to the original post.
 
-After you've determined that your idea have not already been suggested, create an issue on Github and provide the following information:
+After you've determined that your idea have not already been suggested, create an issue on GitHub and provide the following information:
 
 * **Use a clear and descriptive title** for the issue to identify the suggestion.
 * **Provide a step-by-step description of the suggested enhancement** in as many details as possible.
@@ -28,11 +28,11 @@ After you've determined that your idea have not already been suggested, create a
 
 ## Reporting Bugs
 
-Following these guidelines helps maintainers and the community understand your report, reproduce the behavior, and find related reports, which in turn helps fixing the issue you faced.
+Following these guidelines helps maintainers and the community understand your report, reproduce the behavior, and find related reports, which in turn helps to fix the issue you faced.
 
 Start by [a search](https://github.com/Bionus/imgbrd-grabber/issues?q=is%3Aissue) to see if the problem has already been reported. If so, you add information to it if you feel it could help.
 
-After you've determined that your bug have not already been reported, create an issue on Github and provide the following information:
+After you've determined that your bug have not already been reported, create an issue on GitHub and provide the following information:
 
 * **Use a clear and descriptive title** for the issue to identify the problem.
 * **Describe the exact steps which reproduce the problem** in as many details as possible. **Don't just say what you did, but explain how you did it**.
@@ -53,14 +53,14 @@ Include details about your configuration and environment:
 * **Which version of Grabber are you using?** You can get the exact version by going in the `About` menu and clicking `About Grabber`.
 * **What's the name and version of the OS you're using**?
 * **Are you running Grabber in a virtual machine?** If so, which VM software are you using and which operating systems and versions are used for the host and the guest?
-* **Provide your `main.log` file** to see if any obvious error occured.
+* **Provide your `main.log` file** to see if any obvious error occurred.
 * **Provide your `settings.ini` file** will greatly help maintainers reproduce your problem if it may be caused by your configuration.
 
 Note that both `main.log` and `settings.ini` files can be found in `C:/Users/%USERNAME%/AppData/Local/Bionus/Grabber` in Windows, and in the installation directory on Linux.
 
 ## Reporting crashes
 
-Start by follwing the [Reporting Bugs](#reporting-bugs) guidelines. Additionally, a few more information will be required:
+Start by following the [Reporting Bugs](#reporting-bugs) guidelines. Additionally, a few more information will be required:
 
 * **Provide the crash dump** that was linked by the Crash Reporter tool.
 * **If the crash occured during a download, make sure to provide said download**. You can simply provide the `.igl` file that Grabber can generate by clicking the `Save` button of the `Downloads` tab.
@@ -70,10 +70,10 @@ Start by follwing the [Reporting Bugs](#reporting-bugs) guidelines. Additionally
 If you want to ensure your pull request is merged in a timely manner, it is better to follow a few guidelines:
 
 * **Use an explicit commit message**, to help maintainers understand what your pull request is about.
-* **If you changed the code, make sure the program still passes the tests**. They are run automatically on Github Actions in any case, but your pull request won't be merged if the tests are broken.
+* **If you changed the code, make sure the program still passes the tests**. They are run automatically on GitHub Actions in any case, but your pull request won't be merged if the tests are broken.
 * **Follow the coding style of the project**. There is no fixed coding style, but please try to adapt to the code of the project.
 * **Document the code** if what you added is not obvious.
-* **If your pull request is complex, add a detailed description**. You can either add it in your commit message or in the Github discussion.
+* **If your pull request is complex, add a detailed description**. You can either add it in your commit message or in the GitHub discussion.
 
 ## Translations