New translation batch for ja (#31154)

translations/ja-JP/content/actions/hosting-your-own-runners/about-self-hosted-runners.md

@@ -123,7 +123,7 @@ The following operating systems are supported for the self-hosted runner applica
 The following processor architectures are supported for the self-hosted runner application.
 
 - `x64` - Linux, macOS, Windows.
-- `ARM64` - Linux, macOS.
+- `ARM64` - Linux{% ifversion actions-macos-arm %}, macOS{% endif %}.
 - `ARM32` - Linux only.
 
 {% ifversion ghes %}

translations/ja-JP/content/actions/learn-github-actions/contexts.md

@@ -718,7 +718,7 @@ jobs:
 
 ## `needs` context
 
-The `needs` context contains outputs from all jobs that are defined as a dependency of the current job. For more information on defining job dependencies, see "[Workflow syntax for {% data variables.product.prodname_actions %}](/actions/learn-github-actions/workflow-syntax-for-github-actions#jobsjob_idneeds)."
+The `needs` context contains outputs from all jobs that are defined as a direct dependency of the current job. Note that this doesn't include implicitly dependent jobs (for example, dependent jobs of a dependent job). For more information on defining job dependencies, see "[Workflow syntax for {% data variables.product.prodname_actions %}](/actions/learn-github-actions/workflow-syntax-for-github-actions#jobsjob_idneeds)."
 
 | Property name | Type | Description |
 |---------------|------|-------------|

translations/ja-JP/content/code-security/dependabot/dependabot-version-updates/configuration-options-for-the-dependabot.yml-file.md

@@ -77,19 +77,19 @@ updates:
   - package-ecosystem: "github-actions"
     directory: "/"
     schedule:
-      interval: "daily"
+      interval: "weekly"
 
   # Maintain dependencies for npm
   - package-ecosystem: "npm"
     directory: "/"
     schedule:
-      interval: "daily"
+      interval: "weekly"
 
   # Maintain dependencies for Composer
   - package-ecosystem: "composer"
     directory: "/"
     schedule:
-      interval: "daily"
+      interval: "weekly"
 ```
 
 ### `directory`
@@ -105,29 +105,31 @@ updates:
     # Files stored in repository root
     directory: "/"
     schedule:
-      interval: "daily"
+      interval: "weekly"
 
   - package-ecosystem: "npm"
     # Files stored in `app` directory
     directory: "/app"
     schedule:
-      interval: "daily"
+      interval: "weekly"
 
   - package-ecosystem: "github-actions"
     # Workflow files stored in the
     # default location of `.github/workflows`
     directory: "/"
     schedule:
-      interval: "daily"
+      interval: "weekly"
 ```
 
 ### `schedule.interval`
 
 **Required**. You must define how often to check for new versions for each package manager. By default, {% data variables.product.prodname_dependabot %} randomly assigns a time to apply all the updates in the configuration file. To set a specific time, you can use [`schedule.time`](#scheduletime) and [`schedule.timezone`](#scheduletimezone).
 
-- `daily`—runs on every weekday, Monday to Friday.
-- `weekly`—runs once each week. By default, this is on Monday. To modify this, use [`schedule.day`](#scheduleday).
-- `monthly`—runs once each month. This is on the first day of the month.
+| Interval types | Frequency |
+|----------------|-----------|
+| `daily` | Runs on every weekday, Monday to Friday.|
+| `weekly`| Runs once each week. By default, this is on Monday. To modify this, use [`schedule.day`](#scheduleday).|
+| `monthly` | Runs once each month. This is on the first day of the month. |
 
 ```yaml
 # Set update schedule for each package manager
@@ -179,7 +181,7 @@ updates:
   - package-ecosystem: "npm"
     directory: "/"
     schedule:
-      interval: "daily"
+      interval: "weekly"
     allow:
       # Allow updates for Lodash
       - dependency-name: "lodash"
@@ -189,7 +191,7 @@ updates:
   - package-ecosystem: "composer"
     directory: "/"
     schedule:
-      interval: "daily"
+      interval: "weekly"
     allow:
       # Allow both direct and indirect updates for all packages
       - dependency-type: "all"
@@ -197,7 +199,7 @@ updates:
   - package-ecosystem: "pip"
     directory: "/"
     schedule:
-      interval: "daily"
+      interval: "weekly"
     allow:
       # Allow only direct updates for
       # Django and any packages starting "django"
@@ -222,7 +224,7 @@ updates:
   - package-ecosystem: "npm"
     directory: "/"
     schedule:
-      interval: "daily"
+      interval: "weekly"
     # Add assignees
     assignees:
       - "octocat"
@@ -254,7 +256,7 @@ updates:
   - package-ecosystem: "npm"
     directory: "/"
     schedule:
-      interval: "daily"
+      interval: "weekly"
     commit-message:
       # Prefix all commit messages with "npm"
       prefix: "npm"
@@ -262,7 +264,7 @@ updates:
   - package-ecosystem: "composer"
     directory: "/"
     schedule:
-      interval: "daily"
+      interval: "weekly"
     # Prefix all commit messages with "Composer"
     # include a list of updated dependencies
     commit-message:
@@ -272,7 +274,7 @@ updates:
   - package-ecosystem: "pip"
     directory: "/"
     schedule:
-      interval: "daily"
+      interval: "weekly"
     # Include a list of updated dependencies
     # with a prefix determined by the dependency group
     commit-message:
@@ -318,7 +320,7 @@ updates:
   - package-ecosystem: "npm"
     directory: "/"
     schedule:
-      interval: "daily"
+      interval: "weekly"
     ignore:
       - dependency-name: "express"
         # For Express, ignore all updates for version 4 and 5
@@ -389,7 +391,7 @@ updates:
   - package-ecosystem: "npm"
     directory: "/"
     schedule:
-      interval: "daily"
+      interval: "weekly"
     # Specify labels for npm pull requests
     labels:
       - "npm"
@@ -410,7 +412,7 @@ updates:
   - package-ecosystem: "npm"
     directory: "/"
     schedule:
-      interval: "daily"
+      interval: "weekly"
     # Associate pull requests with milestone "4"
     milestone: 4
 ```
@@ -429,14 +431,14 @@ updates:
   - package-ecosystem: "npm"
     directory: "/"
     schedule:
-      interval: "daily"
+      interval: "weekly"
     # Disable version updates for npm dependencies
     open-pull-requests-limit: 0
 
   - package-ecosystem: "pip"
     directory: "/"
     schedule:
-      interval: "daily"
+      interval: "weekly"
     # Allow up to 10 open pull requests for pip dependencies
     open-pull-requests-limit: 10
 ```
@@ -457,7 +459,7 @@ updates:
   - package-ecosystem: "npm"
     directory: "/"
     schedule:
-      interval: "daily"
+      interval: "weekly"
     pull-request-branch-name:
       # Separate sections of the branch name with a hyphen
       # for example, `dependabot-npm_and_yarn-next_js-acorn-6.4.1`
@@ -483,7 +485,7 @@ updates:
   - package-ecosystem: "npm"
     directory: "/"
     schedule:
-      interval: "daily"
+      interval: "weekly"
     # Disable rebasing for npm pull requests
     rebase-strategy: "disabled"
 ```
@@ -535,7 +537,7 @@ updates:
   - package-ecosystem: "pip"
     directory: "/"
     schedule:
-      interval: "daily"
+      interval: "weekly"
     # Add reviewers
     reviewers:
       - "octocat"
@@ -581,7 +583,7 @@ updates:
   - package-ecosystem: "npm"
     directory: "/"
     schedule:
-      interval: "daily"
+      interval: "weekly"
       # Check for npm updates at 9am UTC
       time: "09:00"
 ```
@@ -598,7 +600,7 @@ updates:
   - package-ecosystem: "npm"
     directory: "/"
     schedule:
-      interval: "daily"
+      interval: "weekly"
       time: "09:00"
       # Use Japan Standard Time (UTC +09:00)
       timezone: "Asia/Tokyo"
@@ -616,7 +618,7 @@ updates:
   - package-ecosystem: "pip"
     directory: "/"
     schedule:
-      interval: "daily"
+      interval: "weekly"
     # Raise pull requests for version updates
     # to pip against the `develop` branch
     target-branch: "develop"
@@ -689,7 +691,7 @@ updates:
   - package-ecosystem: "npm"
     directory: "/"
     schedule:
-      interval: "daily"
+      interval: "weekly"
     # Update the npm manifest file to relax
     # the version requirements
     versioning-strategy: widen
@@ -697,7 +699,7 @@ updates:
   - package-ecosystem: "composer"
     directory: "/"
     schedule:
-      interval: "daily"
+      interval: "weekly"
     # Increase the version requirements for Composer
     # only when required
     versioning-strategy: increase-if-necessary
@@ -705,7 +707,7 @@ updates:
   - package-ecosystem: "pip"
     directory: "/"
     schedule:
-      interval: "daily"
+      interval: "weekly"
     # Only allow updates to the lockfile for pip and
     # ignore any version updates that affect the manifest
     versioning-strategy: lockfile-only
@@ -993,6 +995,6 @@ updates:{% ifversion fpt or ghec or ghes > 3.5 %}
   - package-ecosystem: "pub"{% endif %}
     directory: "/"
     schedule:
-      interval: "daily"
+      interval: "weekly"
 ```
 {% endif %}

translations/ja-JP/content/get-started/writing-on-github/working-with-advanced-formatting/attaching-files.md

@@ -22,6 +22,8 @@ To attach a file to an issue or pull request conversation, drag and drop it into
 
 ![Select attachments from computer](/assets/images/help/pull_requests/select-bar.png)
 
+When you attach a file, it is uploaded immediately to {% data variables.product.product_name %} and the text field is updated to show the anonymized URL for the file. {% ifversion fpt or ghec %}For more information on anonymized URLs see "[About anonymized URLs](/github/authenticating-to-github/about-anonymized-urls)".{% endif %}
+
 {% tip %}
 
 **Tip:** In many browsers, you can copy-and-paste images directly into the box.

translations/ja-JP/content/rest/overview/permissions-required-for-github-apps.md

@@ -702,10 +702,10 @@ Issues and pull requests are closely related. For more information, see "[List i
 
 ## Permission on "pages"
 
+GitHub Pages can only be created or unpublished by a repository owner or administrator.
+
 - [`GET /repos/:owner/:repo/pages`](/rest/reference/pages#get-a-github-pages-site) (:read)
-- [`POST /repos/:owner/:repo/pages`](/rest/reference/pages#create-a-github-pages-site) (:write)
 - [`PUT /repos/:owner/:repo/pages`](/rest/reference/pages#update-information-about-a-github-pages-site) (:write)
-- [`DELETE /repos/:owner/:repo/pages`](/rest/reference/pages#delete-a-github-pages-site) (:write)
 - [`GET /repos/:owner/:repo/pages/builds`](/rest/reference/pages#list-github-pages-builds) (:read)
 - [`POST /repos/:owner/:repo/pages/builds`](/rest/reference/pages#request-a-github-pages-build) (:write)
 - [`GET /repos/:owner/:repo/pages/builds/:build_id`](/rest/reference/pages#get-github-pages-build) (:read)

translations/ja-JP/data/release-notes/enterprise-server/3-6/1.yml

@@ -1,33 +1,41 @@
 date: '2022-08-30'
 sections:
   bugs:
-    - 一時的なアクセスのためにリポジトリのロックを解除した後、サイト管理者はリポジトリのセキュリティ製品の設定を管理できませんでした。 
-    - 管理コンソールと `/home/admin/.ssh/authorized_keys` ファイルの両方に、重複する管理 SSH キーが表示されることがありました。
-    - "<code>http(s)://<ホスト名>/stafftools/users/<ユーザー名>/admin</code> の個人ユーザー向けサイト管理者ページに、GitHub Enterprise Server には意図されていない機能が含まれました。"  
-    - 場合によっては、`ghe-cluster-config-apply` を実行して空の構成をクラスターの既存のノードにレプリケートできました。 
-    - "`ghe-config-apply` で開始された構成の実行が、完了しないこと、または`Container count mismatch` エラーを返すことがありました。" 
-    - GitHub Enterprise Server インスタンス上の自己署名 TLS 証明書を更新した後、Web インターフェイスの一部のページの UI 要素が表示されませんでした。 
-    - 場合によっては、スレッドセーフではないにも関わらず同時に使われたライブラリのため、バックグラウンド タスクが停止することがありました。
-    - Web インターフェイスの上部のサイト管理者バーに含まれる、現在実行中のアプリケーションのバージョンに対する SHA へのリンクが、壊れていました。
-    - Organization 所有者は、ディスカッションの作成に必要なアクセスのレベルを設定できませんでした。 
-    - ディスカッションのユーザーは、GitHub.com のコミュニティ ガイドラインに誤って誘導されました。
-    - ユーザーは、ディスカッションを作成する前にメールを検証するよう、誤って指示されることがありました。
-    - サイト管理者が GitHub Enterprise Server 3.4 に直接アップグレードしなかった場合、GitHub Advanced Security のお客様に対するシークレット スキャンからのアラートが、Web UI と REST API に表示されませんでした。現在は、アラートが表示されます。
+    - After unlocking a repository for temporary access, a site administrator was unable to manage settings for security products in the repository. 
+    - Duplicate administrative SSH keys could appear in both the Management Console and the `/home/admin/.ssh/authorized_keys` file.
+    - The site admin page for individual users at <code>http(s)://<em>HOSTNAME</em>/stafftools/users/<em>USERNAME</em>/admin</code> contained functionality not intended for GitHub Enterprise Server.  
+    - In some cases, running `ghe-cluster-config-apply` could replicate an empty configuration to existing nodes in a cluster. 
+    - In some cases, configuration runs started with `ghe-config-apply` did not complete, or returned a `Container count mismatch` error. 
+    - After updating a self-signed TLS certificate on a GitHub Enterprise Server instance, UI elements on some pages in the web interface did not appear. 
+    - In some cases, background tasks could stall due to a library that was used concurrently despite not being thread-safe.
+    - The site admin bar at the top of the web interface contained a broken link to the SHA for the currently running version of the application.
+    - Organization owners were unable to set the level of access required to create discussions. 
+    - Discussions users were incorrectly directed to the community guidelines for GitHub.com.
+    - In some cases, users were incorrectly instructed to verify their email before creating a discussion.
+    - Alerts from secret scanning for GitHub Advanced Security customers were missing in the web UI and REST API if a site administrator did not upgrade directly to GitHub Enterprise Server 3.4. The alerts are now visible.
   changes:
-    - "並列化されたログ サニタイズの結果、サポート バンドルの生成が速くなっています。サポート バンドルについて詳しくは、「[GitHub Support へのデータの提供](/support/contacting-github-support/providing-data-to-github-support)」をご覧ください。"
-    - "`organization` または `org` ルートを含む API が、Organization のスラッグまたは ID を受け取るようになりました。以前の API はスラッグのみを受け取っており、そのために GitHub Advanced Security エンドポイントの `Link` ヘッダーにアクセスできませんでした。詳しくは、REST API のドキュメントの「[組織](https://docs.github.com/rest/orgs/orgs)」をご覧ください。" 
-    - "Enterprise の監査ログに含まれるユーザー生成イベントが増えました (`project.create` など)。REST API からも、追加のユーザー生成イベントが返されます (`repo.create` など)。詳しくは、「[企業の監査ログにアクセスする](/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/accessing-the-audit-log-for-your-enterprise)」と「[Enterprise 用の監査ログ API の使用](/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/using-the-audit-log-api-for-your-enterprise#querying-the-audit-log-rest-api)」をご覧ください。"
-    - "キャッシュ レプリカが、最近更新されたリポジトリでの一部の Git 操作を拒否することがありました。リポジトリのキャッシュについて詳しくは、「[リポジトリのキャッシュについて](/admin/enterprise-management/caching-repositories/about-repository-caching)」をご覧ください。" 
-    - "REST API を使って閉じることができるよう、グローバル通知バナーを構成できるようになりました。詳しくは、「[Enterprise のユーザメッセージをカスタマイズする](/admin/user-management/managing-users-in-your-enterprise/customizing-user-messages-for-your-enterprise#creating-a-global-announcement-banner)」をご覧ください。" 
+    - Generation of support bundles is faster as a result of parallelized log sanitization. For more information about support bundles, see "[Providing data to GitHub Support](/support/contacting-github-support/providing-data-to-github-support)."
+    - APIs that contain the `organization` or `org` route now accept either the organization's slug or ID. Previously, the APIs only accepted slugs, which caused `Link` headers for GitHub Advanced Security endpoints to be inaccessible. For more information, see "[Organizations](https://docs.github.com/rest/orgs/orgs)" in the REST API documentation. 
+    - The enterprise audit log now includes more user-generated events, such as `project.create`. The REST API also returns additional user-generated events, such as `repo.create`. For more information, see "[Accessing the audit log for your enterprise](/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/accessing-the-audit-log-for-your-enterprise)" and "[Using the audit log API for your enterprise](/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/using-the-audit-log-api-for-your-enterprise#querying-the-audit-log-rest-api)."
+    - In some cases, cache replicas could reject some Git operations on recently updated repositories. For more information about repository caching, see "[About repository caching](/admin/enterprise-management/caching-repositories/about-repository-caching)." 
+    - You can now configure the global announcement banner to be dismissable using the REST API. For more information, see "[Customizing user messages for your enterprise](/admin/user-management/managing-users-in-your-enterprise/customizing-user-messages-for-your-enterprise#creating-a-global-announcement-banner)." 
   known_issues:
-    - "{% data variables.product.prodname_ghe_server %} インスタンスを設定したばかりでユーザーがいない場合、攻撃者が最初の管理者ユーザーを作成できました。"
-    - カスタムのファイアウォール規則は、アップグレード プロセス中に削除されます。
-    - "[Web インターフェイスからアップロードされた](https://github.com/blog/2105-upload-files-to-your-repositories) Git LFS 追跡ファイルが誤ってリポジトリに直接追加されます。"
-    - 同じリポジトリ内の BLOB への固定リンクが含まれ、その BLOB のファイル パスが 255 文字を超える場合、issue はクローズできません。
-    - "GitHub Connect で [Users can search GitHub.com]\\(ユーザーが GitHub.com を検索できる\\) が有効になっている場合、プライベートと内部リポジトリのイシューが GitHub.com の検索結果に含まれません。"
-    - "{% data variables.product.prodname_registry %} npm レジストリが、メタデータ応答で時刻値を返さなくなります。これは、パフォーマンスの大幅な向上を見込んで行われました。メタデータ応答の一部として時刻値を返すために必要なすべてのデータを引き続き保持します。また、既存のパフォーマンスの問題を解決したら、将来的にはこの値を再び返す予定です。"
-    - pre-receive フックの処理に固有のリソース制限が、一部の pre-receive フックのエラーを引き起こす場合があります。
-    - 別のホストで作成されたバックアップからインスタンスを復元した後、Actions のサービスを再起動する必要があります。
-    - リポジトリの設定で、読み取りアクセス権を持つユーザーにディスカッションの作成を許可するオプションを有効にしても、この機能は有効になりません。
-    - ユーザーが既存の issue をディスカッションに変換できない場合があります。
-    - "シークレット スキャンのカスタム パターンの末尾の区切り記号は `.*` です (具体的には [After secret]\\(シークレットの後\\) フィールド)。この区切り記号のためにリポジトリ間でのシークレットのスキャンで不整合が発生し、リポジトリの履歴にスキャンが完了していないギャップができる場合があります。増分スキャンも影響を受ける場合があります。スキャンでの問題を避けるには、パターンの末尾を変更して、`.*` 区切り記号を削除します。"
+    - On a freshly set up {% data variables.product.prodname_ghe_server %} instance without any users, an attacker could create the first admin user.
+    - Custom firewall rules are removed during the upgrade process.
+    - Git LFS tracked files [uploaded through the web interface](https://github.com/blog/2105-upload-files-to-your-repositories) are incorrectly added directly to the repository.
+    - Issues cannot be closed if they contain a permalink to a blob in the same repository, where the blob's file path is longer than 255 characters.
+    - When "Users can search GitHub.com" is enabled with GitHub Connect, issues in private and internal repositories are not included in GitHub.com search results.
+    - The {% data variables.product.prodname_registry %} npm registry no longer returns a time value in metadata responses. This was done to allow for substantial performance improvements. We continue to have all the data necessary to return a time value as part of the metadata response and will resume returning this value in the future once we have solved the existing performance issues.
+    - Resource limits that are specific to processing pre-receive hooks may cause some pre-receive hooks to fail.
+    - Actions services need to be restarted after restoring an instance from a backup taken on a different host.
+    - In a repository's settings, enabling the option to allow users with read access to create discussions does not enable this functionality.
+    - In some cases, users cannot convert existing issues to discussions.
+    - Custom patterns for secret scanning have `.*` as an end delimiter, specifically in the "After secret" field. This delimiter causes inconsistencies in scans for secrets across repositories, and you may notice gaps in a repository's history where no scans completed. Incremental scans may also be impacted. To prevent issues with scans, modify the end of the pattern to remove the `.*` delimiter.
+    - |
+      Running `ghe-repl-status` while upgrading a replica node may indicate `WARNING: git replication is behind the primary`. This warning is due to a change in how GitHub Enterprise Server 3.6.0 and later stores repositories. You can safely ignore this message, and the upgrade will proceed normally. [Updated: 2022-09-26]
+    - |
+      Hotpatch upgrades to {% data variables.product.prodname_ghe_server %} 3.6.2 may fail. Upgrades with the full `.pkg` are unaffected. If the upgrade fails for your instance, you can work around the issue in one of two ways.
+      1. SSH into the affected node and run `sudo dpkg --configure -a`, then start the upgrade again.
+      2. Alternatively, run the full `.pkg` upgrade.
+
+      If you're unable to upgrade, or if you need further assistance, contact GitHub Support. For more information, see "[Creating a support ticket](/support/contacting-github-support/creating-a-support-ticket)." [Updated: 2022-09-26]

translations/ja-JP/data/reusables/secret-scanning/partner-secret-list-private-repo.md

@@ -36,6 +36,10 @@ CloudBees CodeShip | CloudBees CodeShip Credential | codeship_credential
 {%- ifversion fpt or ghec or ghes > 3.2 or ghae %}
 Contentful | Contentful Personal Access Token | contentful_personal_access_token{% endif %}
 Databricks | Databricks Access Token | databricks_access_token
+{%- ifversion fpt or ghec or ghes > 3.8 or ghae > 3.8 %}
+DevCycle | DevCycle Client API Key | devcycle_client_api_key
+DevCycle | DevCycle Server API Key | devcycle_server_api_key
+DevCycle | DevCycle Mobile API Key | devcycle_mobile_api_key{% endif %}
 {%- ifversion fpt or ghec or ghes > 3.4 or ghae > 3.4 %}
 DigitalOcean | DigitalOcean Personal Access Token | digitalocean_personal_access_token
 DigitalOcean | DigitalOcean OAuth Token | digitalocean_oauth_token
@@ -104,6 +108,9 @@ Linear | Linear API Key | linear_api_key
 Linear | Linear OAuth Access Token | linear_oauth_access_token
 Lob | Lob Live API Key | lob_live_api_key
 Lob | Lob Test API Key | lob_test_api_key
+{%- ifversion fpt or ghec or ghes > 3.8 or ghae > 3.8 %}
+LogicMonitor | LogicMonitor Bearer Token | logicmonitor_bearer_token
+LogicMonitor | LogicMonitor LMV1 Access Key | logicmonitor_lmv1_access_key{% endif %}
 Mailchimp | Mailchimp API Key | mailchimp_api_key
 Mailgun | Mailgun API Key | mailgun_api_key
 {%- ifversion fpt or ghec or ghes > 3.3 or ghae > 3.3 %}

translations/ja-JP/data/reusables/secret-scanning/secret-list-private-push-protection.md

@@ -17,6 +17,10 @@ Azure | Azure Storage Account Key | azure_storage_account_key{% endif %}
 Checkout.com | Checkout.com Production Secret Key | checkout_production_secret_key
 Clojars | Clojars Deploy Token | clojars_deploy_token
 Databricks | Databricks Access Token | databricks_access_token
+{%- ifversion fpt or ghec or ghes > 3.8 or ghae > 3.8 %}
+DevCycle | DevCycle Client API Key | devcycle_client_api_key
+DevCycle | DevCycle Server API Key | devcycle_server_api_key
+DevCycle | DevCycle Mobile API Key | devcycle_mobile_api_key{% endif %}
 DigitalOcean | DigitalOcean Personal Access Token | digitalocean_personal_access_token
 DigitalOcean | DigitalOcean OAuth Token | digitalocean_oauth_token
 DigitalOcean | DigitalOcean Refresh Token | digitalocean_refresh_token
@@ -50,6 +54,9 @@ Ionic | Ionic Personal Access Token | ionic_personal_access_token
 Ionic | Ionic Refresh Token | ionic_refresh_token
 Linear | Linear API Key | linear_api_key
 Linear | Linear OAuth Access Token | linear_oauth_access_token
+{%- ifversion fpt or ghec or ghes > 3.8 or ghae > 3.8 %}
+LogicMonitor | LogicMonitor Bearer Token | logicmonitor_bearer_token
+LogicMonitor | LogicMonitor LMV1 Access Key | logicmonitor_lmv1_access_key{% endif %}
 Midtrans | Midtrans Production Server Key | midtrans_production_server_key
 New Relic | New Relic Personal API Key | new_relic_personal_api_key
 New Relic | New Relic REST API Key | new_relic_rest_api_key

translations/log/msft-ja-resets.csv

@@ -509,6 +509,7 @@ translations/ja-JP/data/release-notes/enterprise-server/3-4/8.yml,rendering erro
 translations/ja-JP/data/release-notes/enterprise-server/3-5/0-rc1.yml,rendering error
 translations/ja-JP/data/release-notes/enterprise-server/3-5/4.yml,rendering error
 translations/ja-JP/data/release-notes/enterprise-server/3-6/0-rc1.yml,rendering error
+translations/ja-JP/data/release-notes/enterprise-server/3-6/1.yml,broken liquid tags
 translations/ja-JP/data/reusables/actions/actions-audit-events-workflow.md,rendering error
 translations/ja-JP/data/reusables/actions/artifact-log-retention-statement.md,broken liquid tags
 translations/ja-JP/data/reusables/actions/changing-the-access-policy-of-a-runner-group.md,rendering error