fix: conflicts

[vinitkumar]

Summary by Sourcery

CI:

• Reduce permissions in the CodeQL analysis workflow by dropping security-events write access.

[sourcery-ai]

Reviewer's guide (collapsed on small PRs)

Reviewer's Guide

Adjusts GitHub CodeQL workflow permissions by removing the explicit security-events: write permission from the workflow-level permissions block.

File-Level Changes

Change	Details	Files
Relax CodeQL workflow permissions by dropping the explicit write access to security events.	Remove the security-events: write entry from the top-level permissions block of the CodeQL GitHub Actions workflow, relying on default or job-level permissions instead.	.github/workflows/codeql.yml

---

Tips and commands

Interacting with Sourcery

• Trigger a new review: Comment @sourcery-ai review on the pull request.
• Continue discussions: Reply directly to Sourcery's review comments.
• Generate a GitHub issue from a review comment: Ask Sourcery to create an
  issue from a review comment by replying to it. You can also reply to a
  review comment with @sourcery-ai issue to create an issue from it.
• Generate a pull request title: Write @sourcery-ai anywhere in the pull
  request title to generate a title at any time. You can also comment
  @sourcery-ai title on the pull request to (re-)generate the title at any time.
• Generate a pull request summary: Write @sourcery-ai summary anywhere in
  the pull request body to generate a PR summary at any time exactly where you
  want it. You can also comment @sourcery-ai summary on the pull request to
  (re-)generate the summary at any time.
• Generate reviewer's guide: Comment @sourcery-ai guide on the pull
  request to (re-)generate the reviewer's guide at any time.
• Resolve all Sourcery comments: Comment @sourcery-ai resolve on the
  pull request to resolve all Sourcery comments. Useful if you've already
  addressed all the comments and don't want to see them anymore.
• Dismiss all Sourcery reviews: Comment @sourcery-ai dismiss on the pull
  request to dismiss all existing Sourcery reviews. Especially useful if you
  want to start fresh with a new review - don't forget to comment
  @sourcery-ai review to trigger a new review!

Customizing Your Experience

Access your dashboard to:

• Enable or disable review features such as the Sourcery-generated pull request
  summary, the reviewer's guide, and others.
• Change the review language.
• Add, remove or edit custom review instructions.
• Adjust other review settings.

Getting Help

• Contact our support team for questions or feedback.
• Visit our documentation for detailed guides and information.
• Keep in touch with the Sourcery team by following us on X/Twitter, LinkedIn or GitHub.

[sourcery-ai]

Hey - I've found 1 issue

Prompt for AI Agents

Please address the comments from this code review:

## Individual Comments

### Comment 1
<location path=".github/workflows/codeql.yml" line_range="13" />
<code_context>

 permissions:
   contents: read
-  security-events: write

 jobs:
</code_context>
<issue_to_address>
**🚨 issue (security):** Reconsider removing `security-events: write`, as CodeQL may need it to upload results.

CodeQL uses `security-events: write` to upload SARIF results to the Security tab; without it, analysis may run but findings won’t appear in GitHub. If this change is for hardening, consider limiting the permission to the specific job instead of removing it entirely, or first verify that your CodeQL setup no longer needs to write security events.
</issue_to_address>

---

Sourcery is free for open source - if you like our reviews please consider sharing them ✨

• X
• Mastodon
• LinkedIn
• Facebook

_{Help me be more useful! Please click 👍 or 👎 on each comment and I'll use the feedback to improve your reviews.}

[sourcery-ai]

🚨 issue (security): Reconsider removing security-events: write, as CodeQL may need it to upload results.

CodeQL uses security-events: write to upload SARIF results to the Security tab; without it, analysis may run but findings won’t appear in GitHub. If this change is for hardening, consider limiting the permission to the specific job instead of removing it entirely, or first verify that your CodeQL setup no longer needs to write security events.

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 98.56%. Comparing base (8efd90f) to head (6e81df0).
⚠️ Report is 7 commits behind head on master.

Additional details and impacted files

@@           Coverage Diff           @@
##           master     #302   +/-   ##
=======================================
  Coverage   98.56%   98.56%           
=======================================
  Files           6        6           
  Lines         487      487           
=======================================
  Hits          480      480           
  Misses          7        7           

Flag	Coverage Δ
unittests	98.56% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.