#5338 docs: Unify image styles with BentoML theme Pull request opened by Sherlock113 ## What does this PR address? Fixes #(issue) ## Before submitting: • Does the Pull Request follow Conventional Commits specification naming? Here are GitHub's guide on how to create a pull request. • Does the code follow BentoML's code style,

pre-commit run -a

script has passed (instructions)? • Did you read through contribution guidelines and follow development guidelines? • Did your changes require updates to the documentation? Have you updated those accordingly? Here are documentation guidelines and tips on writting docs. • Did you write tests to cover your changes? bentoml/BentoML

#5339 fix: don't restore cwd when importing service in worker Pull request opened by frostming Signed-off-by: Frost Ming me@frostming.com ## What does this PR address? Fixes #(issue) ## Before submitting: • Does the Pull Request follow Conventional Commits specification naming? Here are GitHub's guide on how to create a pull request. • Does the code follow BentoML's code style,

pre-commit run -a

script has passed (instructions)? • Did you read through contribution guidelines and follow development guidelines? • Did your changes require updates to the documentation? Have you updated those accordingly? Here are documentation guidelines and tips on writting docs. • Did you write tests to cover your changes? bentoml/BentoML

1 new commit pushed to

<https://github.com/bentoml/BentoML/tree/main|main>

by larme

<https://github.com/bentoml/BentoML/commit/67c4df5eed0f9e55846fb48feb3a38d4f0d18e64|67c4df5e>

- fix: don't restore cwd when importing service in worker (#5339) bentoml/BentoML

1 new commit pushed to

<https://github.com/bentoml/BentoML/tree/main|main>

by Sherlock113

<https://github.com/bentoml/BentoML/commit/a868994d405be97377ecffe07b89c2ced156cf12|a868994d>

- docs: Unify image styles with BentoML theme (#5338) bentoml/BentoML

1 new commit pushed to

<https://github.com/bentoml/BentoML/tree/main|main>

by aarnphm

<https://github.com/bentoml/BentoML/commit/4e8fad57e93b4fa71558f1efa3f2cfbb491fc8a5|4e8fad57>

- feat: custom readiness hook method (#5337) bentoml/BentoML

Release - v1.4.12 New release published by aarnphm ## What's Changed • docs: Use command to list GPU types by @Sherlock113 in #5330 • chore: disable progress bar on cloud build by @aarnphm in #5331 • fix: handling equal sign in value of secret by @larme in #5332 • fix: make sure to inherit from base image ENV by @aarnphm in #5334 • fix: don't add duplicate global options to requirements.txt by @frostming in #5336 • fix: don't restore cwd when importing service in worker by @frostming in #5339 • docs: Unify image styles with BentoML theme by @Sherlock113 in #5338 • feat: custom readiness hook method by @frostming in #5337 Full Changelog: v1.4.10...v1.4.12 bentoml/BentoML

#5340 docs: Fix BentoCloud CLI link Pull request opened by Sherlock113 ## What does this PR address? Fixes #(issue) ## Before submitting: • Does the Pull Request follow Conventional Commits specification naming? Here are GitHub's guide on how to create a pull request. • Does the code follow BentoML's code style,

pre-commit run -a

script has passed (instructions)? • Did you read through contribution guidelines and follow development guidelines? • Did your changes require updates to the documentation? Have you updated those accordingly? Here are documentation guidelines and tips on writting docs. • Did you write tests to cover your changes? bentoml/BentoML

1 new commit pushed to

<https://github.com/bentoml/BentoML/tree/main|main>

by aarnphm

<https://github.com/bentoml/BentoML/commit/fb016f9fdde017f19957852392d6e660f72ba84a|fb016f9f>

- docs: Fix BentoCloud CLI link (#5340) bentoml/BentoML

#5341 chore(deps): bump astral-sh/setup-uv from 5 to 6 Pull request opened by dependabot[bot] Bumps astral-sh/setup-uv from 5 to 6. Release notes Sourced from astral-sh/setup-uv's releases.

## v6.0.0 🌈 activate-environment and working-directory

## Changes

This version contains some breaking changes which have been gathering up for a while. Lets dive into them:

• Activate environment

• Working Directory

• Default `cache-dependency-glob`

• Use default cache dir on self hosted runners

### Activate environment

In previous versions using the input

python-version

automatically activated a venv at the repository root. This led to some unwanted side-effects, was sometimes unexpected and not flexible enough.

The venv activation is now explicitly controlled with the new input

activate-environment

(false by default):

- name: Install the latest version of uv and activate the environment

uses: astral-sh/setup-uv@v6

with:

activate-environment: true

- run: uv pip install pip

The venv gets created by the `uv venv` command so the python version is controlled by the

python-version

input or the files

pyproject.toml

,

uv.toml

,

.python-version

in the

working-directory

.

### Working Directory

The new input

working-directory

controls where we look for

pyproject.toml

,

uv.toml

and

.python-version

files which are used to determine the version of uv and python to install.

It can also be used to control where the venv gets created.

- name: Install uv based on the config files in the working-directory

uses: astral-sh/setup-uv@v6

with:

working-directory: my/subproject/dir

> [!CAUTION]

>

> The inputs

pyproject-file

and

uv-file

have been removed.

### Default

cache-dependency-glob

`@​ssbarnea` found out that the default

cache-dependency-glob

was not suitable for a lot of users.

The old default

... (truncated) Commits • `6b9c606` Bump dependencies (#389) • `ef6bcdf` Fix default cache dependency glob (#388) • `9a31171` chore: update known checksums for 0.6.17 (#384) • `c7f87aa` bump to v6 in README (#382) • `aadfaf0` Change default cache-dependency-glob (#352) • `a0f9da6` No default UV_CACHE_DIR on selfhosted runners (#380) • `ec4c691` new inputs activate-environment and working-directory (#381) • `aa12905` chore: update known checksums for 0.6.16 (#378) • `fcaddda` chore: update known checksums for 0.6.15 (#377) • `fb3a0a9` log info on venv activation (#375) • See full diff in compare view [Dependabot compatibility score](https://camo.githubusercontent.com/eb286fe030f509d6a53f9eefa9dda80f6be75a872e0607aa3739955d67c7c296/68747470733a2f2f646570656e6461626f742d6261646765732e6769746875626170702e636f6d2f6261646765732f636f6d7061746962696c6974795f73636f72653f646570656e64656e63792d6e616d653d61737472616c2d73682f73657475702d7576267061636b6167652d6d616e616765723d6769746875625f616374696f6e732670726576696f75732d76657273696f6e3d35266e65772d76657273696f6e3d36) Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting

@dependabot rebase

. --- Dependabot commands and options You can trigger Dependabot actions by commenting on this PR: •

@dependabot rebase

will rebase this PR •

@dependabot recreate

will recreate this PR, overwriting any edits that have been made to it •

@dependabot merge

will merge this PR after your CI passes on it •

@dependabot squash and merge

will squash and merge this PR after your CI passes on it •

@dependabot cancel merge

will cancel a previously requested merge and block automerging •

@dependabot reopen

will reopen this PR if it is closed •

@dependabot close

will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually •

@dependabot show <dependency name> ignore conditions

will show all of the ignore conditions of the specified dependency •

@dependabot ignore this major version

will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) •

@dependabot ignore this minor version

will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) •

@dependabot ignore this dependency

will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) bentoml/BentoML

new commit pushed to

<https://github.com/bentoml/BentoML/tree/main|main>

by aarnphm

<https://github.com/bentoml/BentoML/commit/a8aaa336a538a4ac10dee9541b51aee1cb3142d0|a8aaa336>

- chore(deps): bump astral-sh/setup-uv from 5 to 6 (#5341) bentoml/BentoML

#5342 ci: pre-commit autoupdate [skip ci] Pull request opened by pre-commit-ci[bot] updates: • github.com/astral-sh/ruff-pre-commit: v0.11.4 → v0.11.8 • github.com/pdm-project/pdm: 2.23.0 → 2.24.1 • github.com/bufbuild/buf: v1.52.0 → v1.53.0 bentoml/BentoML

new commit pushed to

<https://github.com/bentoml/BentoML/tree/main|main>

by aarnphm

<https://github.com/bentoml/BentoML/commit/a567a3a42867206b7defdd5db0541a4fd5b23a14|a567a3a4>

- ci: pre-commit autoupdate [skip ci] (#5342) bentoml/BentoML

#5343 bug: `client_cls is httpx.Client` pattern does not allow customizing `client_cls` Issue created by Kakadus ### Describe the bug We wanted to pass custom limits to the httpx client, so that the number of connections and max keepalive connections are changed. As bentoml does not support this, we subclasses

httpx.AsyncClient

and set the limits there. We apply the limits by overriding client_cls, but this does not work. Bentoml uses

client_cls is httpx.Client

and

client_cls is httpx.AsyncClient

several times, but

MyHttpxClient is not httpx.AsyncClient

although it inherits from it. If bentoml would use

issubclass

, then everything would be fine. Please not that this is not directly a feature request for custom limits directly (that would be also great!), but rather a request for extensibility of the bentoml client. ### To reproduce class MyHttpxClient(httpx.AsyncClient): ... class MyClient(bentoml.AsyncHTTPClient): client_cls = MyHttpxClient async def test_it() -> None: async with MyClient(...) as client: await client.predict(...) This fails with

RuntimeError: Attempted to send an sync request with an AsyncClient instance.

because of BentoML/src/_bentoml_impl/client/http.py Lines 226 to 233 in</bentoml/BentoML/commit/a567a3a42867206b7defdd5db0541a4fd5b23a14|a567a3a> | return self.client.build_request( | | --------------------------------------- | | "POST", | | endpoint.route, | | headers=headers, | | content=to_async_iterable(payload.data) | | if self.client_cls is httpx.AsyncClient | | else payload.data, | | ) | : (recall that

self.client_cls is not httpx.AsyncClient

) ### Expected behavior Bentoml uses the overridden client class and it works. ### Environment bentoml: a567a3a python: 3.12 OS: Arch Linux bentoml/BentoML

#5344 fix: insert install command even if the base image is specified Pull request opened by frostming Signed-off-by: Frost Ming me@frostming.com ## What does this PR address? Fixes #(issue) ## Before submitting: • Does the Pull Request follow Conventional Commits specification naming? Here are GitHub's guide on how to create a pull request. • Does the code follow BentoML's code style,

pre-commit run -a

script has passed (instructions)? • Did you read through contribution guidelines and follow development guidelines? • Did your changes require updates to the documentation? Have you updated those accordingly? Here are documentation guidelines and tips on writting docs. • Did you write tests to cover your changes? bentoml/BentoML

#5345 fix: subclass checking for client classes Pull request opened by frostming Signed-off-by: Frost Ming me@frostming.com ## What does this PR address? Fix #5343 bentoml/BentoML

1 new commit pushed to

<https://github.com/bentoml/BentoML/tree/main|main>

by aarnphm

<https://github.com/bentoml/BentoML/commit/bda7b5426ac3313f1c1848606f5fe30a7fd06197|bda7b542>

- fix: subclass checking for client classes (#5345) bentoml/BentoML

1 new commit pushed to

<https://github.com/bentoml/BentoML/tree/main|main>

by aarnphm

<https://github.com/bentoml/BentoML/commit/98915ce0c778a6a54e020740728fd14a2d39838a|98915ce0>

- fix: insert install command even if the base image is specified (#5344) bentoml/BentoML

#5346 feat: add paths to schemas to support openai chat endpoints Pull request opened by aarnphm Signed-off-by: Aaron Pham contact@aarnphm.xyz bentoml/BentoML

#5347 fix: do not allow separate python requirements calls Pull request opened by frostming Signed-off-by: Frost Ming me@frostming.com ## What does this PR address? Fixes #(issue) ## Before submitting: • Does the Pull Request follow Conventional Commits specification naming? Here are GitHub's guide on how to create a pull request. • Does the code follow BentoML's code style,

pre-commit run -a

script has passed (instructions)? • Did you read through contribution guidelines and follow development guidelines? • Did your changes require updates to the documentation? Have you updated those accordingly? Here are documentation guidelines and tips on writting docs. • Did you write tests to cover your changes? bentoml/BentoML

#5348 docs: correct description of max_latency_ms Pull request opened by jianshen92 ## What does this PR address? Fixes #(issue) ## Before submitting: • Does the Pull Request follow Conventional Commits specification naming? Here are GitHub's guide on how to create a pull request. • Does the code follow BentoML's code style,

pre-commit run -a

script has passed (instructions)? • Did you read through contribution guidelines and follow development guidelines? • Did your changes require updates to the documentation? Have you updated those accordingly? Here are documentation guidelines and tips on writting docs. • Did you write tests to cover your changes? bentoml/BentoML

1 new commit pushed to

<https://github.com/bentoml/BentoML/tree/main|main>

by aarnphm

<https://github.com/bentoml/BentoML/commit/3c53d0fd66cbe56804064be1f9e111ab21820826|3c53d0fd>

- fix: do not allow separate python requirements calls (#5347) bentoml/BentoML

#5349 fix: support pre-built wheels in bento spec v2 Pull request opened by frostming Signed-off-by: Frost Ming me@frostming.com ## What does this PR address? Fixes #(issue) ## Before submitting: • Does the Pull Request follow Conventional Commits specification naming? Here are GitHub's guide on how to create a pull request. • Does the code follow BentoML's code style,

pre-commit run -a

script has passed (instructions)? • Did you read through contribution guidelines and follow development guidelines? • Did your changes require updates to the documentation? Have you updated those accordingly? Here are documentation guidelines and tips on writting docs. • Did you write tests to cover your changes? bentoml/BentoML

1 new commit pushed to

<https://github.com/bentoml/BentoML/tree/main|main>

by aarnphm

<https://github.com/bentoml/BentoML/commit/2ec12f7393e6fc7f16ebca93ba226d56fb632b21|2ec12f73>

- fix: support pre-built wheels in bento spec v2 (#5349) bentoml/BentoML

1 new commit pushed to

<https://github.com/bentoml/BentoML/tree/main|main>

by aarnphm

<https://github.com/bentoml/BentoML/commit/0a6c4c57e749970c499aec03f517cc6c4e5b3be4|0a6c4c57>

- feat: add paths to schemas to support openai chat endpoints (#5346) bentoml/BentoML

#5350 fix: delete preheat_pip_packages Pull request opened by bojiang bentoml/BentoML

1 new commit pushed to

<https://github.com/bentoml/BentoML/tree/main|main>

by aarnphm

<https://github.com/bentoml/BentoML/commit/8f2ea1678387135a971e8e68a206f6b24b41f6e8|8f2ea167>

- fix: delete preheat_pip_packages (#5350) bentoml/BentoML

#5351 docs: Add docs for wheels and run_script() Pull request opened by Sherlock113 ## What does this PR address? Fixes #(issue) ## Before submitting: • Does the Pull Request follow Conventional Commits specification naming? Here are GitHub's guide on how to create a pull request. • Does the code follow BentoML's code style,

pre-commit run -a

script has passed (instructions)? • Did you read through contribution guidelines and follow development guidelines? • Did your changes require updates to the documentation? Have you updated those accordingly? Here are documentation guidelines and tips on writting docs. • Did you write tests to cover your changes? bentoml/BentoML

1 new commit pushed to

<https://github.com/bentoml/BentoML/tree/main|main>

by frostming

<https://github.com/bentoml/BentoML/commit/d25f04ae82dbbeb217708b7f202589d4ba446d9a|d25f04ae>

- docs: Add docs for wheels and run_script() (#5351) bentoml/BentoML

#5352 chore: minor fix, wrong message Pull request opened by frostming Signed-off-by: Frost Ming me@frostming.com ## What does this PR address? Fixes #(issue) ## Before submitting: • Does the Pull Request follow Conventional Commits specification naming? Here are GitHub's guide on how to create a pull request. • Does the code follow BentoML's code style,

pre-commit run -a

script has passed (instructions)? • Did you read through contribution guidelines and follow development guidelines? • Did your changes require updates to the documentation? Have you updated those accordingly? Here are documentation guidelines and tips on writting docs. • Did you write tests to cover your changes? bentoml/BentoML

1 new commit pushed to

<https://github.com/bentoml/BentoML/tree/main|main>

by frostming

<https://github.com/bentoml/BentoML/commit/debd40ffb70274912fa88f73c8483b9c2f63a9bc|debd40ff>

- chore: minor fix, wrong message (#5352) bentoml/BentoML