Skip to content

v0.5.91: docs i18n, turborepo upgrade#3228

Merged
waleedlatif1 merged 3 commits intomainfrom
staging
Feb 16, 2026
Merged

v0.5.91: docs i18n, turborepo upgrade#3228
waleedlatif1 merged 3 commits intomainfrom
staging

Conversation

@waleedlatif1
Copy link
Collaborator

cherkanovart and others added 2 commits February 16, 2026 00:00
* fix: update i18n.lock

* feat(docs): enhance documentation with new sections on file handling, form deployment, quick reference, agent skills, and A2A integration
)

* feat(i18n): change lockfile (#3216)

* fix: update i18n.lock

* feat(docs): enhance documentation with new sections on file handling, form deployment, quick reference, agent skills, and A2A integration

* fix(docs): update docs and disable i18n action

* fix build

---------

Co-authored-by: cherkanov_art <45258907+cherkanovart@users.noreply.github.com>
@vercel
Copy link

vercel bot commented Feb 16, 2026

The latest updates on your projects. Learn more about Vercel for GitHub.

1 Skipped Deployment
Project Deployment Actions Updated (UTC)
docs Skipped Skipped Feb 16, 2026 8:25am

Request Review

# Conflicts:
#	apps/docs/content/docs/fr/tools/onepassword.mdx
#	apps/docs/content/docs/ja/tools/enrich.mdx
#	apps/docs/content/docs/ja/tools/google_maps.mdx
#	apps/docs/content/docs/ja/tools/onepassword.mdx
#	apps/docs/content/docs/zh/tools/enrich.mdx
#	apps/docs/content/docs/zh/tools/google_forms.mdx
#	apps/docs/content/docs/zh/tools/google_maps.mdx
#	apps/docs/content/docs/zh/tools/notion.mdx
#	apps/docs/content/docs/zh/tools/onepassword.mdx
#	apps/docs/content/docs/zh/tools/tinybird.mdx
@waleedlatif1 waleedlatif1 marked this pull request as ready for review February 16, 2026 08:25
@greptile-apps
Copy link
Contributor

greptile-apps bot commented Feb 16, 2026

Greptile Summary

This PR makes two changes: (1) disables the scheduled cron trigger for the i18n workflow, making it manual-only via workflow_dispatch, and (2) fixes MDX rendering issues across 10 translated documentation files (fr, ja, zh) where curly braces {} were being interpreted as JSX expressions instead of displaying as literal text.

  • i18n workflow: Removed the weekly cron schedule, keeping only manual trigger. The PR template within the workflow still references "weekly" in several places.
  • Docs fixes: Curly braces in parameter description tables are now properly escaped to prevent MDX/JSX parsing errors. Two different escaping strategies are used across files — backslash escaping (\{...\}) in some files and backtick wrapping (`{...}`) in others — which creates a minor consistency issue but both are functionally correct.

Confidence Score: 4/5

  • This PR is safe to merge — all changes are documentation fixes and a CI workflow configuration change with no runtime code impact.
  • Score reflects that all changes are low-risk documentation and CI config fixes. The MDX escaping fixes are correct and will resolve rendering issues. Minor deduction for the inconsistent escaping approach across translated files, which doesn't break anything but makes maintenance slightly harder.
  • No files require special attention. The inconsistent brace escaping across ja/tools/enrich.mdx vs zh/tools/enrich.mdx is a minor style issue.

Important Files Changed

Filename Overview
.github/workflows/i18n.yml Disables scheduled cron trigger for i18n workflow, keeping only manual workflow_dispatch. The PR body/template still references "weekly" in several places, which is now stale but non-functional.
apps/docs/content/docs/fr/tools/onepassword.mdx Wraps a JSON example in backticks to prevent MDX from interpreting curly braces as JSX expressions. Correct fix.
apps/docs/content/docs/ja/tools/enrich.mdx Escapes curly braces with backslashes (\{start, end\}), while the Chinese translation of the same file uses backtick wrapping. Both work but approach is inconsistent.
apps/docs/content/docs/ja/tools/google_maps.mdx Escapes curly braces with backslashes for {lat, lng}. Consistent with the English source file approach.
apps/docs/content/docs/ja/tools/onepassword.mdx Wraps JSON examples in backticks to prevent MDX interpretation issues. Correct fix, consistent with other onepassword translations.
apps/docs/content/docs/zh/tools/enrich.mdx Wraps {start, end} in backticks. Uses a different escaping approach than the Japanese translation of the same file (backslash escaping).
apps/docs/content/docs/zh/tools/google_forms.mdx Escapes curly braces with backslashes in the Pub/Sub topic name format string. Consistent with English source.
apps/docs/content/docs/zh/tools/google_maps.mdx Escapes {lat, lng} with backslashes. Consistent with the English source and Japanese translation.
apps/docs/content/docs/zh/tools/notion.mdx Wraps JSON example in backticks. Correct fix for preventing MDX JSX interpretation.
apps/docs/content/docs/zh/tools/onepassword.mdx Wraps three JSON examples in backticks across create, replace, and update item sections. Consistent with other onepassword translations.
apps/docs/content/docs/zh/tools/tinybird.mdx Wraps URL and JSON examples in backticks. Correct fix for preventing MDX interpretation issues.

Flowchart

flowchart TD
    A[i18n.yml Workflow] -->|"Before: cron + manual"| B[Scheduled Weekly Trigger]
    A -->|"Before: cron + manual"| C[Manual Trigger]
    A -->|"After: manual only"| D[Manual Trigger Only]
    
    E[MDX Doc Files] -->|"Before: raw braces"| F["{ } interpreted as JSX"]
    F --> G[Rendering Error]
    
    E -->|"After: escaped braces"| H["Backslash escaping \{ \}"]
    E -->|"After: escaped braces"| I["Backtick wrapping `{ }`"]
    H --> J[Renders Correctly]
    I --> J
Loading

Last reviewed commit: 8ebe753

Copy link
Contributor

@greptile-apps greptile-apps bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

11 files reviewed, 2 comments

Edit Code Review Agent Settings | Greptile

@greptile-apps
Copy link
Contributor

greptile-apps bot commented Feb 16, 2026

Additional Comments (1)

.github/workflows/i18n.yml
Stale "weekly" references in PR template

Now that the scheduled cron trigger has been removed (line 4), the PR body template still references "weekly" in multiple places: "Automated weekly translation updates" (line 68), "scheduled weekly i18n workflow" (line 70), and the branch name auto-translate/weekly- (line 106). Consider updating these to say "manual" or removing the schedule-specific language to avoid confusion.

Note: If this suggestion doesn't match your team's coding style, reply to this and let me know. I'll remember it for next time!

@waleedlatif1 waleedlatif1 merged commit b7e377e into main Feb 16, 2026
27 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants