composer.json settings allow dev versions for php: Specify max version

Bug #1745250 reported by Rebecca Blundell on 2018-01-24
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Mahara
Status tracked in 20.04
19.10
High
Unassigned
20.04
High
Unassigned

Bug Description

Looking at composer.json to see if we should update dependencies to make tests run better, I see that our syntax for php >=5.3.3 allows any version above that specified with default stability as dev. It explains how I ended up with php 7.2 after running make initcomposer...
I think our default stability should be stable and that we should think about specifying a maximum version.

Should we also change our settings to allow some other upgrades if there is a new stable non-breaking release, or just leave things pinned? If we change to "^version", it allows upgrades up to but not including the next major version, which seems reasonable??

Robert Lyon (robertl-9) wrote :

Tagged as snacked-sized as the code change may be small but the initial testing will probably be an effort

As it will involve checking what versions of PHP work fine with current Mahara and which don't

tags: added: snack-sized
Changed in mahara:
importance: Undecided → Wishlist
status: New → Confirmed
importance: Wishlist → High
milestone: none → 19.10.0
summary: - composer.json settings allow dev versions for php
+ composer.json settings allow dev versions for php: Specify max version
Changed in mahara:
milestone: 19.10.0 → 19.10.1
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers