Skip to content

Conversation

@filipecabaco
Copy link
Member

What kind of change does this PR introduce?

Restrict information shown by Phoenix logger

@vercel
Copy link

vercel bot commented Feb 27, 2025

The latest updates on your projects. Learn more about Vercel for Git ↗︎

1 Skipped Deployment
Name Status Preview Comments Updated (UTC)
realtime-demo ⬜️ Ignored (Inspect) Visit Preview Feb 27, 2025 0:40am

@coveralls
Copy link

coveralls commented Feb 27, 2025

Coverage Status

coverage: 81.43%. remained the same
when pulling 66b358d on fix/restrict-phoenix-logs
into c5f33de on main.

@filipecabaco filipecabaco force-pushed the fix/restrict-phoenix-logs branch 2 times, most recently from 5cb4948 to 973c688 Compare February 27, 2025 12:27
@filipecabaco filipecabaco force-pushed the fix/restrict-phoenix-logs branch from 973c688 to 66b358d Compare February 27, 2025 12:40
@filipecabaco filipecabaco enabled auto-merge (squash) February 27, 2025 12:58
@filipecabaco filipecabaco merged commit 04f8218 into main Feb 27, 2025
7 checks passed
@filipecabaco filipecabaco deleted the fix/restrict-phoenix-logs branch February 27, 2025 13:00
@kiwicopple
Copy link
Member

🎉 This PR is included in version 2.34.36 🎉

The release is available on GitHub release

Your semantic-release bot 📦🚀

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.

5 participants