Skip to content

Symfony6 freeze#52

Merged
herbertroth merged 15 commits intomainfrom
symfony6-freeze
Nov 10, 2025
Merged

Symfony6 freeze#52
herbertroth merged 15 commits intomainfrom
symfony6-freeze

Conversation

@herbertroth
Copy link
Copy Markdown
Member

@herbertroth herbertroth commented Nov 3, 2025

This pull request updates the centralized GitHub workflow files to improve how branch-specific logic is handled, especially for installing the pimcore/symfony-freeze package based on the target branch. The changes ensure that workflows correctly identify the branch context and conditionally install dependencies, leading to more reliable and predictable CI runs.

Branch detection and environment setup:

  • Added a step to both .github/workflows/reusable-codeception-tests-centralized.yaml and .github/workflows/reusable-static-analysis-centralized.yaml to determine the target branch of the workflow run, supporting both pull requests and direct branch runs. The branch name is stored and made available for subsequent steps. [1] [2]
  • Updated environment setup steps to use the detected branch name, ensuring that any branch-specific logic or configuration is based on the correct branch context.

Conditional dependency installation:

  • Introduced a new step to check whether the target branch ends with .x. If not, the workflow installs pimcore/symfony-freeze:^6.0 and sets an environment variable to indicate the result. This prevents unnecessary installations on maintenance branches and ensures compatibility. [1] [2]

Test execution improvements:

  • Updated the Codeception test step to use the detected target branch name in its environment and output, making test runs clearer and easier to debug in CI logs.

@bluvulture bluvulture requested a review from Copilot November 5, 2025 07:21
Copy link
Copy Markdown
Contributor

Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull Request Overview

This PR introduces a Symfony 6 freeze mechanism for specific repository branches to control Symfony version constraints during CI workflows. The implementation adds a centralized configuration file and integrates version constraint logic into existing GitHub Actions workflows.

Key changes:

  • Adds a JSON configuration file to define which repository branches should use frozen Symfony 6 versions
  • Implements branch detection and configuration download steps in CI workflows to conditionally require symfony-freeze package
  • Enhances logging output in test workflows for better debugging and traceability

Reviewed Changes

Copilot reviewed 3 out of 3 changed files in this pull request and generated 2 comments.

File Description
config/symfony6-freeze.json Defines portal-engine branches (5.1, 5.0) that should use Symfony 6 freeze
.github/workflows/reusable-static-analysis-centralized.yaml Adds logic to detect target branch, download freeze config, and conditionally install symfony-freeze package
.github/workflows/reusable-codeception-tests-centralized.yaml Mirrors the freeze detection logic from static analysis workflow and adds logging for branch information

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

@bluvulture bluvulture requested a review from Copilot November 5, 2025 12:03
Copy link
Copy Markdown
Contributor

Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull Request Overview

Copilot reviewed 2 out of 2 changed files in this pull request and generated 3 comments.


💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

bluvulture
bluvulture previously approved these changes Nov 5, 2025
Copy link
Copy Markdown
Contributor

@bluvulture bluvulture left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

lgtm - check does the suggestions from Copilot are valid ones

Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>
herbertroth and others added 2 commits November 10, 2025 09:57
Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>
Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>
@kingjia90
Copy link
Copy Markdown
Contributor

There's something wrong in this logic, it seems that it is always testing on the files on the base branch instead of the files in the PR/branch to be merged.

@kingjia90
Copy link
Copy Markdown
Contributor

kingjia90 commented Nov 11, 2025

Extra notes on the noticed an "odd" behavior:

Maybe it's not even this PR, because something happened even before this being merged... the tests were passing on pimcore/pimcore#18809 (which code/pr was wrong) and master 11.5 failed as expected.

Added new tests pimcore/pimcore#18814 but not appearing in the codeception run
image
false positive passed, but i am sure if i merge this PR, it would run the newly added tests and pass/fail eventually

@kingjia90
Copy link
Copy Markdown
Contributor

Also in this PR, any changes before pimcore/pimcore#18814 a6b787b should have triggered an error because it was clearly wrong in the tests
image

@kingjia90
Copy link
Copy Markdown
Contributor

kingjia90 commented Nov 13, 2025

Update: all good here, the problem described is not related to this PR, the affected workflow in use is not even the one modified here. That was just a coincidence. We (or better saying Nebojsa) are fixing it.

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.

4 participants