release: bump to v0.4.0 - #19
Merged
Merged
Conversation
The README named one lens when four ship, quoted a binary size from three releases ago, and printed the old version in its cargo tree 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.
Cuts v0.4.0: the release that carries the usage lenses (#7) and publishes itself
to crates.io and npm.
The bump
Cargo.toml,Cargo.lockandnpm/package.jsonto0.4.0. The crate job inrelease.ymlrefuses a tag that disagrees withCargo.toml, so this has to landbefore
v0.4.0is tagged.README, brought back in line with what ships
Three things had gone stale, none of them caught by a test:
--lens listprintsagent,atif,usageandusage-atif; the README and the--lenshelp block it quotesmentioned only
agent, which has been wrong sinceatiflanded. Thetrajectory section now shows what
--lens usagelooks like and says what the↳marks.cargo treeprintedtread v0.3.0.is 1 016 560 bytes — 992 KiB.
Verified
cargo test: 1636 passing, 0 failed.cargo test --test keymap_docs: 3 passing — the docs tests still agree withthe binary.
After this merges
Configure npm trusted publishing for
@viict/tread(repoviict/tread,workflow
release.yml, environmentPackaging), then tagv0.4.0. The tagbuilds and tests all six targets natively, cuts the GitHub release, publishes the
crate, and publishes the npm launcher once the release exists for it to read.