Skip to content

Merge release 3.7.1 into 3.8.x - #12614

Merged
greg0ire merged 10 commits into
3.8.xfrom
3.7.x-merge-up-into-3.8.x_kCEwSkAi
Sep 14, 2026
Merged

greg0ire merged 10 commits into
3.8.xfrom
3.7.x-merge-up-into-3.8.x_kCEwSkAi

Conversation

@github-actions

Copy link
Copy Markdown
Contributor

Release Notes for 3.7.1

3.7.1

  • Total issues resolved: 0
  • Total pull requests resolved: 2
  • Total contributors: 1

Bug

greg0ire and others added 10 commits September 7, 2026 21:51
3.7.0 has been released.

As a consequence:
- 3.8.x is the next minor branch;
- 3.7.x is the current branch;
- 3.6.x is no longer maintained.
These 3 versions have less than 2k daily downloads.
This was introduced in d4dc768. 3.6
supports having an STI hierarchy where multiple child entities use the
same join column for associations that target different entities.

SchemaTool does not create foreign keys because they would conflict, and
creates an index instead, and that index must be added only once.
In 6af7de3, I removed redundant EventManager::hasListeners() checks.
In parallel to that, I did a change on 3.6.x to the same piece of code
to replace the schema instance.
Then, during a merge up, I kept both branches of the conflict.
…-docs

Update documentation for SchemaTool DROP_DATABASE / dropDatabase
Ensure ToolEvents::postGenerateSchema is called once
Avoid creating duplicate index for conflicting STI associations
@greg0ire
greg0ire merged commit 0ece868 into 3.8.x Sep 14, 2026
166 checks passed
@greg0ire
greg0ire deleted the 3.7.x-merge-up-into-3.8.x_kCEwSkAi branch September 14, 2026 06:18
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