release(deepagents-talon): 0.0.4 - #5605
Merged
Mason Daugherty (mdrxy) merged 3 commits intoAug 24, 2026
Merged
Conversation
github-actions
Bot
added
autorelease: pending
github-actions
Bot
force-pushed
the
release-please--branches--main--components--deepagents-talon
branch
3 times, most recently
from
August 18, 2026 19:36
1b86b09 to
43da465
Compare
github-actions
Bot
force-pushed
the
release-please--branches--main--components--deepagents-talon
branch
7 times, most recently
from
August 19, 2026 03:24
38c30c2 to
9c93107
Compare
Mason Daugherty (mdrxy)
added a commit
that referenced
this pull request
Aug 19, 2026
Release PRs now fail before merge when their built wheel needs dependency metadata that has not reached PyPI, or when the wheel cannot be installed from the public index the way `release.yml` installs it. --- Source CI installs sibling packages from local editable paths, which can hide a required release order: a sibling package's source may declare a new Python floor or dependency floor that PyPI's latest published wheel does not yet have. Merging in that state would break the post-merge release install. The `📦 Check Dependency Freshness` workflow now, for release PRs only: 1. Builds the release wheel and checks every `Requires-Dist` constraint against PyPI. For repo-managed dependencies it also verifies the newest eligible PyPI files satisfy the sibling's current Python metadata. Direct URL dependencies fail, since this path verifies PyPI. 2. Installs the wheel into a clean environment on the package's release Python with `--index-url https://pypi.org/simple`, with Talon getting the same `--prerelease allow` exception as the release workflow. Non-release PRs get a passing no-op, so the job is safe to require globally. ## Demonstration The check passes on this normal (non-release) PR: [workflow run 32184070069](https://github.com/langchain-ai/deepagents/actions/runs/32184070069). A live GitHub-hosted failure run is not feasible before merge: pull-request workflows execute from the head branch, so the failing Talon 0.0.4 release PR (#5605) does not contain this code, and a new `workflow_dispatch` trigger is not recognized until it exists on the default branch. Locally, the same check against the built Talon wheel and live PyPI JSON fails with: > `deepagents-code 0.1.57 (latest on PyPI) declares requires-python<4.0,>=3.11, but the current deepagents-code metadata requires >=3.12,<4.0. Constraint: <1.0.0,>=0.1.30. Release deepagents-code first, then re-run this check.` The clean Python 3.12 install step was exercised separately and resolved 138 packages from PyPI, including `deepagents-code==0.1.57` — expected, since the install step proves the public graph resolves while the metadata check catches the unpublished sibling change. ## Required status After this lands, a maintainer must add the literal `validate release dependencies against PyPI` job name to the `main` ruleset's required status checks (currently only `✅ CI Success` is required). The job passes on non-release PRs, so requiring it will not block unrelated PRs.
github-actions
Bot
force-pushed
the
release-please--branches--main--components--deepagents-talon
branch
13 times, most recently
from
August 19, 2026 20:27
02b2714 to
177d754
Compare
github-actions
Bot
force-pushed
the
release-please--branches--main--components--deepagents-talon
branch
21 times, most recently
from
August 21, 2026 15:44
38eb7dc to
5398886
Compare
Contributor
|
Review and edit the release notes between the content markers below as needed. Keep the version heading intact. To regenerate with steering instead of editing by hand, run 0.0.4 (2026-08-24)Features
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 |
Contributor
Author
|
The package release workflow has started: Follow the linked run for build, test, and publish status. |
Contributor
Author
|
All dispatched package releases published successfully:
|
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.0.4 (2026-08-24)
Features
End release notes preview.
Note
A community contributors list and a Special thanks section (crediting the users who filed the issues this release's PRs closed) are appended to the GitHub release notes automatically at publish time (see Release Pipeline, step 3).