feat(ci): label release-please PRs with package scope#2539
Merged
Conversation
Mason Daugherty (mdrxy)
requested a review
from Eugene Yurtsev (eyurtsev)
as a code owner
April 7, 2026 20:20
github-actions
Bot
added
feature
james8814
pushed a commit
to james8814/deepagents
that referenced
this pull request
May 1, 2026
) Release PRs created by release-please were never getting package labels (e.g., `repl`, `quickjs`, `deepagents`) because release-please uses `GITHUB_TOKEN`, and GitHub doesn't fire `pull_request_target` events for PRs created by that token. This also affected all other packages whose release-please component names (like `langchain-repl`, `deepagents-acp`) had no `scopeToLabel` mapping. - Add `labelPR()` to `pr-labeler.js` — a reusable function that applies title-based, file-based, and size labels to a given PR number, composing the existing `matchTitleLabels`, `matchFileLabels`, and `computeSize` helpers - Call `labelPR()` from a new step in `release-please.yml` after checkout, with `continue-on-error: true` so labeling failures never block release detection or downstream publish jobs - Add missing `scopeToLabel` entries for all release-please component names: `deepagents-acp`, `langchain-daytona`, `langchain-modal`, `langchain-quickjs`, `langchain-repl`, `langchain-runloop` - Add missing `fileRules` for `libs/partners/quickjs/` and `libs/repl/` so file-based labeling works for those packages
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.
Release PRs created by release-please were never getting package labels (e.g.,
repl,quickjs,deepagents) because release-please usesGITHUB_TOKEN, and GitHub doesn't firepull_request_targetevents for PRs created by that token. This also affected all other packages whose release-please component names (likelangchain-repl,deepagents-acp) had noscopeToLabelmapping.Changes
labelPR()topr-labeler.js— a reusable function that applies title-based, file-based, and size labels to a given PR number, composing the existingmatchTitleLabels,matchFileLabels, andcomputeSizehelperslabelPR()from a new step inrelease-please.ymlafter checkout, withcontinue-on-error: trueso labeling failures never block release detection or downstream publish jobsscopeToLabelentries for all release-please component names:deepagents-acp,langchain-daytona,langchain-modal,langchain-quickjs,langchain-repl,langchain-runloopfileRulesforlibs/partners/quickjs/andlibs/repl/so file-based labeling works for those packages