chore: remove lock files from community directory

[sumitsaurabh927]

Summary

• Deleted all lock files (pnpm-lock.yaml, package-lock.json, i18n.lock) from the community/ directory across 5 projects

Test plan

• No functional changes — lock files only

🤖 Generated with Claude Code

Summary by CodeRabbit

Release Notes

• Chores
  • Internal build configuration update.

[coderabbitai]

📝 Walkthrough

Walkthrough

A new empty Changesets markdown file is added at .changeset/funny-bears-reply.md containing only YAML frontmatter delimiters without any release metadata or content.

Changes

Cohort / File(s)	Summary
Changeset Configuration .changeset/funny-bears-reply.md	New empty changeset file with YAML frontmatter delimiters only; no version bump, release type, or changelog content specified.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Poem

🐰 An empty changeset hops into place,
With dashes so neat, a minimal trace—
No version, no notes, just frontmatter bare,
A placeholder waiting, with curious flair!

🚥 Pre-merge checks | ✅ 1 | ❌ 2

❌ Failed checks (2 warnings)

Check name	Status	Explanation	Resolution
Title check	⚠️ Warning	The title describes removing lock files from the community directory, but the actual change is only adding an empty changeset file with no lock file removals.	Update the title to accurately reflect the changeset file addition, such as 'chore: add changeset for lock file removal' or verify the PR contains the actual lock file deletions.
Description check	⚠️ Warning	The description claims lock files were deleted from the community directory, but the changeset summary shows only an empty changeset file was added with no actual file deletions.	Correct the description to match the actual changes (empty changeset file addition) or ensure the PR includes the actual lock file deletions as described.

✅ Passed checks (1 passed)

Check name	Status	Explanation
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch lock-files

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[coderabbitai]

Actionable comments posted: 1

🤖 Prompt for all review comments with AI agents

Verify each finding against the current code and only fix it if needed.

Inline comments:
In @.changeset/funny-bears-reply.md:
- Around line 1-2: The changeset file .changeset/funny-bears-reply.md contains
only YAML delimiters and is missing required changeset metadata; fix it by
regenerating an empty changeset from the repo root with the command pnpm
new:empty (which produces the proper no-release metadata) or by editing
.changeset/funny-bears-reply.md to include a valid metadata block (e.g., a
package key and bump like "@pkg/name": patch) and a short description so CI
`pnpm changeset status --since origin/main` will pass.

🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

• Push a commit to this branch (recommended)
• Create a new PR with the fixes

---

ℹ️ Review info

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: e41e0c3e-98f3-4df1-ae0a-547f92dbe873

📥 Commits

Reviewing files that changed from the base of the PR and between ab701a7 and d629f7f.

⛔ Files ignored due to path filters (9)

• community/Lingo-lens/package-lock.json is excluded by !**/package-lock.json
• community/Lingo-lens/pnpm-lock.yaml is excluded by !**/pnpm-lock.yaml
• community/global-onboard/i18n.lock is excluded by !**/*.lock
• community/global-onboard/package-lock.json is excluded by !**/package-lock.json
• community/lingo-global-forms/package-lock.json is excluded by !**/package-lock.json
• community/shift-read/pnpm-lock.yaml is excluded by !**/pnpm-lock.yaml
• community/video-lingo-ai/i18n.lock is excluded by !**/*.lock
• community/video-lingo-ai/package-lock.json is excluded by !**/package-lock.json
• community/video-translator/pnpm-lock.yaml is excluded by !**/pnpm-lock.yaml

📒 Files selected for processing (1)

• .changeset/funny-bears-reply.md

[coderabbitai]

⚠️ Potential issue | 🟠 Major

🧩 Analysis chain

🏁 Script executed:

#!/bin/bash
set -euo pipefail

echo "1) Show changed changeset files"
git diff --name-only origin/main...HEAD | rg '^\.(changeset)/.*\.md$' || true

echo "2) Print the file to confirm it is not frontmatter-only"
target=".changeset/funny-bears-reply.md"
nl -ba "$target"

echo "3) Verify changeset parsing/CI behavior"
pnpm changeset status --since origin/main

Repository: lingodotdev/lingo.dev

Length of output: 253

---

🏁 Script executed:

#!/bin/bash

echo "=== 1. Read the changeset file ==="
if [ -f ".changeset/funny-bears-reply.md" ]; then
    echo "File exists. Content (with line numbers):"
    cat -n ".changeset/funny-bears-reply.md"
    echo "---"
    echo "File size:"
    wc -c ".changeset/funny-bears-reply.md"
else
    echo "File not found"
fi

echo ""
echo "=== 2. Check for other changesets to see valid format ==="
ls -la .changeset/*.md 2>/dev/null | head -5 || echo "No changesets found"

echo ""
echo "=== 3. Read one valid changeset example ==="
find .changeset -name "*.md" -type f | head -1 | xargs -I {} sh -c 'echo "File: {}"; cat -n {}'

echo ""
echo "=== 4. Check changesets configuration ==="
if [ -f ".changeset/config.json" ]; then
    cat ".changeset/config.json"
fi

echo ""
echo "=== 5. Check if pnpm/changesets is available ==="
which pnpm && pnpm --version || echo "pnpm not available"

Repository: lingodotdev/lingo.dev

Length of output: 1689

---

🏁 Script executed:

#!/bin/bash

echo "=== Read the 90-byte valid changeset ==="
cat -n ".changeset/slow-groups-find.md"

echo ""
echo "=== Check if there's a .github/workflows file that validates changesets ==="
if [ -f ".github/workflows/pr-check.yml" ]; then
    echo "Found pr-check.yml - extract changeset validation steps:"
    grep -A 5 -B 2 "changeset" ".github/workflows/pr-check.yml" || true
fi

echo ""
echo "=== Look for any changeset format validation or tests ==="
rg "changeset" --type yml --type yaml --type json -A 3 -B 1 | head -40 || true

Repository: lingodotdev/lingo.dev

Length of output: 768

---

🏁 Script executed:

#!/bin/bash

echo "=== Search for any documentation about changesets or empty changesets ==="
find . -type f \( -name "*.md" -o -name "*.txt" \) | xargs grep -l "new:empty\|changeset.*empty" 2>/dev/null | head -5

echo ""
echo "=== Check package.json scripts ==="
cat package.json | grep -A 20 '"scripts"' | head -25

echo ""
echo "=== Look for Changesets documentation or guides in the repo ==="
find . -type f -name "*.md" | xargs grep -l "changeset" 2>/dev/null | head -5

Repository: lingodotdev/lingo.dev

Length of output: 1071

---

🏁 Script executed:

#!/bin/bash

echo "=== Read CLAUDE.md for changeset guidance ==="
head -100 CLAUDE.md

echo ""
echo "=== Read CONTRIBUTING.md for changeset info ==="
grep -A 10 -B 2 "changeset" CONTRIBUTING.md | head -30

Repository: lingodotdev/lingo.dev

Length of output: 967

---

Regenerate the changeset with pnpm new:empty or add changeset content to the empty file.

The file contains only YAML frontmatter delimiters (--- and ---) and is missing required changeset metadata. This will fail the CI validation step pnpm changeset status --since origin/main. Since this PR only removes lock files (no release needed), regenerate using pnpm new:empty from the repo root per the contribution guidelines, or manually add changeset content to this file.

Example of a properly formatted changeset

Valid changesets require a metadata section with a package key and version bump:

---
"@lingo/ctx": minor
---

Description of the changes

For no-release changes (like lock file updates), pnpm new:empty creates the proper structure.

🤖 Prompt for AI Agents

Verify each finding against the current code and only fix it if needed.

In @.changeset/funny-bears-reply.md around lines 1 - 2, The changeset file
.changeset/funny-bears-reply.md contains only YAML delimiters and is missing
required changeset metadata; fix it by regenerating an empty changeset from the
repo root with the command pnpm new:empty (which produces the proper no-release
metadata) or by editing .changeset/funny-bears-reply.md to include a valid
metadata block (e.g., a package key and bump like "@pkg/name": patch) and a
short description so CI `pnpm changeset status --since origin/main` will pass.