Skip to content

chore: release v0.17.0 #493

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
lroolle merged 1 commit into from
Jul 27, 2026
Merged

chore: release v0.17.0 #493

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
17 changes: 17 additions & 0 deletions CHANGELOG.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -7,6 +7,8 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0

## [Unreleased]

## [0.17.0] - 2026-07-27

@chatgpt-codex-connector chatgpt-codex-connector Bot Jul 27, 2026

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P2 Badge Update the released Kimi pin

Publishing the existing notes under the new 0.17.0 header makes them state that KIMI_CODE_VERSION is pinned at 0.28.0, while this commit's release tree has KIMI_CODE_VERSION=0.29.2 in versions.env. Anyone using the release notes to reproduce or audit the shipped image receives the wrong version, so update the Kimi pin stated in this release section to 0.29.2.

Useful? React with 👍 / 👎.


### Added
- kimi agent (Moonshot Kimi Code CLI, #455): `deva.sh kimi` launches the
official `@moonshot-ai/kimi-code` CLI like claude/codex/gemini/grok.
Expand Down Expand Up @@ -76,6 +78,21 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
back to the config value. Precedence is now environment > config files >
`-p` profile > default, with explicit CLI `-p` beating a config-file tag.
Guarded by `scripts/test-image-precedence.sh` in CI.
- `--dry-run` pulled images and rewrote the resolved tag: `check_image` ran
unconditionally, so a dry run could fetch a multi-GB image and, when the
requested tag was missing, its availability fallback rewrote
`DEVA_DOCKER_TAG` — reporting a tag the user never asked for. Resolution
is what `--dry-run` reports; availability is a launch-time concern.
- `deva.sh` exited silently when docker rejected a `.deva` mount (#484):
"Creating persistent container: <name>" and nothing else. Under
`set -euo pipefail` a failing command-substitution assignment aborts at
the assignment, so `docker_exit=$?` and the whole error block below it
were dead code on the one path they exist for. docker's own stderr now
surfaces.
- `update-version-pins.sh` aborted the whole sweep when a single registry
fetch failed (same `set -e` assignment trap), and skipped rewriting
`versions.env` when nothing moved — leaving the heredoc round-trip guard
unexercised on exactly the runs where every fetch failed.

## [0.16.0] - 2026-07-14

Expand Down
2 changes: 1 addition & 1 deletion deva.sh
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -21,7 +21,7 @@ if [ -n "${DEVA_DOCKER_TAG+x}" ]; then
DEVA_DOCKER_TAG_SOURCE="env"
fi

VERSION="0.16.0"
VERSION="0.17.0"
DEVA_DOCKER_IMAGE="${DEVA_DOCKER_IMAGE:-ghcr.io/thevibeworks/deva}"
DEVA_DOCKER_TAG="${DEVA_DOCKER_TAG:-latest}"
DEVA_CONTAINER_PREFIX="${DEVA_CONTAINER_PREFIX:-deva}"
Expand Down
Loading