Repository navigation
The pins and the download URLs move with the release - #19
Merged
Merged
Conversation
The site installs the three libraries as path repositories and names a released version twice — once in `require` and once in the path repository's `versions` map — so both have to move to the version that was just released. The directives package goes to 0.3.1 and the two converters to 0.3.0, and the lock follows the pins: a lock that names an older version fails the install rather than the build, and the message names the repository that is outranked. The assets of `mdoffice` are named after the version, so the three download URLs and the ARM asset one of them names move to 0.1.2. A URL naming a version that was never published is a 404 forever.
The page shows what an installed copy answers, and the answer changed with the release: the tool is `0.1.2`, and it holds the `v0.3.0` of both converters. The libraries were read from the install rather than declared, so the numbers are the ones the program prints. That includes the `v` in front of the library versions, which the transcript was missing: a released copy reads its libraries from Packagist, where the version is the tag — `v0.3.0` — and the published `0.1.1` answers `v0.2.2` on both lines. A checkout answers with the branch it resolved rather than with a release, which is what the prose below the transcript says, and the padding is the program's own: the version starts in the same column on both lines, in the transcript and in the output.
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The site installs the three libraries as path repositories and names a released version twice — once in
requireand once in the path repository'sversionsmap — so both have to move, and they have to agree: a pin that names an older version in one place fails the install rather than the build, and the message names the repository that is outranked.commonmark-generic-directives0.3.00.3.1markdown-worddev-main0.3.0markdown-presentationdev-main0.3.0composer.lockfollows the pins, because a lock that does not satisfycomposer.jsonfailscomposer installoutright. The update was limited to those three; nothing else moved.The download URLs.
mdoffice's assets are named after the version, so every URL that names an asset has to name the version that is published — a URL naming a version that was never published is a 404 forever. Five changed, all of them underreleases/latest/download/: the Linux, macOS and phar URLs on the installation page, the ARM asset it names, and the one on the front page.The
--versiontranscript. The page shows what an installed copy answers, and it was showingmdoffice 0.1.1with the libraries at0.2.2. It now showsmdoffice 0.1.2with the libraries atv0.3.0.The
vis what the program prints: a released copy reads its libraries from the install, where Packagist's version is the tag name. That was checked against the published 0.1.1 executable and the published phar, which both printv0.2.2— so the page was missing thevbefore this change as well. The transcript is now the program's own output, character for character.What is left
This is the last thing to change, and it should be merged after the four releases are published — the URLs it carries are 404 until then.