Closed Bug 1136887 Opened 5 years ago Closed 5 years ago

configure composer to install specific versions of extensions

Categories

(Websites :: wiki.mozilla.org, defect)

defect
Not set

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: ckoehler, Assigned: ckoehler)

Details

(Whiteboard: [dev=2015-02-26][stage=2015-03-05][prod=2015-03-05])

Attachments

(2 files)

Right now package versions in composer.json are indicated with ~, meaning composer will automatically download and update extensions up to the next major point release. We'd like finer control over when extensions are updated, so we need to remove the ~ or add an additional point release to the version number.

Documentation:
https://getcomposer.org/doc/01-basic-usage.md#next-significant-release-tilde-and-caret-operators-
PR submitted: https://github.com/mozilla/wiki.mozilla.org/pull/16
Whiteboard: [dev=2015-02-26]
I've merged this PR, but I want to be clear about what it's intended to do compared to what it actually does.

Not only does it pin to specific releases, but it also updates the dependencies. (You can tell by the composer.lock changes.)

Was this intentional? I'm not sure I want to merge this to production without having tested it first.
(In reply to Gordon P. Hemsley [:GPHemsley] from comment #2)
> Not only does it pin to specific releases, but it also updates the
> dependencies. (You can tell by the composer.lock changes.)

This has always been the case. Composer manages dependencies for packages regardless of how you specify their versions. There might be a way to pin the versions of the dependencies, but I don't see a good reason to do that.

We have some things to refine with regards to the composer workflow, which may address your concerns better than how versions are specified in composer.json.
This was pushed to dev this morning:
https://wiki.allizom.org/Special:Version
Whiteboard: [dev=2015-02-26] → [dev=2015-02-26][stage=2015-03-05][prod=2015-03-05]
Assignee: nobody → ckoehler
This has been pushed to dev, stage and production.
Status: NEW → RESOLVED
Closed: 5 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.