chore: bump version to 1.4.0 - #744
Merged
Merged
Conversation
Release v1.4.0: Vulkan backend, all four engines in the archives, Kimi K3 GPU tier
c/version.py is the single source of truth and the release archives carry it, so this has to land before the tag or the published binaries announce 1.3.0. The four README sample banners go with it -- they went stale for two releases running before #709 caught them at 1.1.0. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
JustVugg
force-pushed
the
chore/bump-1.4.0
branch
from
August 1, 2026 02:25
300f74c to
a489e1b
Compare
Claude Code keeps agent worktrees and session scratch under .claude/. A 'git add -A' picked one up as an embedded git repository while preparing the 1.4.0 bump; it was caught before the PR was reviewed, but the guard belongs in the tree rather than in whoever runs the next 'add -A'. Co-Authored-By: Claude Opus 5 <noreply@anthropic.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
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.
Version bump ahead of the
v1.4.0tag.c/version.pyis the single source of truth and the release archives carry it, so this has to land before the tag — otherwise the published binaries announce 1.3.0.The four README sample banners go with it. They went stale for two releases running before #709 caught them sitting at 1.1.0, so they are bumped in the same commit rather than remembered separately.
Targets
mainbecause the tag is cut frommainanddevis already identical to it (0 commits apart). It will flow back with the nextdevsync.