[Feature] Create a release

[TimidRobot]

Problem

1. Production/Staging installation is done via composer
2. composer uses releases
3. there is not yet a release

Description

Create a release

Additional context

• "External" Composer version numbers must be prefixed with v (ex. v0.1.0)
  • Versions and constraints - Composer
  • Git Tags
  • GitHub Releases
• "Internal" Composer version numbers and WordPress version numbers must not be prefixed (ex. 0.1.0)
  • composer.json
  • PHP files
  • WordPress readme.txt
  • etc.

[TimidRobot]

Related: [Feature] Support WordPress installation and updates via composer · Issue #213 · creativecommons/project_creativecommons.org

[brylie]

Hei @TimidRobot. I can't find the Composer docs related to the external version number prefixing. All I have found are the following, which don't seem to indicate the v prefix.

• https://getcomposer.org/doc/04-schema.md#version
• https://getcomposer.org/doc/05-repositories.md

I don't mind following the v prefix convention if it is mandatory but would prefer dropping the v if things work without it.

[brylie]

Release v2022.2.1: https://github.com/creativecommons/wp-plugin-creativecommons-website/releases/tag/v2022.2.1

[TimidRobot]

@brylie I added the v prefix requirements to our WordPress Development Process internal documentation on 2021-07-01. Unfortunately, I did not document the exact error encountered.

SemVer required the prefix in the past (ex. semver/semver#1, semver/semver#204, https://stackoverflow.com/a/2011372), but I can't find anything concrete about composer requiring it. I suspect it's poorly documented because removing a requirement is a non-breaking change.

I recommend we experiment with non-prefixed tags/releases on a non-essential or test package. Or that we wait until we're not under a deadline.