chore: bump Framework to 4.40.0 and CLI to 3.41.0 - #406
Merged
Conversation
Releases the three adopter-triage batches (PRs #403, #404, #405): nine issues remediated. Framework touched in all three (telemetry schema + charter templates, .qoder/skills + manifest, backlog pattern doc) → minor fw bump; CLI gains followups merge-driver (#391), the FOLLOWUP-UNTRACKED-ID validate warning (#392) and Qoder skills (#399) → minor CLI bump (docs already cite cli-3.41.0 for these features). Version tables updated in README + CLI-REFERENCE (en/es/zh-CN); CHANGELOG entry summarizes all nine fixes.
1 task
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.
Summary
Releases the three adopter-triage batches merged this week (PRs #403, #404, #405 — nine issues remediated).
straymark followups merge-driver(followups: the registry is a guaranteed conflict between parallel PRs, and the correct resolution silently reverts closures #391),FOLLOWUP-UNTRACKED-IDvalidate warning (followups/validate: a follow-up declared outside## Follow-upsis invisible to the extractor and nothing warns #392), Qoder skills (init / install-skills: Qoder CLI is not a supported skill target —.qoder/skills/is never materialized #399),update-frameworkchecksum fix (update-framework overwrote a user-modified config.yml without prompting on 4.38.0 → 4.38.1 (silently reverted language: es → en) #388) and the five lote-1 fixes (charter drift uses two-dot range (A..HEAD), reporting the base branch's own changes as the branch's drift #397/charter batch-complete is unusable in non-English projects: exact-match on "## Batch Ledger" vs translated headings #389/charter amend: the scaffolded AILOG fails the CLI's own validate — 4 required fields missing thatnew -t ailogemits #390/charter audit --merge-reports --round N emite un camporoundque el esquema de telemetría rechaza #401/--merge-reports acepta informes con frontmatter incompleto y omite el campo en silencio #402). The lote-3 docs already citecli-3.41.0for these features; this makes the tag real.dist/— telemetry schema + charter templates (lote 1),.qoder/skills/+ manifest (lote 2), FOLLOW-UPS-BACKLOG-PATTERN.md (lote 3).Files:
cli/Cargo.toml,Cargo.lock,dist/dist-manifest.yml, CHANGELOG entry, and the version tables in README + CLI-REFERENCE (en/es/zh-CN). Follows the pattern of #385.Test plan
cargo buildgreen; binary reportsstraymark 3.41.0fw-4.39.0/cli-3.40.0refs left in docs/