Skip to content

Release SDK updates - #13

Open
llama-org-ci-bot[bot] wants to merge 30 commits into
mainfrom
stainless/release
Open

llama-org-ci-bot[bot] wants to merge 30 commits into
mainfrom
stainless/release

Conversation

@llama-org-ci-bot

@llama-org-ci-bot llama-org-ci-bot Bot commented Sep 9, 2026

Copy link
Copy Markdown
Contributor

Promotes stainless/release onto main30 commits. Merging this lets release-please cut the next release and write CHANGELOG.md.

Features

  • feat(parse): agentic 2026-09-09 — cache-stable prompt order + Flash Lite MINIMAL thinking (#26273) (f820ba4)
  • feat(parse): add detected_form_types to the per-page enriched forms output (#26052) (81df468)
  • feat(parse): display enriched Forms granular highlights (#26366) (5c07972)
  • feat(parse): ship the illegible-classification prompts as agentic_plus 2026-09-11 (latest) (#26490) (5e7dd7a)
  • feat(split): accept a parse config or parse_job_id like extract_v2 (#26303) (fc152c9)
  • feat(split): target_pages page selection when splitting a parse job (#26921) (72cb9fe)
  • feat(chat): let a chat session refuse queries from its share link (#27012) (dec92c1)
  • feat(sdk): publish beta.attachments list and get (184eb3c)

Bug Fixes

  • fix(ci): give resolver builds a real commit subject (LI-9592) (974210c)
  • fix(chat): report every index a chat turn could not query (#26981) (cfe7db5)

⚠️ Not conventional-commit — release-please will DROP these from CHANGELOG.md

  • LI-9563: add a paginated GET /api/v1/beta/data-sinks (#26430) (39105dd)
  • Map GET /api/v1/beta/data-sinks in SDK config (462c9aa)
  • LI-9561: add a paginated GET /api/v2/webhook-configs (#26517) (3bee1f5)
  • Release Agentic 2026-09-13 with RCL for primary Flash Lite (#26387) (55c4a90)
  • LI-9567: add a paginated GET /api/v1/beta/retrievers (#26553) (ab1530f)
  • Keep job data points out of the published API surface (#26716) (c619862)
  • LI-9748: check the custom-code anchor invariant instead of discovering it five days later (f914e54)
  • LI-9759: restore generated surface a corrupted seal removed (Release SDK updates #6) (d737521)
  • LI-9759: drop retired generated files the custom-code patch was re-applying (db1fa79)
  • LI-9773: drop job_data_points from the prod SDK config (4bc5ec9)
  • LI-9676: map the classify v2 delete endpoint in the SDK config (7616a67)
  • split: add version registration, and a Jev classification preview (#27082) (f9f3833)
Chores & CI (1)
  • chore(sync): resolve back-sync conflicts with production (888c794)
Codegen & merge commits (7)

Regenerated by stlc-promote.yml on every promote, from main...stainless/release.

stlc-bot added 15 commits September 9, 2026 00:27
Stainless-Generated-From: bff2b056790b4e3449b8b43eabd2c0e3965b642f
Stainless-Generated-From: a058ddcac0c266e3c82c4528e40f1bfd2b56ffcb
…ite MINIMAL thinking (#26273)

Stainless-Generated-From: ceef34e61b1d58ca7308066599a382f6c44f2f6a
…utput (#26052)

Stainless-Generated-From: aba848973eb80ceec66fb828f6b29a9758eb06b9
Stainless-Generated-From: 0891d057ffc1f08075ea8e878730ed410201452f
Stainless-Generated-From: 9bdde4352f68c53467c3c23de0d383083dcd6816
Stainless-Generated-From: 2009ba3017d6ac15987d5c91942f77b6d984bef3
Stainless-Generated-From: a68168a9c87d9252654680256c8c0cfd14b12262
…s 2026-09-11 (latest) (#26490)

Stainless-Generated-From: f0fa2fe4fba99934407f70fd733324798b1874d7
Stainless-Generated-From: 5a0a19c0a6cc383736c21c9e84c3ef2f9bf1c57c
Stainless-Generated-From: d3ff58f9fa62fd684f99ccd5fb81d4f5be140121
Stainless-Generated-From: c7fd5bfb3c776f7ff226ac708c7de163d22feadb
Stainless-Generated-From: b8503ea79775a4692ac339047eb4ea235c3bbfe6
…26303)

Stainless-Generated-From: 64579140bfb2ac848ccd8eeb00ea1079c8c675a7
…g it five days later

Stainless-Generated-From: 99e7bb0245666e697a17502593671979d12e47b1
@yongpark

Copy link
Copy Markdown
Contributor

Do not merge — LI-9759.

The pre-promotion mirror this branch was built from is carrying a corrupted custom-code seal that deletes generated model fields. Merging this PR would ship that regression to the published SDK.

Measured on llamacloud-prod-python, custom-code patch base → integrated, deletions of field declarations inside the models directory:

seal count
clean, 2026-09-08 0
first poisoned, 2026-09-09 90
current 90

Affected surface includes custom_instructions, min_pages_per_split, pipeline_id, tier, parse_tier, total_pages, confidence, page_token, page_size, annotate_line_numbers.

The generator still emits all of these — every base tree has them, only integrated does not — and the spec never changed. It re-seals on every build, so it is current, not historical.

The public repos are clean; the last release (2026-09-08) predates the poison. That containment holds only while these promote PRs stay unmerged.

Unblock order: land the seal-corruption control → repair the affected mirrors → clean regenerate → then promote. Tracked in LI-9759, under LI-9748.

stlc-bot and others added 14 commits September 17, 2026 00:31
Stainless-Generated-From: ef75194c0c0d37a5115f7ec1fb7de8871b7935e1
main is a hard build break (232 errors) because the custom-code seal deletes 185 generated
declarations on every build, including MinPagesPerSplit and CustomInstructions across seven
Split model classes and ProjectID from 34 v1 *Params records.

Legitimate csharp custom code is 7 files and touches no source file, so the correct tree is
the generated base plus those 7. Rebuilt on that basis.

Compile-verified: solution (lib + tests, 4 TFMs, TreatWarningsAsErrors) builds with 0 errors
and 0 warnings; main builds with 232 errors; keeping the 50 stale files builds with 8
(CS0101 duplicate 'Mode' — the generator moved that enum between files, so removing them is
required, not optional).

Evidence of corruption rather than intent: the poisoned integrated blob for
DataSinkGetParams.cs is byte-identical to the 2026-08-20 generated base blob.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_014aUNkktYrKPomnF4JnPfsL
Stainless-Generated-From: 99e7bb0245666e697a17502593671979d12e47b1
…plying

An anchor-repair merge resurrected 50 files the generator had already
retired. They were absorbed into the next seal as custom code, so every
build re-applied a patch that reverted generated files — removing
SplittingStrategy.MinPagesPerSplit, CustomInstructions and the ParseTier
enum while the tests still referenced them. CI has been red since.

Reset src/ to the sealed generated base and keep only the genuine custom
files outside it. The published llama-parse-csharp ships none of the
removed resources, so this changes no released surface.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_014aUNkktYrKPomnF4JnPfsL
LI-9759: drop retired generated files the custom-code patch was re-applying
Stainless-Generated-From: debc1d859091bc015119a8d51cc15f373d712e05
…#26921)

Stainless-Generated-From: 5908f3d247cd22b5e910c00d8f0985b9a8af56b4
Stainless-Generated-From: 42c9f70ed7f4796bd62a0f64bada18db3758eee2
Stainless-Generated-From: 3e055e4b45b0721e601175720fb8dec2fb9f7c6e
Stainless-Generated-From: 9140cfa2132af4c9e1168b330004903c06e59347
…7012)

Stainless-Generated-From: 64b4560175483302da9a14c3627477235ed57377
…7082)

Stainless-Generated-From: aa00a01db0f86f26d228f2a4bd49fdcc276a69ef
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_014aUNkktYrKPomnF4JnPfsL
Sync release changes from production
Stainless-Generated-From: 337a9ea63ed67cd57fbf9be152e4433cdc085664
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