Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merge release 2.10.0 into 3.0.x #9066

Merged
merged 24 commits into from
Oct 3, 2021

Conversation

github-actions[bot]
Copy link
Contributor

@github-actions github-actions bot commented Oct 3, 2021

Release Notes for 2.10.0

2.10.0

  • Total issues resolved: 4
  • Total pull requests resolved: 56
  • Total contributors: 9

CI

Improvement

Bug

Deprecation

Documentation

Deprecation,Improvement

BC Break,Deprecation

New Feature

Backporting

BC Break,Backporting

Backporting,Improvement

sztyup and others added 24 commits September 30, 2021 23:29
…lumns

Remove calls to `ForeignKeyConstraint::getColumns()`
Signed-off-by: Alexander M. Turek <[email protected]>
* 2.9.x:
  Run PHP 8.1 CI with stable dependencies (#9058)
  Duplicate testTwoIterateHydrations (#9048)
  Add PHP 8.1 to CI (#9006)
  Fix locking non-existing entity (#9053)

Signed-off-by: Alexander M. Turek <[email protected]>
1.12.0 and up comes with a migration to azjezz/psl that makes it
impossible to troubleshoot issues with external commands such as git push
1.12.0 and up comes with a migration to azjezz/psl that makes it
impossible to troubleshoot issues with external commands such as git push
To avoid recursive workflows, Github will prevent the release bot from
pushing tags because that would result in a new workflow being triggered.
To avoid recursive workflows, Github will prevent the release bot from
pushing tags because that would result in a new workflow being triggered.
Despite what is described in the docs, it seems that there is still an
attempt to run a workflow for tags.
…for-tags

Explicitly disallow workflows for tags
My previous attempts to disallow running a workflow when pushing a tag
failed, so let's ensure we can run said workflow. Maybe we will be able
to understand why it happened after it happens.
@greg0ire greg0ire merged commit bcd6ac8 into 3.0.x Oct 3, 2021
@greg0ire greg0ire deleted the 2.10.x-merge-up-into-3.0.x_6159cb4217e697.30353290 branch October 3, 2021 20:59
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.

3 participants