mahara-contributors team mailing list archive

[Rebecca Blundell <1745250@xxxxxxxxxxxxxxxxxx>]

This was fixed in another patch:
https://bugs.launchpad.net/mahara/+bug/1772792


** Changed in: mahara/20.04
       Status: In Progress => Fix Released

** Changed in: mahara/19.10
       Status: Confirmed => Fix Released

** No longer affects: mahara/20.04

** No longer affects: mahara/19.10

** Changed in: mahara
    Milestone: 20.04.0 => None

-- 
You received this bug notification because you are a member of Mahara
Contributors, which is subscribed to Mahara.
Matching subscriptions: Subscription for all Mahara Contributors -- please ask on #mahara-dev or mahara.org forum before editing or unsubscribing it!
https://bugs.launchpad.net/bugs/1745250

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

Status in Mahara:
  Fix Released

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??

To manage notifications about this bug go to:
https://bugs.launchpad.net/mahara/+bug/1745250/+subscriptions