Skip to content

Fix release workflow: Clarify MCP tool call vs bash file operations #11991

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
pelikhan merged 2 commits into from
Jan 27, 2026
Merged

Fix release workflow: Clarify MCP tool call vs bash file operations #11991

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
627ee54
Initial plan
Copilot Jan 27, 2026
756d4d4
Fix: Clarify MCP tool call instructions in release workflow
Copilot Jan 27, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
18 changes: 15 additions & 3 deletions .github/workflows/release.lock.yml
View file
Open in desktop

Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.

18 changes: 15 additions & 3 deletions .github/workflows/release.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -470,11 +470,21 @@ Dependency updates and internal improvements to keep things running smoothly.

## Output Format

**CRITICAL**: You MUST call the `update_release` tool to update the release with the generated highlights:
**CRITICAL**: You MUST call the `update_release` MCP tool to update the release with the generated highlights.

**HOW TO CALL THE TOOL:**

The `update_release` tool is an **MCP (Model Context Protocol) tool**, not a bash command or file operation. To call it:

1. **Use the MCP tool call syntax** - The tool is registered as `update_release` (or `safeoutputs___update_release`)
2. **DO NOT write JSON files manually** - Writing files like `/tmp/gh-aw/safeoutputs/update_release_001.json` will NOT work
3. **DO NOT use bash to simulate tool calls** - The tool must be called through the MCP protocol

**Example Tool Call:**

```javascript
update_release({
tag: "${RELEASE_TAG}",
tag: "v0.37.26",
operation: "prepend",
body: "## 🌟 Release Highlights\n\n[Your complete markdown highlights here]"
})
Expand All @@ -485,7 +495,9 @@ update_release({
- `operation` - Must be `"prepend"` to add before existing notes
- `body` - Complete markdown content (include all formatting, emojis, links)

**WARNING**: If you don't call the `update_release` tool, the release notes will NOT be updated!
**IMPORTANT**: This is a real tool call through MCP, NOT a bash command or file write operation. The tool will automatically write to the correct output file (`/opt/gh-aw/safeoutputs/outputs.jsonl`).

**WARNING**: If you don't call the `update_release` tool properly through MCP, the release notes will NOT be updated!

**Documentation Base URLs:**
- User docs: `https://githubnext.github.io/gh-aw/`
Expand Down