chore: release v0.3.0-preview.1 - #9
Merged
Merged
Conversation
A preview, because plugin loading is new and has only been run on macOS and Linux. It is a GitHub pre-release, which is the whole mechanism: `godo -e update` reads the newest *release*, and the Homebrew cask and Scoop manifest are left alone, so nobody arrives at a preview without going to get it. Also here because the preview is otherwise a trap: - `go install …/cmd/godo@v0.3.0-preview.1` links none of our -ldflags, so the binary reported 0.1.0-dev and `engine.version: ">=0.3.0"` refused a catalog it actually satisfied. The tag now comes from Go's build info, read through godo.Release(). A build from a working tree still says 0.1.0-dev: Go names it with a pseudo-version, and nobody released that. - The changelog still said "Nothing loads plugins yet", and never said plugins run — the release's whole point. - A rebase had copied the --flag= quoting fix into the released [0.1.0] section. A released section does not gain entries.
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
1 participant
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.
Prepares the preview tag.
Why a preview. Plugin loading is new and has been run on macOS and Linux
only. A GitHub pre-release is the whole mechanism:
godo -e updatereads/releases/latest, which GitHub answers with the newest release, and theHomebrew cask and Scoop manifest are skipped for a tag with a pre-release part.
Nobody arrives at a preview without going to get it.
The trap this also closes
go install github.com/my-rv/godo/cmd/godo@v0.3.0-preview.1links none of our-ldflags, so the binary reported0.1.0-dev— cosmetic untilengine.versionexisted, and then enough to make a catalog refuse a binary that satisfied it.
godo.Release()now takes the tag from Go's build info whenVersionis stillthe default. A build from a working tree keeps saying
0.1.0-dev: Go names itwith a pseudo-version, and nobody released that.
Also
which is the release.
--flag=quoting fix into the released[0.1.0]section. Removed — a released section does not gain entries.
docs/roadmap.mdv0.3 was "held until plugin loading works". It works../godo cigreen.