Skip to content

chore: bump version to 3.35.0 - #964

Merged
fernandotonon merged 1 commit into
masterfrom
chore/release-3.35.0
Aug 30, 2026
Merged

chore: bump version to 3.35.0#964
fernandotonon merged 1 commit into
masterfrom
chore/release-3.35.0

Conversation

@fernandotonon

@fernandotonon fernandotonon commented Aug 29, 2026

Copy link
Copy Markdown
Owner

Release bump for the text-to-motion v8.0 work merged in #963.

Ships:

  • t2m v8.0 — trained on the curated template clips instead of the CMU corpus, which never carried the correct facing convention. Generated clips now face the right way.
  • Leg-chain fix — a walk's bend stays in the knee rather than the ankle (the defect that rendered as a false second knee). Knee/ankle 41°/8° vs a real reference walk's 38°/10°; leg-chain penalty 0.359 → 0.0003.
  • Data gates — anatomical ankle gate and a minimum-resolved-roles floor drop four actions whose source clips were broken (march/throw/hey/confession); those prompts fall back to the curated templates.

Model and the 150-clip training library are published on HuggingFace; the app downloads the model on first use.

Version synced across README and the website action ref via scripts/sync-doc-versions-from-cmake.sh.

🤖 Generated with Claude Code

Summary by CodeRabbit

  • Release
    • Updated QtMeshEditor to version 3.35.0 across the application and related resources.
    • Updated documentation, CI examples, container references, and reproducible-build instructions to reflect version 3.35.0.

Ships the text-to-motion v8.0 model (#837, PR #963): template-taught so
generated clips face the right way, plus the leg-chain fix that keeps a walk's
bend in the knee rather than the ankle.
@coderabbitai

coderabbitai Bot commented Aug 29, 2026

Copy link
Copy Markdown

Review Change Stack

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info
⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro Plus

Run ID: e48a7c7d-8522-417b-83bb-72ba741fead9

📥 Commits

Reviewing files that changed from the base of the PR and between c41fb55 and 3618d0e.

📒 Files selected for processing (3)
  • CMakeLists.txt
  • README.md
  • website/src/hooks/useQtmeshActionRef.js

Included review availability: Your plan provides up to 1 included review per hour; 0 remain after this review.


📝 Walkthrough

Walkthrough

The project version changes to 3.35.0. README examples and the website action fallback now reference the same version.

Changes

Version synchronization

Layer / File(s) Summary
Update canonical project version
CMakeLists.txt
The CMake project declaration changes the QtMeshEditor version from 3.34.0 to 3.35.0.
Update release references
README.md, website/src/hooks/useQtmeshActionRef.js
README action and container examples and the website fallback change from 3.34.0 to 3.35.0.

Estimated code review effort: 2 (Simple) | ~10 minutes

Merge Risk: ⚪ Minimal · up to 3618d

This PR updates release-version references for 3.35.0 without changing application behavior or introducing new dependencies or permissions; no actionable merge-blocking risk remains after normal checks and review.

🚥 Pre-merge checks | ✅ 5
✅ Passed checks (5 passed)
Check name Status Explanation
Title check ✅ Passed The title clearly and concisely identifies the main change: bumping the project version to 3.35.0.
Description check ✅ Passed The description provides a relevant summary and technical details for the 3.35.0 release. It also identifies version synchronization and explains the text-to-motion v8.0 work. The required headings ar…
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff. Analyzed 0 functions across 1…
Linked Issues check ✅ Passed Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check ✅ Passed Check skipped because no linked issues were found for this pull request.
Full details: Description check

Explanation

The description provides a relevant summary and technical details for the 3.35.0 release. It also identifies version synchronization and explains the text-to-motion v8.0 work. The required headings are not used exactly, but the required information is mostly present.

Full details: Docstring Coverage

Explanation

No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff. Analyzed 0 functions across 1 files. (2 skipped: 2 unsupported.)

✨ Finishing Touches
📝 Generate docstrings
  • Create stacked PR
  • Commit on current branch
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch chore/release-3.35.0

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands.

@sonarqubecloud

Copy link
Copy Markdown

@fernandotonon
fernandotonon merged commit 042cc02 into master Aug 30, 2026
24 checks passed
@fernandotonon
fernandotonon deleted the chore/release-3.35.0 branch August 30, 2026 00:19
fernandotonon added a commit that referenced this pull request Aug 30, 2026
Branch protection requires a status context named plain `build-linux`, but the
job is a matrix and GitHub derives its check name from EVERY matrix parameter,
so it reported as:

    build-linux (amd64, ubuntu-latest, linux, linux_gcc_64, gcc_64, x86_64-linux-gnu)

The bare `build-linux` context therefore never appeared, sat pending forever,
and every PR showed BLOCKED with nothing actually failing — #963 and #964 both
had to be merged by hand despite 18 green checks.

Pin `name: build-linux (${{ matrix.arch }})` so the job reports as
`build-linux (amd64)` / `build-linux (arm64)`: short, stable, and unaffected
if the matrix gains or loses parameters later.

The required contexts still need updating from `build-linux` to those two
names — a repo-settings change, done separately.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant