[fabeat]

Merge this last. It names versions that the three release pull requests publish,
and the download URLs it carries are the assets of a release that does not exist yet.

The pin moves with the release. The site installs the three libraries as path
repositories and pins the version it installs, so it names a released version twice
— once in require and once in the path repository's versions map — and both
move together. A pin that names an older version fails the install rather than the
build.

markdown-office/markdown-word	0.3.1 → 0.4.0
markdown-office/markdown-presentation	0.3.1 → 0.4.0
markdown-office/commonmark-generic-directives	0.3.1, unchanged — there is nothing new in it

The pages follow:

• the installation page's download URLs name mdoffice-0.2.0-…
• the --version sample names mdoffice 0.2.0 and the two libraries at v0.4.0
• the Composer install asks for ^0.2 of markdown-office/mdoffice, which is the
  series this release carries

The order this suite releases in:

1. markdown-office/markdown-word v0.4.0 and markdown-office/markdown-presentation
   v0.4.0 are tagged and published.
2. markdown-office/mdoffice v0.2.0 is tagged and published, and the pipeline is run
   without a tag first.
3. This pull request is merged.

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud