Merge branch 'main' into feat/docs/clean-frontmatters-WDOC-WDOC-1102

Author: iManu

.github/labeler.yml

@@ -11,4 +11,4 @@
 
 'type: dependencies':
   - package.json
-  - yarn.lock
+  - pnpm-lock.yaml

.husky/commit-msg

@@ -1,4 +1,4 @@
 #!/bin/sh
 . "$(dirname "$0")/_/husky.sh"
 
-yarn commitlint -e && echo "\nHey! Did you Val(e)date your changes? 💡🤡\n"
+pnpm commitlint -e && echo "\nHey! Did you Val(e)date your changes? 💡🤡\n"

.prettierignore

@@ -1,4 +1,4 @@
 node_modules/
 package.json
-yarn.lock
+pnpm-lock.yaml
 *.mdx

bin/check-pre-commit

@@ -2,6 +2,6 @@
 
 [[ $(bin/count-invalid-slugs) == "0" ]] && \
 [ ! -d node_modules/ ] && echo "⚠️ You need to install node_modules first" && exit 1; \
-yarn lint-staged || \
+pnpm lint-staged || \
 (echo "💔 Slug error(s):" && bin/list-invalid-slugs \ 
 echo "⚠️ You must fix slugs in 'menu/navigation.json' before commit"; exit 1)

changelog/july2025/2025-07-08-transactional-email-added-ipv6-support-enabled-on-smtp-.mdx

@@ -0,0 +1,10 @@
+---
+title: IPv6 support enabled on SMTP proxy
+status: added
+date: 2025-07-08
+category: domains-and-webhosting
+product: transactional-email
+---
+
+IPv6 is now enabled on the SMTP proxy for our TEM service.
+No action is required on your side, as the system will automatically use IPv6 when available, without changing the `smtp.tem.scaleway.com` hostname. 

docs/CONTRIBUTING.md

@@ -127,7 +127,7 @@ git clone [email protected]:scaleway/docs-content.git | bash -s -- cd docs-content
 
 Helpful pre-commit commands:
 
-- `yarn check-slugs` Output slugs that are not kebab-case well formatted.
+- `pnpm check-slugs` Output slugs that are not kebab-case well formatted.
 
 ### Commit conventions
 

macros/audit-trail/account-endpoints.mdx

@@ -0,0 +1,24 @@
+---
+macro: adt-account-endpoints
+---
+
+<Accordion>
+  ## Account
+
+  ### Account supported endpoints
+
+    The following [Account](/account/) endpoints are supported and will be logged in Audit Trail:
+
+    - SendPhoneValidation (`POST /account/v3/phone-validations`)
+    - ConfirmPhoneValidation (`POST /account/v3/phone-validations/{phone_validation_id}/confirm`)
+    - UpdateUserPreferences (`PATCH /account/v3/users/{user_id}/preferences`)
+    - CreateMFAOTP (`POST /account/v3/mfa/otps`)
+    - DeleteMFAOTP (`DELETE /account/v3/mfa/otps/{mfa_otp_id}`)
+    - ValidateMFAOTP (`POST /account/v3/mfa/otps/{mfa_otp_id}/validate`)
+    - UpdateUser (`PATCH /account/v3/users/{user_id}`)
+    - ChangeUserEmail (`POST /account/v3/users/{user_id}/change-email`)
+    - ChangeUserPassword (`POST /account/v3/users/{user_id}/change-password`)
+    - ChangeSupportPlan (`POST /account/v3/organizations/{organization_id}/support-plans`)
+    - CloseOrganization (`POST /account/v3/organizations/{organization_id}/close`)
+    - SetPicture (`PUT /account/v3/organizations/{organization_id}/picture`)
+</Accordion>

macros/audit-trail/iam-endpoints.mdx

@@ -7,7 +7,7 @@ macro: adt-iam-endpoints
 
   ### IAM supported endpoints
 
-    The following IAM endpoints are supported and will be logged in Audit Trail:
+    The following [IAM](/iam/) endpoints are supported and will be logged in Audit Trail:
 
     - CreateSSHKey (`POST /iam/v1alpha1/ssh-keys`)
     - UpdateSSHKey (`PATCH /iam/v1alpha1/ssh-keys/{ssh_key_id}`)

macros/audit-trail/key-manager-endpoints.mdx

@@ -7,7 +7,7 @@ macro: adt-key-manager-endpoints
 
   ### Key Manager supported endpoints
 
-    The following Key Manager endpoints are supported and will be logged in Audit Trail:
+    The following [Key Manager](/key-manager/) endpoints are supported and will be logged in Audit Trail:
 
     - CreateKey (`POST /key-manager/v1alpha1/regions/{region}/keys`)
     - UpdateKey (`PATCH /key-manager/v1alpha1/regions/{region}/keys/{key_id}`)

macros/audit-trail/kubernetes-endpoints.mdx

@@ -7,7 +7,7 @@ macro: adt-kubernetes-endpoints
 
   ### Kubernetes supported endpoints
 
-    The following Kubernetes endpoints are supported and will be logged in Audit Trail:
+    The following [Kubernetes](/kubernetes/) endpoints are supported and will be logged in Audit Trail:
 
     - Create a new cluster (`POST /k8s/v1/regions/{region}/clusters`)
     - Update a cluster (`PATCH /k8s/v1/regions/{region}/clusters/{cluster_id}`)