docs: point at the latest release, and only ask for natives that exist - #4
Merged
Conversation
The README named a specific tag, so it went stale the moment upstream published anything and had to be edited on every bump. GitHub's /releases/latest never does. But a link to "latest" under the words "generated from this release" would have been a lie between bumps, so the sentence now says what is true: the binding tracks the latest stable release, and the revision actually vendored lives in binding.yml, which the CD maintains. Also stops asking for native artifacts when the job that builds them was skipped. It is skipped whenever the release has not moved -- most runs, and every republish of work already merged -- and downloading artifacts that were never produced fails the step and takes the publish with it.
Contributor
API gate: additiveEvery symbol that existed still exists, unchanged. Nothing that compiled before stops compiling.
Enum and constant values are part of the measured surface: a renumbering keeps compiling and sends the wrong number to the driver, so it counts as a removal. |
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 README named a specific tag, so it went stale the moment upstream published
anything and had to be edited on every bump. GitHub's /releases/latest never
does. But a link to "latest" under the words "generated from this release" would
have been a lie between bumps, so the sentence now says what is true: the binding
tracks the latest stable release, and the revision actually vendored lives in
binding.yml, which the CD maintains.
Also stops asking for native artifacts when the job that builds them was skipped.
It is skipped whenever the release has not moved -- most runs, and every republish
of work already merged -- and downloading artifacts that were never produced fails
the step and takes the publish with it.