Repository navigation
fix(release): report publish PipelineError partial output in --json - #760
Merged
Merged
Conversation
Co-authored-by: Cursor <cursoragent@cursor.com>
Contributor
|
Standing release PR: #730 · v0.42.1 queued (4 packages) · open 6h 32m · ✅ ready to merge Release Preview — v0.42.0 → v0.42.1
These changes will be added to the release PR (#730) when merged: Changelogmonorepo 0.42.0 → 0.42.1
After merge — predicted release
Updated automatically by ReleaseKit |
Owner
Author
|
@greptile review |
The issue asked for both `release` and `standing-pr publish` to report a failed publish's partial output; only `release` had a test. The helper's doc comment said it matched `publish --json`, which now calls it, so it says why the message names the stage instead. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…tput Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This was referenced Oct 24, 2026
Merged
goosewobbler
pushed a commit
that referenced
this pull request
Oct 24, 2026
Resolves the export conflict in packages/publish/src/index.ts by keeping both pipelineErrorEnvelope (from #760) and VersionPackageChangelogSchema.
This was referenced Oct 24, 2026
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
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.
Description
release --jsonandstanding-pr publish --jsondropped a failed publish's partial output. Their error envelope haddata: null,changed: false, and a message that didn't name the failed stage.publish --jsonalready reported all three, so the commands disagreed on the same failure, and a retry or an agent reading thereleaseenvelope couldn't see what had already been published.pipelineErrorEnvelopein@releasekit/publishbuilds the envelope for aPipelineError.publishuses it, and so doesemitErrorin@releasekit/release, which therelease,standing-prandgatecommands share. The envelope can't drift between commands.docs/cli.mdsaysreleaseandstanding-pr publishreport a failed publish stage the same way, and thatdatathen holds the publish output rather than their usual payload.Related Issue(s)
Closes #700.
Type of Change
feat— New featurefix— Bug fixdocs— Documentation changerefactor— Code refactoringtest— Adding or updating testschore— Maintenance, dependencies, toolingScope
@releasekit/version@releasekit/notes@releasekit/publish@releasekit/release@releasekit/config@releasekit/coreChecklist
pnpm lint)pnpm test)pnpm typecheck)dataandchangedonly gain values on this failureTesting Notes
release --jsonandstanding-pr publish --json: aPipelineErrorfrom the publish stage yieldsdataset to the partial output,changed: true, and a message naming the stage. Both fail againstmain'semitResult.ts.release.tsandstanding-pr.tsrethrow the originalPipelineErrorafter posting the failure report, so the real commands reach the same envelope as the tests.@releasekit/publish(334) and@releasekit/release(857) typecheck and tests pass, andpnpm lintpasses.Made with Cursor


Confidence Score: 5/5
The PR appears safe to merge.Summary
Shares publish failure reporting through
pipelineErrorEnvelope.Reviews (1) · Last reviewed commit: "fix(release): report publish PipelineErr..." · Reviewed by Greptile