Would it be possible tag spec versions in GitHub?
I’m currently maintaining a PHP fork of stmd.js. I’m including jgm/CommonMark (via Composer) as a dev dependency in order to test my implementation directly against the spec. Without Git tags, I can only reference the master branch or a specific commit.
Referencing master doesn’t work because spec.txt sometimes contains new changes which aren’t part of a completed version - this results in failed builds like this one.
Although I could lock to a certain commit, I feel it would be “cleaner” and easier-to-read if I could reference the specific spec version (via it’s Git tag). This would also help reduce potential confusion caused by the CommonMark repository and http://spec.commonmark.org/ showing different content for the same “version”.
I therefore propose tagging the release of each new spec version using an annotated Git tag pushed to GitLab. This should solve the issues mentioned above.