Add support for CiviCRM Standalone #12
Conversation
| @@ -200,6 +203,7 @@ protected function getLatestStable() { | |||
| '[email protected]' => array('commit' => "6.x-$rev"), | |||
| '[email protected]' => array('commit' => "7.x-$rev"), | |||
| '[email protected]' => array('commit' => "8.x-$rev"), | |||
| 'civicrm-standalone' => array('commit' => $rev), | |||
There was a problem hiding this comment.
The git array defines the commits/tags that correspond to the code for a particular build. We're not actually tagging civicrm-standalone.git (and it's not used as part of that build).
I'm not sure that tags should be sync'd, since civicrm-standalone.git is more like a project-template rather than a library that one depends on. If we don't do those tags, then we shouldn't have this line.
But if you think there's a reason why we should, then this should be here. (But there are probably some other bits that will be required for that.)
|
If it's working in prod, then that's good. Probably better to merge unless there's a major problem (since that makes
Perhaps because the distmaker updates (civicrm-core#27104) are only in
👍
Makes sense, for the same reason as RC. They won't appear until 5.66-master becomes 5.66-stable (unless one specifically ports civicrm-core#27104). +1 month doesn't feel "soon" right now, but it is "soon" in the grand scheme of things... We can keep an eye after freezing for 5.66-rc in the next week. If that fixes RC, then it's reasonable to expect STABLE to will also sort out. |
Related to (merged) civicrm/civicrm-core#27104
Has been tested in prod already.
I'm not really sure why it shows for Nightly and not the RC (stable uses different code). I mostly copy-pasted what I could. (and stable builds are 404 for now, but they should soon show up, right?)