release(deepagents): 0.7.1 - #5170
Merged
Mason Daugherty (mdrxy) merged 3 commits intoJul 30, 2026
Merged
Mason Daugherty (mdrxy) merged 3 commits into
Mason Daugherty (mdrxy) merged 3 commits into
Conversation
github-actions
Bot
added
auto:release-pending
github-actions
Bot
force-pushed
the
release-please--branches--main--components--deepagents
branch
25 times, most recently
from
July 30, 2026 19:35
bea3dc2 to
7c1bfaf
Compare
github-actions
Bot
force-pushed
the
release-please--branches--main--components--deepagents
branch
from
July 30, 2026 19:40
7c1bfaf to
e89bc78
Compare
Mason Daugherty (mdrxy)
marked this pull request as ready for review
July 30, 2026 20:14
Mason Daugherty (mdrxy)
temporarily deployed
to
release-bot
July 30, 2026 20:14 — with 
GitHub Actions
Inactive
GitHub Actions
Inactive
Contributor
|
Review and edit the release notes between the content markers below as needed. Keep the version heading intact. 0.7.1 (2026-07-30)Features
Bug Fixes
When the release changes are finalized, run: Merge only after the curated release-notes check passes. If new relevant entries appear after applying, draft again and then re-apply: To ship without curated notes, add the |
![open-swe[bot]](https://avatars.githubusercontent.com/in/1395372?s=60&v=4){kind=small}
Member
|
release-bot apply |
Contributor
|
Curated release notes were applied to the package changelog and release PR body. Do not add more |
Mason Daugherty (mdrxy)
deleted the
release-please--branches--main--components--deepagents
branch
July 30, 2026 20:31
Contributor
Author
|
The package release workflow has started: Follow the linked run for build, test, and publish status. |
github-actions
Bot
added
auto:release-tagged
Mason Daugherty (mdrxy)
added a commit
that referenced
this pull request
Jul 30, 2026
…5206) Release PRs opened or updated by release-please get their `uv.lock` files regenerated again. The `update-lockfiles` job was silently skipping on every push to `main` — the workflow showed green while release PR lockfiles went stale and the "🔒 Check Lockfiles" workflow failed on them — because #5161 put the legitimately-skipped `trigger-releases` job in its upstream `needs` chain and the job's bare `if:` kept GitHub Actions' implicit `success()` gate. #5169 fixed this for the `release-please` job; this applies the same gating to `update-lockfiles` (and audits the remaining downstream jobs). --- ## Why `update-lockfiles` needs `release-please`, which (after #5161) transitively needs `trigger-releases` via `guard-pending-release`. On ordinary pushes to `main`, `trigger-releases` is skipped — and without a status-check function in the job's `if:`, Actions' implicit `success()` gate on the whole `needs` chain fails closed. The job was skipped with an all-green workflow; observed on release PR #5170, where lockfiles had to be regenerated by hand. ## Fix - `update-lockfiles`: `!cancelled()` plus explicit `result == 'success'` checks on every dependency in the chain (`guard-empty-commit`, `detect-release-commit`, `guard-pending-release`, `release-please`), keeping the existing `prs != '[]' && prs != ''` requirement. Fail-closed semantics preserved: a crashed guard or unset `prs` still blocks the job. `trigger-releases` is deliberately not re-checked — on release commits, `release-please` succeeding already implies the guard saw the dispatch succeed. - `dispatch-release-notes-check`: audit found its `always()` gate already survived the skipped-`trigger-releases` case, but would also run after a cancelled workflow or red guardians. Added `!cancelled()` and the same hand-checked ancestor results; `update-lockfiles` stays a sequencing-only need whose own failure does not block the dispatch. - `guard-empty-commit`, `detect-release-commit`, and `trigger-releases` need no changes — their `needs` chains never contain a legitimately-skipped job. Tests pin the new truth tables for both jobs, mirroring the style #5169 used for `release-please`, and `_evaluate` now handles `always()`.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Caution
Merging this PR will automatically publish to PyPI and create a GitHub release.
For the full release process, see
.github/RELEASING.md.Release notes preview: keep this section in sync with the package
CHANGELOG.md. Publish reads the merged CHANGELOG viarelease.yml, not this PR description — keep them aligned anyway so the PR stays an accurate historical record for reviewers and anyone returning later.0.7.1 (2026-07-30)
Features
lc_versions.deepagents(#5158)Bug Fixes
read_filewindows (#5184)End release notes preview.
Note
A New Contributors section is appended to the GitHub release notes automatically at publish time (see Release Pipeline, step 2).