Agent cuts release without explicit user request

Open Beginner friendly
#505 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
64/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Quiet
Tech stack
typescript
Domain
release

Research direction

Start by reading the release-package skill's operating policy and the release.yml workflow, then trace how a diagnosis request can reach the release path. Ensure diagnosis produces findings or proposed fixes without initiating a release unless the user explicitly requests one, and verify the workflow still supports explicitly requested releases.

Written by the indexing model from the issue text.

Description

When asked to diagnose a deployment problem, Junior cut a patch release of the junior package without being asked to. The user had only asked for diagnosis of why Vercel wasn't showing route traffic.

What happened:

  • User reported staging Vercel not showing route traffic
  • Junior diagnosed an upstream juniorNitro() wiring gap in 0.65.0 and immediately dispatched release.yml bump=patch, approved the publish issue, and merged it to npm
  • User had not requested a release; they wanted diagnosis and root-cause analysis

Root cause of the mistake:
The release-package skill's operating policy says "proceed without asking for confirmation" when someone asks to make a release. Junior misapplied this policy to a diagnosis request and treated identifying a potential fix as sufficient authorization to cut a release.

Impact:
An unnecessary 0.65.1 release was published. The release may also have been based on an incorrect diagnosis — the actual cause of missing Vercel route traffic was not yet confirmed.

Expected behavior:
Junior should not initiate releases unless explicitly asked. Diagnosis tasks should produce findings and proposed fixes, not autonomous release actions.

Action taken on behalf of David Cramer.

Dominant language
TypeScript
Stars
358
Forks
38
Avg merge
7h
Merged PRs (30d)
199

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from getsentry/junior

All issues in getsentry/junior

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.