Skip to content

Release genkit_llamadart 3.7.0 - #1799

Merged
leehack merged 1 commit into
mainfrom
release/genkit_llamadart-v3.7.0
Nov 8, 2026
Merged

leehack merged 1 commit into
mainfrom
release/genkit_llamadart-v3.7.0

Conversation

@leehack

@leehack leehack commented Nov 8, 2026 •

Copy link
Copy Markdown
Owner

Summary

  • Prepare genkit_llamadart 3.7.0: version 3.6.0 → 3.7.0, and ## Unreleased → ## 3.7.0 - 2026-11-08. The one bullet comes from #1780 (llamadart: ^0.18.0).
  • Why 3.7.0: adapter minors track core minors (3.5/0.16, 3.6/0.17), and ^0.18.0 is a new core minor. Public API unchanged.
  • Two files only, as release_genkit_on_prep_merge.yml requires. Core llamadart 0.18.0 and the 0.18 Apple companions are on pub.dev, so "core first" holds. Release approved by the maintainer on #1747 ("Go").

What merging this PR does

Merging publishes. The branch matches release/genkit_llamadart-vX.Y.Z and changes only the two prep files, so release_genkit_on_prep_merge.yml tags the merge commit genkit_llamadart-v3.7.0 and dispatches publish_genkit_pubdev.yml, which publishes genkit_llamadart 3.7.0 and creates its GitHub Release with --latest=false. Core and companion publishers do not run. pub.dev versions cannot be unpublished. If the merge lands on a later day, fix the changelog date first.

Production-readiness scope

  • User-facing scope: after merge, genkit_llamadart 3.7.0 (llamadart: ^0.18.0) is on pub.dev.
  • Supported platforms/paths: unchanged from main.
  • Unsupported or intentionally unavailable paths: unchanged from main.
  • Out of scope / follow-ups: after publication, update the published-pairing snippets in website/docs/integrations/genkit.md and choosing-an-api.md to 3.7.0 / llamadart 0.18.0, as #1589 did after 3.6.0. The Genkit ## Unreleased heading returns with the next adapter change, as Move genkit_llamadart to llamadart 0.18 #1780 did after 3.6.0.

Completeness checklist

  • Declared scope is fully implemented, or explicitly reduced above.
  • Unsupported platform/option combinations fail loudly with actionable diagnostics or are clearly documented as unavailable. N/A: version and changelog only.
  • Public API docs, README/website docs, examples, support matrices, and changelog entries are updated where relevant. Website pairings follow publication, as noted above.
  • Regression coverage covers the original issue plus key negative/version-skew paths where relevant. N/A: no code change.
  • Public capability changes update the validation coverage registry with a pack or a reasoned, issue-linked exemption; inventory checks pass (or N/A with scope). N/A: no capability change.
  • Security/privacy review completed: version and changelog text only.
  • Follow-up work that is useful but not required for this PR is tracked in GitHub Issues, or explicitly marked "None" above.

PR type guidance

  • Feature PR: N/A, release prep.
  • Bugfix PR: N/A, release prep.
  • Docs-only PR: N/A. A version changes and the merge publishes.

Test Plan

Pinned Flutter 3.47.1 (Dart 3.13.1), macOS arm64, head 94344434e1397324286fc818b149cfe08c7d60a1.

  • dart run tool/prepare_workspace.dart: no tracked changes.
  • dart format --output=none --set-exit-if-changed .: 0 changed.
  • dart analyze: no issues.
  • dart test -p vm -j 1 --exclude-tags local-only: N/A, no core change. dart test -p vm test/unit/tooling/: +1576 ~5, including genkit_release_routing_test.dart and genkit_package_staging_test.dart; the only 6 failures are windows_registry_qualification_test.dart, which needs pwsh (not installed on this host).
  • dart test -p chrome --exclude-tags local-only: N/A, no core change.
  • coverage-lib: N/A, no lib/ change.
  • Other targeted/local-only validation:
    • From packages/genkit_llamadart, hosted llamadart 0.18.0: dart format, dart analyze --fatal-infos, python3 .github/check_docs.py, .github unittests: pass. dart test -x real-model: +471.
    • Lower-bound pins ([email protected] [email protected] [email protected] [email protected] [email protected]), in-tree then restored: analyze clean, +471. Local SDK is 3.13.1; CI's lower-bound leg runs exact Dart 3.12.0.
    • stage_genkit_package.py to a fresh directory, dart pub get && dart pub publish --dry-run: 3.7.0, 0 warnings, 584 KB.
    • python3 -B -m unittest discover -s test/ci -p 'test_*.py': OK.
    • verify_release_docs_versions.dart: pass. --release-prep reports only core 0.19 conditions (root ## Unreleased, pending companion native pins), not this Genkit-only release.

Matrix Evidence

Matrix row Scope covered Platform / model / backend Result Evidence / notes
genkit-release release isolation, two-file prep scope, tag/version guards, staging macOS arm64 PASS routing and staging tests pass; dry-run 0 warnings
genkit-contracts adapter tests, docs, archive, lower bounds macOS arm64, hosted llamadart 0.18.0 PASS +471 published and minimum pins
release-companion-pub-gate pub.dev version availability pub.dev API PASS (pre-merge) genkit_llamadart 3.7.0 returns 404; latest is 3.6.0; tag genkit_llamadart-v3.7.0 absent
release-doc-version-consistency install snippets full tags PASS --release-prep core-only findings explained above

Review Notes

  • Independent review status: ACCEPT at exact head 94344434e1397324286fc818b149cfe08c7d60a1 vs base a468360f5c826b01d7d7bea4de442b03df997145 by a fresh Claude Opus auditor session uninvolved in the implementation (operator-owned); 0 blocking findings. Reproduced the staged archive dry-run (file list identical to 3.6.0), lower bounds on Dart 3.12.0 (+471), hosted core (+471) and Genkit tooling tests; confirmed core/companion/docs-cut publishers cannot match genkit_llamadart-v3.7.0. Non-blocking: keep the 2026-11-08 date (merge today); website pins follow publication; the real-model leg runs in the publisher's verify job.
  • CI status / head SHA: green at 94344434e1397324286fc818b149cfe08c7d60a1 (CI: Genkit lower bounds and published, Genkit local core, Markdown Tests, Linux & Web pass; 9 success, 21 skipped, 0 failed).

High-risk regression review

git diff --name-only --no-renames origin/main...HEAD | dart run tool/testing/classify_high_risk_changes.dart:

Classification: high-risk
Surfaces: artifactConsumer
Required matrix: dart run tool/testing/test_matrix.dart --tier high-risk
  • Classification: high-risk (artifactConsumer)
  • Implementation task: this PR's author session
  • Independent blocking QA task: fresh Claude Opus auditor session, ACCEPT, 0 known PR-caused P1, 0 unresolved threads
  • Exact head / current base: 94344434e1397324286fc818b149cfe08c7d60a1 / a468360f5c826b01d7d7bea4de442b03df997145
  • Production-branch deletion, bypass, or miswire proof: genkit_release_routing_test.dart passes at head; deleting the "$changelog_version" != "$version" check from release_genkit_on_prep_merge.yml fails only test_version_or_changelog_mismatch_fails (mutation control observed, workflow restored).
  • Readiness CLI: dart run tool/testing/high_risk_readiness.dart --evidence evidence_1799-audited.json --pr-number 1799 --head-sha 94344434e1397324286fc818b149cfe08c7d60a1 --base-sha a468360f5c826b01d7d7bea4de442b03df997145 --pr-author leehack exited 2 (unverifiedPrerequisites / externalPrerequisitesUnavailable): repository-local evidence internally consistent; external app/environment/ruleset provenance is unavailable locally, as expected.
  • Affected-family real-model/artifact evidence: N/A, no runtime change; staged archive dry-run above.
  • Explicit unavailable-family or other N/A evidence: N/A.
  • Known PR-caused P1 regressions: 0
  • Unresolved review threads: 0

@leehack
leehack marked this pull request as ready for review November 8, 2026 12:42
@leehack
leehack merged commit 3d4b742 into main Nov 8, 2026
30 checks passed
@leehack
leehack deleted the release/genkit_llamadart-v3.7.0 branch November 8, 2026 12:42
@github-actions

github-actions Bot commented Nov 8, 2026

Copy link
Copy Markdown
Contributor

Chat app preview removed for leehack/llamadart-chat-pr-1799.

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