fix: update deprecated 'lingo.dev auth --login' references to 'lingo.dev login' (#1108)

* fix: update deprecated 'lingo.dev auth --login' references to 'lingo.dev login'

- Updated error messages in status.ts, i18n.ts, and init.ts
- Replaced all instances of deprecated 'auth --login' command with 'login'
- Maintains authentication flow functionality while using current command syntax

Fixes #1104

Co-Authored-By: matej@lingo.dev <matej@lednicky.name>

* fix: apply prettier formatting to i18n.ts

- Fix formatting issue that was causing CI check to fail
- Consolidate multi-line error message to single line per prettier rules

Co-Authored-By: matej@lingo.dev <matej@lednicky.name>

* fix: apply prettier formatting to workflow and config files

- Fix formatting issues in .claude/agents/code-architect-reviewer.md
- Fix formatting issues in .github/workflows/claude-code-review.yml
- Fix formatting issues in .github/workflows/claude-issue-autolabel.yml
- Fix formatting issues in .github/workflows/label-all-unlabeled-issues.yml

These were pre-existing formatting issues causing CI checks to fail.
The core changes to update deprecated 'lingo.dev auth --login' references remain intact.

Co-Authored-By: matej@lingo.dev <matej@lednicky.name>

* feat: add changeset for deprecated command reference updates

- Add changeset for updating 'lingo.dev auth --login' to 'lingo.dev login'
- Patch-level change for CLI error message updates
- Resolves CI requirement for changeset to be present in PR

Co-Authored-By: matej@lingo.dev <matej@lednicky.name>

---------

Co-authored-by: Devin AI <158243242+devin-ai-integration[bot]@users.noreply.github.com>
Co-authored-by: matej@lingo.dev <matej@lednicky.name>

Author: devin-ai-integration[bot]

.changeset/early-shrimps-smile.md

@@ -0,0 +1,5 @@
+---
+"lingo.dev": patch
+---
+
+Update deprecated 'lingo.dev auth --login' command references to 'lingo.dev login' in CLI error messages

.claude/agents/code-architect-reviewer.md

@@ -9,27 +9,31 @@ You are an Expert Software Architect and Code Reviewer with deep expertise in cl
 When reviewing code, you will:
 
 **Architectural Analysis:**
+
 - Evaluate overall code structure and organization
 - Assess adherence to SOLID principles and design patterns
 - Identify architectural smells and suggest improvements
 - Review separation of concerns and modularity
 - Analyze dependency management and coupling
 
 **Clean Code Assessment:**
+
 - Review naming conventions for clarity and expressiveness
 - Evaluate function and class sizes (single responsibility)
 - Check for code duplication and suggest DRY improvements
 - Assess readability and self-documenting code practices
 - Review error handling and edge case coverage
 
 **Best Practices Validation:**
+
 - Verify adherence to language-specific conventions
 - Check for proper use of abstractions and interfaces
 - Evaluate testing strategy and testability
 - Review performance considerations and potential bottlenecks
 - Assess security implications and vulnerabilities
 
 **Review Process:**
+
 1. First, understand the code's purpose and context
 2. Analyze the overall architecture and design decisions
 3. Examine implementation details for clean code violations
@@ -38,13 +42,15 @@ When reviewing code, you will:
 6. Provide concrete, actionable recommendations with examples
 
 **Feedback Format:**
+
 - Start with positive observations about good practices
 - Organize feedback by category (Architecture, Clean Code, Performance, etc.)
 - For each issue, explain the problem, why it matters, and how to fix it
 - Provide code examples for suggested improvements when helpful
 - End with a summary of key action items
 
 **Quality Standards:**
+
 - Be thorough but focus on the most impactful improvements
 - Explain the reasoning behind each recommendation
 - Consider maintainability, scalability, and team collaboration

.github/workflows/claude-code-review.yml

@@ -8,7 +8,7 @@ on:
   workflow_dispatch:
     inputs:
       pr_number:
-        description: 'PR number to review'
+        description: "PR number to review"
         required: false
         type: string
 
@@ -250,4 +250,4 @@ jobs:
             - NEVER approve without thorough analysis
             - ALWAYS provide actionable feedback with examples
         env:
-          GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
+          GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}

.github/workflows/claude-issue-autolabel.yml

@@ -6,7 +6,7 @@ on:
   workflow_dispatch:
     inputs:
       issue_number:
-        description: 'Issue number to label'
+        description: "Issue number to label"
         required: false
         type: string
 
@@ -156,4 +156,3 @@ jobs:
             - ALWAYS be matter-of-fact and use simple, casual language
         env:
           GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
-

.github/workflows/label-all-unlabeled-issues.yml

@@ -10,27 +10,27 @@ jobs:
       issues: write
       contents: read
       actions: write
-      
+
     steps:
       - name: Checkout repository
         uses: actions/checkout@v4
 
       - name: Find and Label Unlabeled Issues
         run: |
           echo "Finding all issues without 'autolabeled' label..."
-          
+
           # Get all issues without the "autolabeled" label
           unlabeled_issues=$(gh issue list --limit 1000 --json number,labels --jq '.[] | select(.labels | map(.name) | contains(["autolabeled"]) | not) | .number')
-          
+
           if [[ -z "$unlabeled_issues" ]]; then
             echo "No issues found without 'autolabeled' label"
             exit 0
           fi
-          
+
           echo "Found issues without 'autolabeled' label:"
           echo "$unlabeled_issues"
           echo ""
-          
+
           # Process each issue by triggering the labeling workflow
           for issue_number in $unlabeled_issues; do
             echo "Triggering labeling workflow for issue #$issue_number..."
@@ -42,8 +42,8 @@ jobs:
             # Wait a bit to avoid overwhelming the system
             sleep 10
           done
-          
+
           echo "Triggered labeling workflows for all issues without 'autolabeled' label"
           echo "Check workflow runs: gh run list --workflow=claude-issue-autolabel.yml"
         env:
-          GH_TOKEN: ${{ secrets.GITHUB_TOKEN }}
+          GH_TOKEN: ${{ secrets.GITHUB_TOKEN }}

packages/cli/src/cli/cmd/i18n.ts

@@ -542,7 +542,7 @@ export async function validateAuth(settings: ReturnType<typeof getSettings>) {
   if (!settings.auth.apiKey) {
     throw new CLIError({
       message:
-        "Not authenticated. Please run `lingo.dev auth --login` to authenticate.",
+        "Not authenticated. Please run `lingo.dev login` to authenticate.",
       docUrl: "authError",
     });
   }
@@ -554,8 +554,7 @@ export async function validateAuth(settings: ReturnType<typeof getSettings>) {
   const user = await authenticator.whoami();
   if (!user) {
     throw new CLIError({
-      message:
-        "Invalid API key. Please run `lingo.dev auth --login` to authenticate.",
+      message: "Invalid API key. Please run `lingo.dev login` to authenticate.",
       docUrl: "authError",
     });
   }

packages/cli/src/cli/cmd/init.ts

@@ -234,7 +234,7 @@ export default new InteractiveCommand()
         }
       } else {
         Ora().warn(
-          "You are not logged in. Run `npx lingo.dev@latest auth --login` to login.",
+          "You are not logged in. Run `npx lingo.dev@latest login` to login.",
         );
       }
     } else {

packages/cli/src/cli/cmd/status.ts

@@ -76,7 +76,7 @@ export default new Command()
           ora.succeed(`Authenticated as ${auth.email}`);
         } else {
           ora.info(
-            "Not authenticated. Continuing without authentication. (Run `lingo.dev auth --login` to authenticate)",
+            "Not authenticated. Continuing without authentication. (Run `lingo.dev login` to authenticate)",
           );
         }
       } catch (error) {