Skip to content

Conversation

@Cmdv
Copy link
Contributor

@Cmdv Cmdv commented Nov 6, 2025

Description

Add your description here, if it fixes a particular issue please provide a link to the issue.

Checklist

  • Commit sequence broadly makes sense
  • Commits have useful messages
  • New tests are added if needed and existing tests are updated
  • Any changes are noted in the changelog
  • Code is formatted with fourmolu on version 0.10.1.0 (which can be run with scripts/fourmolize.sh)
  • Self-reviewed the diff

Migrations

  • The pr causes a breaking change of type a,b or c
  • If there is a breaking change, the pr includes a database migration and/or a fix process for old values, so that upgrade is possible
  • Resyncing and running the migrations provided will result in the same database semantically

If there is a breaking change, especially a big one, please add a justification here. Please elaborate
more what the migration achieves, what it cannot achieve or why a migration is not possible.

@Cmdv Cmdv requested a review from a team as a code owner November 6, 2025 15:23
@Cmdv Cmdv force-pushed the feature/perf-improvements branch 2 times, most recently from 3f766aa to cc58d4e Compare November 12, 2025 12:20
@Cmdv Cmdv force-pushed the feature/perf-improvements branch from cc58d4e to 61103a4 Compare November 13, 2025 10:21
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.

2 participants