Skip to content

Conversation

@lambdalisue
Copy link
Member

The following updates are detected:

module from to type
@probitas/runner 0.5.4 0.5.5 patch

Please ensure:

  • Versions in deno.json files are updated correctly
  • Releases.md is updated correctly

The following commits are not recognized. Please handle them manually if necessary:


To make edits to this PR:

git fetch upstream release-2026-01-08-12-07-27 && git checkout -b release-2026-01-08-12-07-27 upstream/release-2026-01-08-12-07-27

@codecov
Copy link

codecov bot commented Jan 8, 2026

Codecov Report

✅ All modified and coverable lines are covered by tests.

📢 Thoughts on this report? Let us know!

@lambdalisue lambdalisue marked this pull request as ready for review January 8, 2026 12:10
Copilot AI review requested due to automatic review settings January 8, 2026 12:10
@lambdalisue lambdalisue merged commit 366264f into main Jan 8, 2026
3 checks passed
@lambdalisue lambdalisue deleted the release-2026-01-08-12-07-27 branch January 8, 2026 12:11
Copy link

Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

This is a release PR for version 0.5.5 of the @probitas/runner package, which includes a bug fix to propagate abort reason from external signals.

  • Updates package version from 0.5.4 to 0.5.5
  • Documents the fix in the release notes

Reviewed changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated 1 comment.

File Description
packages/probitas-runner/deno.json Increments version from 0.5.4 to 0.5.5
Releases.md Adds changelog entry for version 0.5.5 with fix description

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

Comment on lines 1 to +7
### 2026.01.08

#### @probitas/runner 0.5.5 (patch)

- fix(@probitas/runner): propagate abort reason from external signal

### 2026.01.08
Copy link

Copilot AI Jan 8, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

There are duplicate date headers for the same date (2026.01.08). Typically, multiple releases on the same date should be grouped under a single date header. Consider consolidating both version entries under one date header, or if these are truly separate releases, ensure they have different dates.

Copilot uses AI. Check for mistakes.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants