Uploaded image for project: 'Moodle'
  1. Moodle
  2. MDL-54899

CLONE - Update composer.json with the new moodlehq/behat-extension tag

    XMLWordPrintable

    Details

    • Testing Instructions:
      Hide

      Test 1

      1. Run behat in master branch SHOULD finish with a 100% passes (check http://integration.moodle.org, maybe the CI server already reported there)

      Test 2

      1. Run php composer.phar update
      2. Open composer.lock
      3. You SHOULD find
        "name": "moodlehq/behat-extension",
        "version": "v3.32.0",
      4. Delete vendor/ composer.lock
      5. Run again php composer.phar update
      6. Open composer.lock
      7. You SHOULD find
        "name": "moodlehq/behat-extension",
        "version": "v3.32.0",
      Show
      Test 1 Run behat in master branch SHOULD finish with a 100% passes (check http://integration.moodle.org , maybe the CI server already reported there) Test 2 Run php composer.phar update Open composer.lock You SHOULD find "name": "moodlehq/behat-extension", "version": "v3.32.0", Delete vendor/ composer.lock Run again php composer.phar update Open composer.lock You SHOULD find "name": "moodlehq/behat-extension", "version": "v3.32.0",
    • Affected Branches:
      MOODLE_32_STABLE
    • Fixed Branches:
      MOODLE_32_STABLE
    • Pull Master Branch:
      wip-mdl-54899

      Description

      In the https://github.com/moodlehq/moodle-behat-extension.git project we have different tags branches for each major release, for example 1.25.x for Moodle 2.5, this tags are created from different branches, one per moodle major release keeping the master branch according to the moodle master branch (1.26.x for Moodle 2.6dev for example) After releasing XY we should update composer.json to point to a new tag (from https://github.com/moodlehq/moodle-behat-extension.git master branch) according to the moodle development version (1.30.0 for Moodle 3.0dev for example)

      Detailed process:

        Attachments

          Issue Links

            Activity

              People

              • Votes:
                0 Vote for this issue
                Watchers:
                3 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved:
                  Fix Release Date:
                  5/Dec/16