chore(deps): update dependency prettier to v3.6.2 (#3519)

renovate[bot] · vasfvitor · web-flow · commit bc695aade874 · 2025-09-25T22:51:49.000-03:00
Co-authored-by: renovate[bot] &lt;29139614+renovate[bot]@users.noreply.github.com&gt;
Co-authored-by: Ayres Vitor &lt;gitkey@virtuaires.com.br&gt;
diff --git a/pnpm-lock.yaml b/pnpm-lock.yaml
diff --git a/src/content/docs/distribute/Sign/windows.mdx b/src/content/docs/distribute/Sign/windows.mdx
@@ -47,9 +47,7 @@ There are a few things we have to do to get Windows prepared for code signing. T
 <Steps>
 
 1. #### Convert your `.cer` to `.pfx`
-
    - You will need the following:
-
      - certificate file (mine is `cert.cer`)
      - private key file (mine is `private-key.key`)
 
@@ -60,15 +58,13 @@ There are a few things we have to do to get Windows prepared for code signing. T
    - You should be prompted to enter an export password **DON'T FORGET IT!**
 
 2. #### Import your `.pfx` file into the keystore.
-
    - We now need to import our `.pfx` file.
 
    - Assign your export password to a variable using `$WINDOWS_PFX_PASSWORD = 'MYPASSWORD'`
 
    - Now Import the certificate using `Import-PfxCertificate -FilePath certificate.pfx -CertStoreLocation Cert:\CurrentUser\My -Password (ConvertTo-SecureString -String $WINDOWS_PFX_PASSWORD -Force -AsPlainText)`
 
 3. #### Prepare Variables
-
    - Start ➡️ `certmgr.msc` to open Personal Certificate Management, then open Personal/Certificates.
 
    - Find the certificate we just imported and double-click on it, then click on the Details tab.
@@ -129,7 +125,6 @@ The secrets we used are as follows
 #### Workflow Modifications
 
 1. We need to add a step in the workflow to import the certificate into the Windows environment. This workflow accomplishes the following
-
    1. Assign GitHub secrets to environment variables
    2. Create a new `certificate` directory
    3. Import `WINDOWS_CERTIFICATE` into tempCert.txt
@@ -307,21 +302,16 @@ You need to install [trusted-signing-cli](https://github.com/Levminer/trusted-si
 <Steps>
 
 1. #### Install trusted-signing-cli
-
    - `cargo install trusted-signing-cli`
 
 2. #### Configure environment variables
-
    - trusted-signing-cli needs the following environment variables to be set, don't forget to add these as Github Actions [secrets](https://docs.github.com/en/actions/security-for-github-actions/security-guides/using-secrets-in-github-actions):
-
      - `AZURE_CLIENT_ID`: The client ID of your [App Registration](https://melatonin.dev/blog/code-signing-on-windows-with-azure-trusted-signing/#step-4-create-app-registration-user-credentials)
      - `AZURE_CLIENT_SECRET`: The client secret of [App Registration](https://melatonin.dev/blog/code-signing-on-windows-with-azure-trusted-signing/#step-4-create-app-registration-user-credentials)
      - `AZURE_TENANT_ID`: The tenant ID of your Azure directory, you can also get this from your [App Registration](https://melatonin.dev/blog/code-signing-on-windows-with-azure-trusted-signing/#step-4-create-app-registration-user-credentials)
 
 3. ### Modify your `tauri.conf.json` file
-
    - You can modify your `tauri.conf.json` or you can create a specific config file for Windows. Replace the URL and the certificate name with your own values.
-
      - -e: The endpoint of your Azure Code Signing account
      - -a: The name of your Azure Code Signing Account
      - -c: The name of your Certificate profile inside your Azure Code Signing Account
diff --git a/src/content/docs/distribute/debian.mdx b/src/content/docs/distribute/debian.mdx
@@ -54,12 +54,10 @@ Manual compilation is suitable when you don't need to compile your application f
 <Steps>
 
 1. #### Install Rust targets for your desired architecture
-
    - For ARMv7 (32-bit): `rustup target add armv7-unknown-linux-gnueabihf`
    - For ARMv8 (ARM64, 64-bit): `rustup target add aarch64-unknown-linux-gnu`
 
 2. #### Install the corresponding linker for your chosen architecture
-
    - For ARMv7: `sudo apt install gcc-arm-linux-gnueabihf`
    - For ARMv8 (ARM64): `sudo apt install gcc-aarch64-linux-gnu`
 
@@ -74,7 +72,6 @@ Manual compilation is suitable when you don't need to compile your application f
    ```
 
 4. #### Enable the respective architecture in the package manager
-
    - For ARMv7: `sudo dpkg --add-architecture armhf`
    - For ARMv8 (ARM64): `sudo dpkg --add-architecture arm64`
 
@@ -159,14 +156,12 @@ Manual compilation is suitable when you don't need to compile your application f
 6. #### Update the package information: `sudo apt-get update && sudo apt-get upgrade -y`
 
 7. #### Install the required webkitgtk library for your chosen architecture
-
    - For ARMv7: `sudo apt install libwebkit2gtk-4.1-dev:armhf`
    - For ARMv8 (ARM64): `sudo apt install libwebkit2gtk-4.1-dev:arm64`
 
 8. #### Install OpenSSL or use a vendored version
 
    This is not always required so you may want to proceed first and check if you see errors like `Failed to find OpenSSL development headers`.
-
    - Either install the development headers system-wide:
      - For ARMv7: `sudo apt install libssl-dev:armhf`
      - For ARMv8 (ARM64): `sudo apt install libssl-dev:arm64`
@@ -177,12 +172,10 @@ Manual compilation is suitable when you don't need to compile your application f
    ```
 
 9. #### Set the `PKG_CONFIG_SYSROOT_DIR` to the appropriate directory based on your chosen architecture
-
    - For ARMv7: `export PKG_CONFIG_SYSROOT_DIR=/usr/arm-linux-gnueabihf/`
    - For ARMv8 (ARM64): `export PKG_CONFIG_SYSROOT_DIR=/usr/aarch64-linux-gnu/`
 
 10. #### Build the app for your desired ARM version
-
     - For ARMv7: cargo tauri build --target armv7-unknown-linux-gnueabihf
     - For ARMv8 (ARM64): cargo tauri build --target aarch64-unknown-linux-gnu
 
diff --git a/src/content/docs/distribute/rpm.mdx b/src/content/docs/distribute/rpm.mdx
@@ -366,12 +366,10 @@ Manual compilation is suitable when you don't need to compile your application f
 <Steps>
 
 1. #### Install Rust targets for your desired architecture
-
    - For ARMv7 (32-bit): `rustup target add armv7-unknown-linux-gnueabihf`
    - For ARMv8 (ARM64, 64-bit): `rustup target add aarch64-unknown-linux-gnu`
 
 2. #### Install the corresponding linker for your chosen architecture
-
    - For ARMv7: `sudo apt install gcc-arm-linux-gnueabihf`
    - For ARMv8 (ARM64): `sudo apt install gcc-aarch64-linux-gnu`
 
@@ -386,7 +384,6 @@ Manual compilation is suitable when you don't need to compile your application f
    ```
 
 4. #### Enable the respective architecture in the package manager
-
    - For ARMv7: `sudo dpkg --add-architecture armhf`
    - For ARMv8 (ARM64): `sudo dpkg --add-architecture arm64`
 
@@ -471,14 +468,12 @@ Manual compilation is suitable when you don't need to compile your application f
 6. #### Update the package information: `sudo apt-get update && sudo apt-get upgrade -y`
 
 7. #### Install the required webkitgtk library for your chosen architecture
-
    - For ARMv7: `sudo apt install libwebkit2gtk-4.1-dev:armhf`
    - For ARMv8 (ARM64): `sudo apt install libwebkit2gtk-4.1-dev:arm64`
 
 8. #### Install OpenSSL or use a vendored version
 
    This is not always required so you may want to proceed first and check if you see errors like `Failed to find OpenSSL development headers`.
-
    - Either install the development headers system-wide:
      - For ARMv7: `sudo apt install libssl-dev:armhf`
      - For ARMv8 (ARM64): `sudo apt install libssl-dev:arm64`
@@ -489,12 +484,10 @@ Manual compilation is suitable when you don't need to compile your application f
    ```
 
 9. #### Set the `PKG_CONFIG_SYSROOT_DIR` to the appropriate directory based on your chosen architecture
-
    - For ARMv7: `export PKG_CONFIG_SYSROOT_DIR=/usr/arm-linux-gnueabihf/`
    - For ARMv8 (ARM64): `export PKG_CONFIG_SYSROOT_DIR=/usr/aarch64-linux-gnu/`
 
 10. #### Build the app for your desired ARM version
-
     - For ARMv7: cargo tauri build --target armv7-unknown-linux-gnueabihf
     - For ARMv8 (ARM64): cargo tauri build --target aarch64-unknown-linux-gnu
 
diff --git a/src/content/docs/zh-cn/distribute/Sign/android.mdx b/src/content/docs/zh-cn/distribute/Sign/android.mdx
@@ -69,7 +69,6 @@ import { Steps } from '@astrojs/starlight/components';
 4.  在 Gradle 中配置签名
 
     通过编辑 `[project]/src-tauri/gen/android/app/build.gradle.kts` 文件，配置 gradle 在发布模式下构建应用时使用您的上传密钥。
-
     1.  在文件开头添加所需的导入。
 
         ```kotlin
diff --git a/src/content/docs/zh-cn/distribute/Sign/windows.mdx b/src/content/docs/zh-cn/distribute/Sign/windows.mdx
@@ -44,9 +44,7 @@ import { Steps } from '@astrojs/starlight/components';
 <Steps>
 
 1. #### 将 `.cer` 转换为 `.pfx`
-
    - 你将需要以下内容：
-
      - 证书文件 (我是 `cert.cer`)
      - 私钥文件 (我是 `private-key.key`)
 
@@ -57,15 +55,13 @@ import { Steps } from '@astrojs/starlight/components';
    - 你应该被提示输入导出密码**别忘了!**
 
 2. #### 将你的 `.pfx` 文件导入密钥库。
-
    - 我们现在需要导入我们的 `.pfx` 文件。
 
    - 使用 `$WINDOWS_PFX_PASSWORD = 'MYPASSWORD'` 将您的导出密码分配到一个变量
 
    - 现在使用 `Import-PfxCertificate -FilePath certificate.pfx -CertStoreLocation Cert:\CurrentUser\My -Password (ConvertTo-SecureString -String $WINDOWS_PFX_PASSWORD -Force -AsPlainText)` 导入证书。
 
 3. #### 准备变量
-
    - 开始 ➡️ 打开 `certmgr.msc` 以打开个人证书管理，然后打开"个人/证书"。
 
    - 找到刚导入的证书，双击它，然后点击 Details 选项卡。
@@ -126,7 +122,6 @@ info: "Done Adding Additional Store\r\nSuccessfully signed: APPLICATION FILE PAT
 #### 工作流的修改
 
 1. 我们需要在工作流中添加一个步骤来将证书导入 Windows 环境。该工作流完成以下工作。
-
    1. 将 GitHub 密钥分配给环境变量
    2. 创建一个新的 `certificate` 目录
    3. 将 `WINDOWS_CERTIFICATE` 导入到 tempCert.txt 文件中
