fix(josh-sync): expose yq directly in the consumer devenv module
devenvModules.default only added the wrapProgram-wrapped josh-sync binary, whose bundled PATH (yq, jq, etc.) only applies while josh-sync itself runs. Plain `yq` was never actually on PATH in a consumer's devenv shell, breaking the manual `yq -i` config-editing commands the josh-sync skill's docs call for. Adds pkgs.yq-go to the module's packages list directly. Bumps to v2.3.1. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01TNXgcFWVgSh3wkQS55cCX6
This commit is contained in:
@@ -1,5 +1,11 @@
|
||||
# Changelog
|
||||
|
||||
## 2.3.1
|
||||
|
||||
### Fixes
|
||||
|
||||
- **`devenvModules.default` now exposes `yq` directly.** The `josh-sync` package it includes is `wrapProgram`-wrapped, so its bundled PATH (yq, jq, etc.) only applied while `josh-sync` itself was running — plain `yq` was never actually on PATH in a consumer's devenv shell. This broke the manual `yq -i` config-editing commands the josh-sync skill's docs call for (e.g. schema migrations) on any project without a system-wide yq install. `pkgs.yq-go` is now added to the module's `packages` list directly.
|
||||
|
||||
## 2.3.0
|
||||
|
||||
### Features
|
||||
|
||||
Reference in New Issue
Block a user