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

Update composer.json with the new moodlehq/behat-extension tag for 4.0dev (and exceptionally, 3.10dev)

    XMLWordPrintable

Details

    • MOODLE_310_STABLE
    • MOODLE_310_STABLE
    • Hide

      Requirements

      terminal access and PHP 7.2 cli

      In the master branch only:

      Test 0
      1. Skip this step, nothing to do, dear tester, integrators will deal with this. Verify that both phpunit and behat runs are installing and passing ok for master.
      Test 1

      (better use composer >= 1.10, to avoid some time format differences)

      1. Open a terminal and navigate to your moodle root directory.
      2. Run php composer.phar update
      3. Open composer.lock on a text editor.
      4. You SHOULD find
        "name": "moodlehq/behat-extension",
        "version": "3.400.0",
        with "url": "https://github.com/moodlehq/moodle-behat-extension.git",
      5. Back on your terminal, delete the "vendor" folder and "composer.lock". Also remove composer caches.

        rm -rf vendor
        rm composer.lock
        php composer.phar clearcache
        

      6. Run again php composer.phar update
      7. Open composer.lock on a text editor
      8. You SHOULD find
        "name": "moodlehq/behat-extension",
        "version": "3.400.0",
        with "url": "https://github.com/moodlehq/moodle-behat-extension.git",

      Note: the local run of composer update may lead to some other small differences (git diff composer.lock) if some dependency packages were updated the last hours @ packagist. They can be ignored, unless there is something really big detected.

      In the MOODLE_310_STABLE branch only:

      1. Repeat the tests performed in the previous section for "master".
      2. Verify, when looking within the composer.lock file, that the version is now:
        "version": "3.310.0"
        (i.e. 310 instead of 400)
      Show
      Requirements terminal access and PHP 7.2 cli In the master branch only: Test 0 Skip this step, nothing to do, dear tester , integrators will deal with this. Verify that both phpunit and behat runs are installing and passing ok for master. Test 1 (better use composer >= 1.10, to avoid some time format differences) Open a terminal and navigate to your moodle root directory. Run php composer.phar update Open composer.lock on a text editor. You SHOULD find "name": "moodlehq/behat-extension", "version": "3.400.0", with "url": "https://github.com/moodlehq/moodle-behat-extension.git", Back on your terminal, delete the " vendor " folder and " composer.lock ". Also remove composer caches. rm -rf vendor rm composer.lock php composer.phar clearcache Run again php composer.phar update Open composer.lock on a text editor You SHOULD find "name": "moodlehq/behat-extension", "version": "3.400.0", with "url": "https://github.com/moodlehq/moodle-behat-extension.git", Note: the local run of composer update may lead to some other small differences ( git diff composer.lock ) if some dependency packages were updated the last hours @ packagist. They can be ignored, unless there is something really big detected. In the MOODLE_310_STABLE branch only: Repeat the tests performed in the previous section for "master". Verify , when looking within the composer.lock file, that the version is now: "version": "3.310.0" (i.e. 310 instead of 400)

    Description

      Special notes (for this issue only):

      Note: This must be done for as many dev branches still not having their corresponding tags. Normally it's only master, but under parallel development periods, when it could be (together with or alternatively) an XXX_STABLE dev branch. Of course it requires the dev branches to exist, cannot be done before that.


      ^^^ In this case, it's together with the 311_STABLE branch, master too.


      After releasing XY we should update composer.json in master to point to a new tag (from https://github.com/moodlehq/moodle-behat-extension.git master branch) according to the moodle development version (3.310.0 for Behat 3 and Moodle 3.10dev for example - and 3.400.0 for Behat 3 and Moodle 4.0dev - this issue).

      Detailed process:

      https://docs.moodle.org/dev/Release_process#2_weeks_after

      After creating the branch & tag and pushing it upstream... verify the new version has been released in packagist (it happens automatically - hooks are enabled since v3.36.x - or under demand if a package maintainer is asked). Link:

      https://packagist.org/packages/moodlehq/behat-extension

      Then, in the master branch, edit composer.json and bump the "moodlehq/behat-extension" to the newly created tag.

      To regenerate the composer.lock file, follow the instructions available @ Moodle Docs.

      Ensure changes related to the extension are ok in the .lock file (version, pointing to moodlehq repo...). It will come also with updates to many of the dependencies. Run behat tests and phpunit tests to confirm they work ok.

      Attachments

        Issue Links

          Activity

            People

              stronk7 Eloy Lafuente (stronk7)
              stronk7 Eloy Lafuente (stronk7)
              moodle.com moodle.com
              Sara Arjona (@sarjona) Sara Arjona (@sarjona)
              Janelle Barcega Janelle Barcega
              Andrew Lyons, Huong Nguyen, Jun Pataleta, Michael Hawkins, Shamim Rezaie, Simey Lameze, Stevani Andolo
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved:
                9/Nov/20

                Time Tracking

                  Estimated:
                  Original Estimate - 0 minutes
                  0m
                  Remaining:
                  Remaining Estimate - 0 minutes
                  0m
                  Logged:
                  Time Spent - 4 hours, 31 minutes
                  4h 31m