Skip to content

feat(i18n): update translations#1593

Closed
waleedlatif1 wants to merge 5 commits intostagingfrom
auto-translate/staging-merge-18397426882
Closed

feat(i18n): update translations#1593
waleedlatif1 wants to merge 5 commits intostagingfrom
auto-translate/staging-merge-18397426882

Conversation

@waleedlatif1
Copy link
Collaborator

Summary

Automated translation updates triggered by changes to documentation.

This PR was automatically created after content changes were made, updating translations for all supported languages using Lingo.dev AI translation engine.

Original trigger: feat(deployed-chat): added file upload to workflow execute API, added to deployed chat, updated chat panel (#1588)

  • feat(deployed-chat): updated chat panel UI, deployed chat and API can now accept files

  • added nested tag dropdown for files

  • added duplicate file validation to chat panel

  • update docs & SDKs

  • fixed build

  • rm extraneous comments

  • ack PR comments, cut multiple DB roundtrips for permissions & api key checks in api/workflows

  • allow read-only users to access deployment info, but not take actions

  • add downloadable file to logs for files passed in via API

  • protect files/serve route that is only used client-side


Co-authored-by: waleed
Commit: da156cb
Workflow: https://github.com/simstudioai/sim/actions/runs/18397426882

Type of Change

  • Bug fix
  • New feature
  • Breaking change
  • Documentation
  • Other: ___________

Testing

This PR includes automated translations for modified English documentation content:

  • 🇪🇸 Spanish (es) translations
  • 🇫🇷 French (fr) translations
  • 🇨🇳 Chinese (zh) translations
  • 🇯🇵 Japanese (ja) translations
  • 🇩🇪 German (de) translations

What reviewers should focus on:

  • Verify translated content accuracy and context
  • Check that all links and references work correctly in translated versions
  • Ensure formatting, code blocks, and structure are preserved
  • Validate that technical terms are appropriately translated

Checklist

  • Code follows project style guidelines (automated translation)
  • Self-reviewed my changes (automated process)
  • Tests added/updated and passing
  • No new warnings introduced
  • I confirm that I have read and agree to the terms outlined in the Contributor License Agreement (CLA)

Screenshots/Videos

waleedlatif1 and others added 5 commits October 8, 2025 08:36
…splayText to various subblocks that didn't have it (#1582)
…1583)

* feat(billing): bill by threshold to prevent cancellation edge case

* fix org billing

* fix idempotency key issue

* small optimization for team checks

* remove console log

* remove unused type

* fix error handling
… to deployed chat, updated chat panel (#1588)

* feat(deployed-chat): updated chat panel UI, deployed chat and API can now accept files

* added nested tag dropdown for files

* added duplicate file validation to chat panel

* update docs & SDKs

* fixed build

* rm extraneous comments

* ack PR comments, cut multiple DB roundtrips for permissions & api key checks in api/workflows

* allow read-only users to access deployment info, but not take actions

* add downloadable file to logs for files passed in via API

* protect files/serve route that is only used client-side

---------

Co-authored-by: waleed <waleed>
@vercel vercel bot temporarily deployed to Preview – sim October 10, 2025 06:35 Inactive
@vercel
Copy link

vercel bot commented Oct 10, 2025

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

Project Deployment Preview Comments Updated (UTC)
docs Error Error Oct 10, 2025 6:36am
1 Skipped Deployment
Project Deployment Preview Comments Updated (UTC)
sim Skipped Skipped Oct 10, 2025 6:36am

Copy link
Collaborator Author

waleedlatif1 commented Oct 10, 2025

1 Job Failed:

CI / Test and Build / Test and Build failed on "Build application"
[...]
https://nextjs.org/telemetry

   ▲ Next.js 15.4.1 (Turbopack)
   - Experiments (use with caution):
     ✓ optimizeCss
     ⨯ turbopackSourceMaps

Error: docs#build: command (/home/runner/_work/sim/sim/apps/docs) /home/runner/.bun/bin/bun run build exited (1)
   Creating an optimized production build ...
error: script "build" exited with code 130

 Tasks:    2 successful, 4 total
Cached:    0 cached, 4 total
  Time:    34.182s 
Failed:    docs#build

 ERROR  run failed: command  exited (1)
error: script "build" exited with code 1
Error: Process completed with exit code 1.

Summary: 1 failed workflow
  • CI (1 job failed)

Last updated: 2025-10-10 06:37:43 UTC

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.

Greptile Overview

Summary

Automated translation updates triggered by PR #1588 which added file upload functionality to the workflow execution API and deployed chat. This PR updates documentation translations across 5 languages (Spanish, French, German, Japanese, and Chinese) for 4 key documentation sections:

  • API Trigger documentation - Added file upload format specifications, file property tables, and examples showing both base64-encoded and URL-referenced file uploads
  • TypeScript SDK documentation - Added comprehensive file upload examples for both browser and Node.js environments, including file handling patterns
  • Chat Trigger documentation - Enhanced with detailed file property tables showing all accessible attributes (url, name, size, type, uploadedAt, expiresAt)
  • Costs/Billing documentation - Added new threshold billing model explanation and examples

The translations preserve code blocks, technical terminology, markdown formatting, and MDX components correctly. The i18n.lock file has been updated with new content checksums to track these translation versions.

Confidence Score: 5/5

  • This PR is safe to merge with no risk
  • This is an automated translation PR that only updates documentation content in non-English languages. No code logic is changed, only translated documentation reflecting the file upload feature added in PR #1588. The translations appear consistent, preserve formatting and technical terms appropriately, and the i18n.lock file properly tracks content versions.
  • No files require special attention - all changes are automated translations

Important Files Changed

File Analysis

Filename Score Overview
apps/docs/content/docs/es/triggers/api.mdx 5/5 Spanish translation updated to reflect new file upload documentation and API changes
apps/docs/content/docs/de/triggers/api.mdx 5/5 German translation updated to reflect new file upload documentation and API changes
apps/docs/content/docs/fr/triggers/api.mdx 5/5 French translation updated to reflect new file upload documentation and API changes
apps/docs/content/docs/ja/triggers/api.mdx 5/5 Japanese translation updated to reflect new file upload documentation and API changes
apps/docs/content/docs/zh/triggers/api.mdx 5/5 Chinese translation updated to reflect new file upload documentation and API changes
apps/docs/i18n.lock 5/5 Translation checksums updated to track new content versions across all languages

Sequence Diagram

sequenceDiagram
    participant Dev as Developer
    participant PR as PR #1588
    participant GHA as GitHub Actions
    participant Lingo as Lingo.dev AI
    participant Docs as Documentation Files

    Dev->>PR: Merge PR #1588 (file upload feature)
    PR->>Docs: Update English docs
    PR->>GHA: Trigger translation workflow
    GHA->>Lingo: Send English content changes
    
    loop For each language (es, fr, de, ja, zh)
        Lingo->>Lingo: Translate content
        Lingo->>Docs: Update translated .mdx files
    end
    
    GHA->>Docs: Update i18n.lock checksums
    GHA->>PR: Create PR #1593
    
    Note over PR,Docs: All 5 languages synchronized<br/>with English source content
Loading

25 files reviewed, no comments

Edit Code Review Agent Settings | Greptile

@waleedlatif1 waleedlatif1 deleted the auto-translate/staging-merge-18397426882 branch October 13, 2025 17:37
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants