docs: mention bun.lock for lockfile

[iiio2]

Since bun.lock is also a lockfile, maybe we can include it here.

[vercel]

@iiio2 is attempting to deploy a commit to the Nitro Team on Vercel.

A member of the Team first needs to authorize it.

[coderabbitai]

Caution

Review failed

The pull request is closed.

📝 Walkthrough

Walkthrough

SECURITY.md was updated to expand the list of recommended lock files for version control. The bun.lock file was added to the existing list that included yarn.lock, package-lock.json, and pnpm-lock.yaml.

Changes

Cohort / File(s)	Change Summary
Security Documentation SECURITY.md	Added bun.lock to the list of maintained lock files in security guidance

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

This is a straightforward documentation update with a single item added to a list. The change is purely informational with no code logic or structural modifications.

✨ Finishing touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment

---

📜 Recent review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 888e556 and f6a5563.

📒 Files selected for processing (1)

• SECURITY.md (1 hunks)

Tip

📝 Customizable high-level summaries are now available in beta!

You can now customize how CodeRabbit generates the high-level summary in your pull requests — including its content, structure, tone, and formatting.

• Provide your own instructions using the high_level_summary_instructions setting.
• Format the summary however you like (bullet lists, tables, multi-section layouts, contributor stats, etc.).
• Use high_level_summary_in_walkthrough to move the summary from the description to the walkthrough section.

Example instruction:

"Divide the high-level summary into five sections:

1. 📝 Description — Summarize the main change in 50–60 words, explaining what was done.
2. 📓 References — List relevant issues, discussions, documentation, or related PRs.
3. 📦 Dependencies & Requirements — Mention any new/updated dependencies, environment variable changes, or configuration updates.
4. 📊 Contributor Summary — Include a Markdown table showing contributions:
   | Contributor | Lines Added | Lines Removed | Files Changed |
5. ✔️ Additional Notes — Add any extra reviewer context.
   Keep each section concise (under 200 words) and use bullet or numbered lists for clarity."

Note: This feature is currently in beta for Pro-tier users, and pricing will be announced later.

---

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

[pi0]

Thnx!

[iiio2]

Thanks @pi0 . 😊