Skip to content

gardener: Upgrade Gardener to v0.1.13 - #211

Merged
scuffi merged 1 commit into
mainfrom
gardener-0.1.13
Oct 8, 2026
Merged

scuffi merged 1 commit into
mainfrom
gardener-0.1.13

Conversation

@scuffi

@scuffi scuffi commented Oct 8, 2026 •

Copy link
Copy Markdown
Member

Gardener now reacts to the issue or comment that started a run, so it's visible when a task is working on something.

Reactions

  • While it works: 👀 on the issue (triage) or comment (mention-reply) that started the run.
  • When it finishes: 👀 is replaced with 🚀 if the task applied its plan, or 😕 if planning or applying failed. A run that proposes nothing just removes 👀.
  • Who gets one: only authors the task admits. Both tasks here admit maintainers, checked against GitHub's author association, so a private org member may get no reaction even though the task still runs for them. Outsiders never get one.
  • Where: issues, pull requests and their comments, review comments and discussions. Review submissions get none (GitHub has no reactions API for them), so pr-review-fix is unchanged, as is the scheduled dependabot-merge.
  • How: two short jobs, "React" and "React with result", run alongside the task. They check nothing out and only make fixed API calls; a failed reaction never fails the run. A task can turn them off with reactions: false in its TASK.md.

What changes in this repository

  • Workflows: gardener-triage.yml and gardener-mention-reply.yml pass the new reactions input. Their permissions are unchanged: both already grant the writes the reactions need.
  • Version pins: the workflows move to 0.1.13's pinned release, and gardener:generate points at @scuffi/gardener@0.1.13.
  • Unchanged: every task keeps the same bundle hash.
  • Deployment: the runtime is already on 0.1.13. Regenerating with the published package changes nothing.

Tested on a demo repository first

  • Pull request: 👀 appeared a few seconds after it opened, and became 🚀 once the review task posted its review.
  • Mention: 👀 on the comment, then 🚀 after the reply was posted.

Devin Review

@changeset-bot

changeset-bot Bot commented Oct 8, 2026

Copy link
Copy Markdown

⚠️ No Changeset found

Latest commit: 09c87fd

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

@devin-ai-integration devin-ai-integration Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

✅ Devin Review: No Issues Found

Devin Review analyzed this PR and found no bugs or issues to report.

Devin Review

@pkg-pr-new

pkg-pr-new Bot commented Oct 8, 2026

Copy link
Copy Markdown

Open in StackBlitz

npm i https://pkg.pr.new/@cloudflare/computer@211

commit: 09c87fd

@scuffi
scuffi merged commit 1f0b5be into main Oct 8, 2026
28 checks passed
@scuffi
scuffi deleted the gardener-0.1.13 branch October 8, 2026 12:16
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.

1 participant