… main (mistralai#531)

- run_examples: build + install only, no secrets, no env, runs on PR + push
- examples: build + run examples with CI_MISTRAL_API_KEY_PYTHON_*, environment: publish, push-to-main only

Pins runners to ubuntu-24.04 while here.

ci: rename environment to publish

* ci: publish Python SDKs to PyPI with OIDC

* ci: pin PyPI publish runner

Replaces Speakeasy's reusable workflow with a steps-based job invoking
the speakeasy ci generate CLI directly. This lets the generate job
declare environment: publish, gating secrets access behind the required
reviewer approval.

Also bumps speakeasyVersion to 1.763.2, which includes the upstream
fix for the go-git push bug in CommitAndPush
(speakeasy-api/speakeasy#2043).

Three generation workflows updated: mistralai-sdk, mistralai-azure-sdk,
mistralai-gcp-sdk.

* Workflows: Add JSONPatch events partial decryption

* Update to new format

* Improvement

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.

…alai#537)

uv version <new> triggers a hatchling editable build which validates
pyproject.toml. The azure and gcp packages declare readme = "README-PYPI.md"
but the file is generated at publish time by scripts/prepare_readme.py and
not committed. On fresh CI checkouts hatchling raises OSError: Readme file
does not exist: README-PYPI.md before the version is bumped.

Run prepare_readme.py before uv version so the file exists for validation,
mirroring what publish.sh already does at release time.

…ralai#508)

* feat: add Azure DefaultAzureCredential support for blob storage

* fix: narrow account_url type for mypy/pyright

…stralai#543)

The mistralai-{azure,gcp} pyproject.toml files reference README-PYPI.md
which is generated by scripts/prepare_readme.py from the regular README.md
with relative links rewritten to absolute GitHub URLs.

Until now, the file was gitignored per package and only generated at
publish time. This caused align-version to fail in CI because uv version
triggers a hatchling editable build which validates pyproject.toml, and
hatchling refuses to validate a non-existent readme file.

The root mistralai package already commits its README-PYPI.md (added in
mistralai#518) and works fine. Apply the same pattern to azure and gcp:

- Remove README-PYPI.md from each package's .gitignore
- Commit the generated file
- Drop the prepare_readme step from gen workflows (added in mistralai#537)
  since the file is now always present on disk

prepare_readme.py is still called by publish.sh and the publish workflow
to refresh the file at release time, so it stays accurate.

Picks up two upstream Python generator fixes:
- envVarPrefix fallback when SDK is constructed without security args
  (1.763.4 + 1.763.6) — Mistral() now correctly reads MISTRAL_API_KEY
  from the environment when no api_key argument is passed, matching
  the standard pattern used by OpenAI, Anthropic, Cohere, etc.
- Types package support exports preserved correctly
- General multi-SDK fixes for async declarations, doc rendering, exports

Validated locally with speakeasy run -t mistralai-sdk: regen is clean
and the generated src/mistralai/client/sdk.py contains the security
fallback patch. Confirmed Mistral() + MISTRAL_API_KEY env var
correctly resolves the api_key via get_security_from_env.

Aligns the python publish workflow with the env name used by all other
workflows. The public-sdk environment no longer exists on the repo
(removed when renaming to publish), so the publish workflow currently
references a non-existent environment.

The publish workflow builds a single bundled mistralai wheel from root
pyproject.toml that includes the sub-packages as source. Only the root
RELEASES.md changing reflects a new release. Sub-package RELEASES.md
changes (packages/azure, packages/gcp) shouldn't trigger publish runs
since they don't produce a new wheel.

…LAI-GCP-SDK [speakeasy/mistralai-gcp-sdk-26292830187-1] 2.1.0 (mistralai#548)

* ci: regenerated with OpenAPI Doc , Speakeasy CLI 1.763.6

* chore: align pyproject.toml and uv.lock to version 2.1.0

* fix(tests): top_p, stop, presence_penalty, frequency_penalty default to UNSET

The regenerated SDK uses the UNSET sentinel instead of None as the
default value for these parameters in the GCP chat client. Update
the parity tests to match.

* fix(tests): Fim top_p and stop default to UNSET

The regenerated SDK uses UNSET for these parameters on Fim too.

* fix(tests): Fim top_p default test asserts UNSET

The regenerated SDK uses UNSET for Fim.complete/stream top_p, not 1.

---------

Co-authored-by: speakeasybot <bot@speakeasyapi.dev>

…RE-SDK [speakeasy/mistralai-azure-sdk-26292833044-1] 2.1.0 (mistralai#549)

* ci: regenerated with OpenAPI Doc , Speakeasy CLI 1.763.6

* chore: align pyproject.toml and uv.lock to version 2.1.0

* fix(examples,tests): adapt to regenerated SDK changes

- examples/azure/chat_no_streaming.py: guard against None message
  (message can now be AssistantMessage | None in the new generation)
- tests/test_azure_v2_parity.py: top_p, stop, presence_penalty, and
  frequency_penalty now default to UNSET instead of None

* fix(tests): remove id from OCR_PROCESS_PARAMS

The regenerated SDK no longer exposes the id parameter on Ocr.process
(removed from the spec). Drop the obsolete test entry.

---------

Co-authored-by: speakeasybot <bot@speakeasyapi.dev>

…tralai-sdk-26292816554-1] 2.4.7 (mistralai#550)

* ci: regenerated with OpenAPI Doc , Speakeasy CLI 1.763.6

* chore: align pyproject.toml and uv.lock to version 2.4.7

* fix: use is_error_status_code callable in workflow helper

The regenerated SDK changed BaseSDK.do_request_async signature from
error_status_codes (List[str]) to is_error_status_code (Callable[[int], bool]).
Update the workflow helper to use the new callable form.

---------

Co-authored-by: speakeasybot <bot@speakeasyapi.dev>