The constant "update to latest" pressure in the LLM agent space feels like it's actively undermining secure deployment. On a constrained device, every update is a risk—bigger attack surface, new deps, untested code.

But pinning for security feels like you're fighting your own tools. Look at typical agent project deps:
```python
# so common it hurts
openai>=1.0.0
langchain>=0.1.0
```
That's a pipeline for pulling in a malicious or broken package tomorrow.

* Automated scanners flag old pinned versions as vulnerabilities.
* Repos push `pip install` without `--no-deps` or hash checking.
* Nano agents on edge devices can't afford a 3am breakage from a transitive dep update.

How are you all handling this? Are you:
* Fully vendoring?
* Using `pip-tools` with hashes?
* Just accepting the risk and automating rollbacks? 🤔

The Yocto model (recipe revisions, locked downloads) seems right, but it's heavy for Python agents. Is there a middle ground?