vstorm-co / pydantic-deepagents / 31028413127
100%

DEFAULT BRANCH: main
Ran
Jobs 1
Files 89
Run time 1min
Badge
Embed ▾
README BADGES
x

If you need to use a raster PNG badge, change the '.svg' to '.png' in the link

Markdown

Textile

RDoc

HTML

Rst
coverage: 100.0%. Remained the same
31028413127

push

github

web-flow 
fix(deps): update dependency pydantic-ai-backend to >=0.2.25 (#192)

This PR contains the following updates:

| Package | Change |
[Age](https://docs.renovatebot.com/merge-confidence/) |
[Confidence](https://docs.renovatebot.com/merge-confidence/) |
|---|---|---|---|
|
[pydantic-ai-backend](https://redirect.github.com/vstorm-co/pydantic-ai-backend)
| `>=0.2.18` → `>=0.2.25` |
![age](https://developer.mend.io/api/mc/badges/age/pypi/pydantic-ai-backend/0.2.25?slim=true)
|
![confidence](https://developer.mend.io/api/mc/badges/confidence/pypi/pydantic-ai-backend/0.2.18/0.2.25?slim=true)
|

---

### Release Notes

<details>
<summary>vstorm-co/pydantic-ai-backend (pydantic-ai-backend)</summary>

###
[`v0.2.25`](https://redirect.github.com/vstorm-co/pydantic-ai-backend/blob/HEAD/CHANGELOG.md#0225---2026-08-04)

[Compare
Source](https://redirect.github.com/vstorm-co/pydantic-ai-backend/compare/v0.2.24...v0.2.25)

Four open issues, and the first is the one to read.

##### Fixed

- **A `PermissionRuleset`'s per-path rules are enforced.** Handing one
to
`ConsoleCapability` reached two things — `requires_approval`, for the
write and
  execute approval flags, and `_denied_tools`, which drops a tool whose
*operation* defaults to `"deny"`. Nothing read
`OperationPermissions.rules`. So
the shape a caller writes when they want "allow the workspace, deny
credentials
and the system tree" — every operation `default="allow"`, the patterns
in
`rules` — was no enforcement at all: `/etc/passwd` and `**/.env` read
and wrote
freely, and `grep` returned their contents line by line. Worse than
rejecting
  the ruleset, because it looked like a working boundary.

`PermissionGuard` had been here since `LocalBackend` needed it and only
`LocalBackend` ever used it. `GuardedBackend` puts it on any backend,
applied
where the toolset resolves its backend — the one place every tool passes
through. A caller with no ruleset, or a backend enforcing its own, is
untouched,
so nothing changes ... (continued)

6919 of 6919 relevant lines covered (100.0%)

1.0 hits per line

Jobs
ID Job ID Ran Files Coverage
1 31028413127.1 89
100.0
 GitHub Action Run
Source Files on build 31028413127