Skip to content

Conversation

@jwong-dayspring
Copy link

We use PropelBundle and Propel1, and are trying to keep up with Symfony LTS. Since Propel2 is still in alpha, we made updates to PropelBundle to allow for Symfony 4 with Propel1.

This really ought to be against a "1.7" branch, but there isn't one in the upstream project.

jwong-dayspring and others added 24 commits May 11, 2018 15:17
…o resolve deprecation warnings for symfony 3.2
detect and handle difference in yaml format from symfony/yaml 3.3 and 3.4
fix issue with rendering propel profiler
* initial commit

* composer validate and install

* fix indentation

* bump to latest version (1.7.2)

* run phpunit tests

* remove jenkins suffix from phpunit dist filename

* add end of file newline

* add php matrix

* disable fail-fast

* set continue-on-error for experimental

* set default for experimental

* add composer prefer-lowest

* remove php 8.0

* remove travis ci

* fix format

* rename to ci.yml for better clarity

* remove php 8 experimental again

* remove continue-on-error

Co-authored-by: Jeffrey Wong <jwong@dayspring-tech.com>
@dereuromark
Copy link
Contributor

Shall we revive this?

@dereuromark
Copy link
Contributor

All propel 2 dev should go into https://github.com/SkyFoxvn/PropelBundle as this will most likely be the follower of this now.
But 1.x issues could still be released here.

"propel/propel1": "^1.6.8",
"symfony/framework-bundle": "^3.0.2"
"propel/propel1": "^1.7.2",
"symfony/framework-bundle": "^3.4|^4.0"
Copy link
Contributor

Choose a reason for hiding this comment

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

Can we state the major PHP versions we support?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants