Background

We're still on v0.1.0 for the extension. While extension versioning is mostly neglected in our continuous development environment, we should bump the version number before rolling out experiment to separate from ancient extension time.
Following that logic, it's clear that adhering to semver logic were a good choice.

https://www.mediawiki.org/wiki/Extension:ReadingLists

Proposal

Bump extension in beta to a version like 0.9.0 or 0.10.0 to set it clearly apart from before (even Dillon's changes would have already jumped a number of version. Or consider even a 1.0.0-beta.1

Requirement

Scope: ReadingLists extension (desktop + mobile).

• Update the ReadingLists extension version number from v0.1.0 to v1.0.0-beta.1 in extension.json.
• This version bump distinguishes the current experiment release from legacy versions and aligns with semantic versioning (semver) conventions.
• After deployment, the new version number should display on the Special:Version page under the ReadingLists entry.

BDD

Feature: ReadingLists version bump for experiment launch

  Scenario: Viewing ReadingLists extension version
    Given the updated ReadingLists extension is deployed
    When I visit the Special:Version page
    Then the ReadingLists extension version displays as `1.0.0-beta.1`

Test Steps

Test Case 1: Verify ReadingLists version bump

1. Navigate to Special:Version on the wiki.
2. Locate the ReadingLists extension entry.
3. AC1: The version number shown is 1.0.0-beta.1.

QA Results - Prod