docs + brew: ship 0.2.111 notes and Homebrew formula - #275
Draft
huyplb wants to merge 2 commits into
Draft
Conversation
User-facing What's new for the v0.2.111 ship (History revert, SQL Editor, dialect generator fixes) since the last npm/Homebrew publish at 0.2.73. Co-authored-by: huy.phan9 <huyplb@users.noreply.github.com>
Point the Homebrew formula at the published npm tarball and note that 0.2.111 is on the registry. Co-authored-by: huy.phan9 <huyplb@users.noreply.github.com>
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.
Ship notes + Homebrew formula for Fox Schema 0.2.111. The
v0.2.111tag already exists onca34cea. Do not move the tag.Published
foxschemalateston registry.npmjs.org5nickels/foxschema:v0.2.111andghcr.io/tedious-code/foxschema:v0.2.111(+:latest)d0981ee0…173d7fd6docs/RELEASE_0.2.111.mdStill needed (GitHub Release)
In-app What's new links to the GitHub Release page. Create it after this merges (tag already exists):
gh release create v0.2.111 --title "0.2.111" --notes-file docs/RELEASE_0.2.111.mdCI token
Repo secret
NPM_TOKENstill 404s onPUT(every Actions publish since 0.2.71). Replace it in GitHub → Settings → Secrets with an Automation token for thetedious-codenpm user so the next tag can ship from CI. Do not paste tokens into chat or commit them.