Skip to content

docs: sync accesses delete description with current spec#538

Merged
Nelson-PROIA merged 1 commit into
mainfrom
chore/unstick-accesses-readme
May 21, 2026
Merged

docs: sync accesses delete description with current spec#538
Nelson-PROIA merged 1 commit into
mainfrom
chore/unstick-accesses-readme

Conversation

@Nelson-PROIA
Copy link
Copy Markdown
Contributor

Summary

Every speakeasy run -t mistralai-sdk produces a 3-way merge conflict on docs/sdks/accesses/README.md:

both modified:   docs/sdks/accesses/README.md
could not apply persistent edits for "python": merge conflicts detected in 1 file(s)

The persistent-edits baseline in .speakeasy/gen.lock is anchored to text that the upstream OpenAPI spec updated months ago (typo fix its owntheir own plus a deprecation warning about the response code changing from 200 to 204).

This blocks the entire mistralai-sdk gen workflow.

Fix

Update the file in-tree to match the current spec text. This re-anchors the persistent edit so the next gen run completes cleanly.

The exact same text change was in the abandoned regen PR #522 (May 12, the incident date).

Validation

Reproduced locally: with this change applied, speakeasy run -t mistralai-sdk completes successfully and re-anchors pristine_commit_hash in gen.lock.

What comes next

After merging, the next workflow_dispatch on sdk_generation_mistralai_sdk.yaml will produce a normal regen PR with the accumulated spec changes since the last successful run. That PR goes through standard review → merge → publish env gate → release flow.

@louis-sanna-dev
Copy link
Copy Markdown
Contributor

louis-sanna-dev commented May 21, 2026

(this would be amazing to get rid of the persistent edit)

The persistent-edits baseline in .speakeasy/gen.lock anchors this paragraph
to text that the upstream OpenAPI spec has since updated (typo fix and
deprecation warning). Every speakeasy run produces a 3-way merge conflict
on this single line, blocking the entire mistralai-sdk gen workflow.

Updating the file in-tree re-anchors the persistent edit so the next gen
run can proceed cleanly and produce a normal regen PR with the accumulated
spec changes.
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.

2 participants