hisaishi-kanade
/
CKAN-meta
mirror of https://github.com/KSP-CKAN/CKAN-meta.git
1
0
Fork 0
Code Releases Activity
CKAN-meta/builds.json

23 lines
479 B
JSON
Raw Normal View History

Create builds.json Test for new support for BuildIDs.
2016-03-30 13:55:51 +00:00
{
Update builds.json Remove platform-specific mappings. Add a `builds` key in case we need to add additional metadata in the future.
2016-03-31 11:34:59 +00:00
"builds": {
Add build 0.23.5.464 @pjf included it in his comment on KSP-CKAN/CKAN#1645
2016-04-09 14:48:08 +00:00
"464": "0.23.5.464",
Extra BuildIDs That's as far back as I can provide. I was surprised to find I still had a copy of the short-lived 1.0.5 lost build. Should we capture that buildID and handle it specially?
2016-04-09 14:26:30 +00:00
"559": "0.24.2.559",
"642": "0.25.0.642",
"705": "0.90.0.705",
"830": "1.0.0.830",
"842": "1.0.2.842",
"861": "1.0.4.861",
"1024": "1.0.5.1024",
"1028": "1.0.5.1028",
Update builds.json Remove platform-specific mappings. Add a `builds` key in case we need to add additional metadata in the future.
2016-03-31 11:34:59 +00:00
"1172": "1.1.0.1172",
Extra BuildIDs That's as far back as I can provide. I was surprised to find I still had a copy of the short-lived 1.0.5 lost build. Should we capture that buildID and handle it specially?
2016-04-09 14:26:30 +00:00
"1174": "1.1.0.1174",
New Prerelease build
2016-04-09 14:42:47 +00:00
"1183": "1.1.0.1183",
Add new BuiildID
2016-04-15 10:42:04 +00:00
"1196": "1.1.0.1196",
Add BuildID 1228
2016-04-20 07:25:40 +00:00
"1203": "1.1.0.1203",
Add BuildID 01230
2016-04-20 22:39:59 +00:00
"1228": "1.1.0.1228",
Add BuildID 1.1.1.1250 (#1110)
2016-04-29 06:43:15 +00:00
"1230": "1.1.0.1230",
Add 1.1.2.1260
2016-04-30 15:39:34 +00:00
"1250": "1.1.1.1250",
"1260": "1.1.2.1260"
Create builds.json Test for new support for BuildIDs.
2016-03-30 13:55:51 +00:00
}
}