diff --git a/adev-ja/src/app/features/update/recommendations.en.ts b/adev-ja/src/app/features/update/recommendations.en.ts
index 4ad177e308..60456e8abe 100644
--- a/adev-ja/src/app/features/update/recommendations.en.ts
+++ b/adev-ja/src/app/features/update/recommendations.en.ts
@@ -2752,7 +2752,7 @@ export const RECOMMENDATIONS: Step[] = [
},
{
action:
- "In the application's project directory, run `ng update @angular/core@20 @angular/cli@21` to update your application to Angular v21.",
+ "In the application's project directory, run `ng update @angular/core@21 @angular/cli@21` to update your application to Angular v21.",
level: ApplicationComplexity.Basic,
necessaryAsOf: 2100,
possibleIn: 2100,
diff --git a/adev-ja/src/app/features/update/recommendations.ts b/adev-ja/src/app/features/update/recommendations.ts
index ea3c413235..848a716e98 100644
--- a/adev-ja/src/app/features/update/recommendations.ts
+++ b/adev-ja/src/app/features/update/recommendations.ts
@@ -2752,7 +2752,7 @@ export const RECOMMENDATIONS: Step[] = [
},
{
action:
- "アプリケーションのプロジェクトディレクトリで、`ng update @angular/core@20 @angular/cli@21` を実行して、アプリケーションを Angular v21 に更新します。",
+ "アプリケーションのプロジェクトディレクトリで、`ng update @angular/core@21 @angular/cli@21` を実行して、アプリケーションを Angular v21 に更新します。",
level: ApplicationComplexity.Basic,
necessaryAsOf: 2100,
possibleIn: 2100,
diff --git a/adev-ja/src/content/guide/forms/signals/models.en.md b/adev-ja/src/content/guide/forms/signals/models.en.md
index f0f2fc4e67..92a871918a 100644
--- a/adev-ja/src/content/guide/forms/signals/models.en.md
+++ b/adev-ja/src/content/guide/forms/signals/models.en.md
@@ -14,7 +14,7 @@ Form models solve this by centralizing form data in a single writable signal. Wh
A form model is a writable signal created with Angular's `signal()` function. The signal holds an object that represents your form's data structure.
-```ts
+```angular-ts
import { Component, signal } from '@angular/core'
import { form, Field } from '@angular/forms/signals'
@@ -150,7 +150,7 @@ Each field in the field tree is a function. Calling a field returns a `FieldStat
Access field state when working with individual fields in templates or reactive computations:
-```ts
+```angular-ts
@Component({
template: `
Current email: {{ loginForm.email().value() }}
@@ -292,7 +292,7 @@ This synchronization happens automatically. You don't write subscriptions or eve
### Example: Both directions
-```ts
+```angular-ts
@Component({
template: `
@@ -386,7 +386,7 @@ userForm.settings.theme // FieldTree
In templates, you bind nested fields the same way as top-level fields:
-```ts
+```angular-ts
@Component({
template: `
diff --git a/adev-ja/src/content/guide/forms/signals/models.md b/adev-ja/src/content/guide/forms/signals/models.md
index b2db1a0733..b4d3a7e74f 100644
--- a/adev-ja/src/content/guide/forms/signals/models.md
+++ b/adev-ja/src/content/guide/forms/signals/models.md
@@ -14,7 +14,7 @@ NOTE: フォームモデルは、コンポーネントの双方向バインデ
フォームモデルは、Angularの`signal()`関数で作成される書き込み可能なシグナルです。このシグナルは、フォームのデータ構造を表すオブジェクトを保持します。
-```ts
+```angular-ts
import { Component, signal } from '@angular/core'
import { form, Field } from '@angular/forms/signals'
@@ -150,7 +150,7 @@ onSubmit() {
テンプレートやリアクティブな計算で個々のフィールドを扱う場合は、フィールドの状態にアクセスします:
-```ts
+```angular-ts
@Component({
template: `
Current email: {{ loginForm.email().value() }}
@@ -292,7 +292,7 @@ export class UserProfileComponent {
### 例: 両方向 {#example-both-directions}
-```ts
+```angular-ts
@Component({
template: `
@@ -386,7 +386,7 @@ userForm.settings.theme // FieldTree
テンプレートでは、トップレベルのフィールドと同じ方法でネストされたフィールドをバインドします:
-```ts
+```angular-ts
@Component({
template: `
diff --git a/adev-ja/src/content/guide/routing/navigate-to-routes.en.md b/adev-ja/src/content/guide/routing/navigate-to-routes.en.md
index 6651cd1418..2992f17bba 100644
--- a/adev-ja/src/content/guide/routing/navigate-to-routes.en.md
+++ b/adev-ja/src/content/guide/routing/navigate-to-routes.en.md
@@ -149,7 +149,7 @@ The `router.navigateByUrl()` method provides a direct way to programmatically na
```ts
// Standard route navigation
-router.navigateByUrl('/products);
+router.navigateByUrl('/products');
// Navigate to nested route
router.navigateByUrl('/products/featured');
diff --git a/adev-ja/src/content/guide/routing/navigate-to-routes.md b/adev-ja/src/content/guide/routing/navigate-to-routes.md
index 1e979f7240..bd00b236f4 100644
--- a/adev-ja/src/content/guide/routing/navigate-to-routes.md
+++ b/adev-ja/src/content/guide/routing/navigate-to-routes.md
@@ -149,7 +149,7 @@ export class UserDetailComponent {
```ts
// Standard route navigation
-router.navigateByUrl('/products);
+router.navigateByUrl('/products');
// Navigate to nested route
router.navigateByUrl('/products/featured');
diff --git a/origin b/origin
index 2ecdb221d3..2ddf26e699 160000
--- a/origin
+++ b/origin
@@ -1 +1 @@
-Subproject commit 2ecdb221d3bd80ddfd1817385d9ecc23c9002b5a
+Subproject commit 2ddf26e69906a09dfcc915cc44c3a0bcecd3af67
diff --git a/tools/adev-patches/replace-environment-values.patch b/tools/adev-patches/replace-environment-values.patch
index 5c2d706ff0..21864c9cd4 100644
--- a/tools/adev-patches/replace-environment-values.patch
+++ b/tools/adev-patches/replace-environment-values.patch
@@ -1,18 +1,16 @@
diff --git a/adev/src/app/environment.ts b/adev/src/app/environment.ts
-index 733b01d357..c84ac6bf7c 100644
+index 4a8b03193f..7491f820f7 100644
--- a/adev/src/app/environment.ts
+++ b/adev/src/app/environment.ts
-@@ -11,11 +11,11 @@ export default {
+@@ -21,9 +21,9 @@ export default {
// Those values are publicly visible in the search request headers, and presents search-only keys.
// https://www.algolia.com/doc/guides/security/api-keys/#search-only-api-key
algolia: {
- appId: 'L1XWT2UJ7F',
- apiKey: 'dfca7ed184db27927a512e5c6668b968',
+- indexName: indexName,
+ appId: 'D4RZISVST0',
+ apiKey: '77e5a0684280325e2e1f313e0fcc11b8',
- // The indexName value must match the branch it's on.
- // So it needs to be updated on release of the new major on the patch branch.
-- indexName: 'angular_next_dev',
+ indexName: 'angular_jp_v19',
},
- googleAnalyticsId: 'G-XB6NEVW32B',