tonyair
/
silverstripe-installer
mirror of https://github.com/silverstripe/silverstripe-installer
1
0
Fork 0
Code Issues Projects Releases Wiki Activity
silverstripe-installer/composer.json

31 lines
739 B
JSON
Raw Normal View History

Added composer.json Once we've sorted out packagist listing ownership, we should be able to remove the custom repository entries.
2012-11-01 17:26:18 +01:00
{
"name": "silverstripe/installer",
"description": "The SilverStripe Framework Installer",
"require": {
Update PHP min version and PHPUnit version
2017-03-24 12:20:44 +01:00
"php": ">=5.6.0",
Remove self.version (#138) Lock dev branches to dev
2016-09-20 00:20:52 +02:00
"silverstripe/cms": "4.0.x-dev",
"silverstripe/framework": "4.0.x-dev",
Fix dev dependencies for root project
2017-03-16 04:01:15 +01:00
"silverstripe/config": "1.0.x-dev",
Add admin module to root installer
2017-03-10 03:17:14 +01:00
"silverstripe/admin": "1.0.x-dev",
Add assets as module
2017-03-16 04:51:44 +01:00
"silverstripe/assets": "1.0.x-dev",
Remove self.version (#138) Lock dev branches to dev
2016-09-20 00:20:52 +02:00
"silverstripe/reports": "4.0.x-dev",
"silverstripe/siteconfig": "4.0.x-dev",
"silverstripe-themes/simple": "~3.2.0",
Added GraphQL dependency This is required here in order for the "cow" release tool to include the module in tagging releases. At the moment, it's only an indirect asset-admin dependency, but will become a framework dependency once we switch CampaignAdmin to use GraphQL as well.
2017-01-16 23:44:33 +01:00
"silverstripe/asset-admin": "1.0.x-dev",
"silverstripe/graphql": "0.2.x-dev"
Added composer.json Once we've sorted out packagist listing ownership, we should be able to remove the custom repository entries.
2012-11-01 17:26:18 +01:00
},
Added phpunit to dev dependencies
2015-02-26 02:21:47 +01:00
"require-dev": {
Update PHP min version and PHPUnit version
2017-03-24 12:20:44 +01:00
"phpunit/PHPUnit": "^5.7"
Added phpunit to dev dependencies
2015-02-26 02:21:47 +01:00
},
Merge remote-tracking branch 'origin/3.1' Conflicts: composer.json
2013-05-31 18:10:15 +02:00
"extra": {
Updated composer.json
2012-12-11 18:01:38 +01:00
"branch-alias": {
Update branch alias for master
2014-11-20 05:19:24 +01:00
"dev-master": "4.0.x-dev"
Fixed composer.json (merge error)
2013-06-02 20:38:13 +02:00
}
Include a higher timeout value to avoid timeouts. Checking out framework can often take longer than the default (300 seconds). This gives a 10min limit to creating a new project.
2013-03-06 08:22:48 +01:00
},
"config": {
Added phpunit to dev dependencies
2015-02-26 02:29:38 +01:00
"process-timeout": 600
Include a higher timeout value to avoid timeouts. Checking out framework can often take longer than the default (300 seconds). This gives a 10min limit to creating a new project.
2013-03-06 08:22:48 +01:00
},
Prefer stable packages while still allowing dev ones. Fixes #100 Although the original ticket recommended increasing our minimum-stability, this change gives us the best of both worlds. - Where stable packages are available and meet the requirements, they will be used. - Where stable packages aren’t available or they don’t meet the dependency requirements, non-stable packages are still allowed. As part of this I have also tightened up the silverstripe-themes req version, as “*” is an anti-pattern. The versioning of the theme has rightly split off from the versioning of the framework; it looks like 3.1.* is what we should expect. Arguably, we could set the dependency to ~3.1, but in this case I think it’s fine to be conservative.
2015-07-03 18:34:58 +02:00
"prefer-stable": true,
Added composer.json Once we've sorted out packagist listing ownership, we should be able to remove the custom repository entries.
2012-11-01 17:26:18 +01:00
"minimum-stability": "dev"
NEW: Added dev dependencies to composer. FIX: Don't hardcode framework and cms version in installer.
2012-11-04 09:24:59 +01:00
}