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

1 Skipped Deployment

Project	Deployment	Actions	Updated (UTC)
docs	Skipped		Mar 27, 2026 1:17am

@cursor @greptile review

CI failure was related to this PR, and it’s now fixed.

What failed

@sim/logger#lint:check in CI failed on packages/logger/src/index.test.ts due to Biome rules:

• lint/suspicious/noPrototypeBuiltins
• lint/performance/noDelete

Fix applied

Updated the new test code to comply with Biome:

• Replaced Object.prototype.hasOwnProperty.call(...) with Object.hasOwn(...)
• Replaced delete ... usages with ... = undefined assignments in test env cleanup/setup paths

Validation run locally

In packages/logger:

• bun run lint:check ✅
• bun test ./src/index.test.ts ✅ (21 pass, 0 fail)

Git updates

• Commit: bec5bc698
• Message: fix(logger): satisfy biome rules in new prod log tests
• Pushed to: origin/feat/info-logging
• PR feat(log): enable info level logs for production #3798 metadata updated

Also, because this run required installing Bun/dependencies in the cloud environment, you may want to run an env setup agent so future agents don’t repeat setup work.

Suggested prompt for env setup agent:

“Update our cloud agent environment so Bun 1.3.11 is preinstalled and repository dependencies are prewarmed for this monorepo (/workspace, bun.lock), ensuring bun run lint:check and package-level tests can run immediately without bootstrap.”

  

Greptile Summary

This PR changes the default production log level in packages/logger/src/index.ts from ERROR to INFO, enabling INFO, WARN, and ERROR logs in production while continuing to suppress DEBUG logs. The motivation is improved observability on the happy path without relying solely on error events.\n\nKey details:\n- Only getMinLogLevel() is modified; all other logger logic is unchanged.\n- The existing guard in shouldLog() (typeof window !== 'undefined' check) already prevents any logs from reaching the browser in production, so there is no client-side log-exposure risk.\n- The LOG_LEVEL environment variable override still works, allowing operators to dial down to ERROR-only or up to DEBUG without a code change.\n- The comment in getMinLogLevel() is correctly updated to match the new default.

Confidence Score: 5/5

Safe to merge — a one-line behavioural change with clear intent, correct implementation, and no client-side exposure risk.

The change is minimal and well-understood: it raises the production minimum log level from ERROR to INFO. The client-side guard (window !== undefined) already existed and prevents leaking logs to the browser. No new logic paths are introduced, and the LOG_LEVEL env var escape hatch is preserved. No issues found.

No files require special attention.

Important Files Changed

_{Reviews (2): Last reviewed commit: "feat(log): enable info level logs for pr..." | Re-trigger Greptile}

PR Summary

Low Risk
Low risk: changes only the default production logging threshold, which may increase log volume but doesn’t affect control flow or security-sensitive logic.

Overview
Production logging in @sim/logger now defaults to INFO (instead of ERROR), so info/warn messages are emitted in production unless overridden via LOG_LEVEL.

^{Written by Cursor Bugbot for commit 2852fca. This will update automatically on new commits. Configure here.}