Release v0.0.4 - #7
Merged
Merged
Conversation
Bump to 0.0.4 and add the changelog entry. The release ships --json output from #6 for list, get, doctor, and service status, and the new warning when routes.json cannot be read. Co-Authored-By: Claude Opus 5 (1M context) <[email protected]> Claude-Session: https://claude.ai/code/session_01BSDFAb4giiESfUnAHgHG3S
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.
Release v0.0.4
This PR bumps the version and adds the changelog entry. It ships
--jsonfrom #6:list,get,doctor, andservice statusprint a JSON document for scripts and agents, with only the JSON on stdout and camelCase keys.list --jsonreturns the routes the proxy serves (live processes and aliases) and exits 1 whenroutes.jsoncannot be read or parsed. The release also includes the new warning whenroutes.jsoncannot be read.Merging publishes
@variablelab/[email protected]through npm trusted publishing (GitHub OIDC). It also creates thev0.0.4GitHub release from the notes inCHANGELOG.fork.md.Local checks: build, unit tests (999 passed, 1 skipped), and
npm publish --dry-run(version 0.0.4, 9 files) are green. The release notes come out of the markers the same wayrelease.ymlextracts them.🤖 Generated with Claude Code
https://claude.ai/code/session_01BSDFAb4giiESfUnAHgHG3S