Skip to content

feat: exclude CSP violations from LogReport by default#13

Closed
audunru wants to merge 2 commits intomainfrom
feat/log-report-exclude-csp
Closed

feat: exclude CSP violations from LogReport by default#13
audunru wants to merge 2 commits intomainfrom
feat/log-report-exclude-csp

Conversation

@audunru
Copy link
Copy Markdown
Owner

@audunru audunru commented May 3, 2026

Summary

  • Excludes CSP violations from LogReport by default (configurable)
  • Logs CSP violations at warning level instead of error
  • Switches release workflow to use RELEASE_PLEASE_TOKEN PAT to support branch protection rules

Test plan

  • Add RELEASE_PLEASE_TOKEN secret to the repository
  • Merge and verify release pipeline succeeds

🤖 Generated with Claude Code

audunru and others added 2 commits May 3, 2026 10:36
…ning level

LogReport now skips csp-violation reports by default (since LogCspViolation
already handles them) and logs at warning level instead of info.

BREAKING CHANGE: LogReport no longer logs CSP violations by default, and log
level changed from info to warning. Override shouldExclude() returning false
to restore the previous CSP logging behavior.

Closes #11

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
@audunru
Copy link
Copy Markdown
Owner Author

audunru commented May 3, 2026

Superseded — the feature was already merged in #12. Recreating with just the workflow fix.

@audunru audunru closed this May 3, 2026
@audunru audunru deleted the feat/log-report-exclude-csp branch May 3, 2026 14:50
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant