starred/human-mcp
1
0
Fork 0
mirror of https://github.com/mrgoonie/human-mcp.git synced 2026-04-26 12:05:49 +03:00
Code Issues Projects Releases 5 Packages Wiki Activity

[PR #14] [MERGED] fix(ci): use default github.token for release job #14

New issue
Closed
opened 2026-03-03 15:56:49 +03:00 by kerem · 0 comments
kerem commented 2026-03-03 15:56:49 +03:00
Owner
Copy link

📋 Pull Request Information

Original PR: https://github.com/mrgoonie/human-mcp/pull/14
Author: @mrgoonie
Created: 2/28/2026
Status: ✅ Merged
Merged: 2/28/2026
Merged by: @mrgoonie

Base: main ← Head: dev

📝 Commits (1)

  • 9afc4e9 fix(ci): use default github.token for release job checkout and semantic-release

📊 Changes

1 file changed (+1 additions, -2 deletions)

View changed files

📝 .github/workflows/publish.yml (+1 -2)

📄 Description

Summary

  • Remove CI_GITHUB_TOKEN from release job entirely — secret exists but is invalid/expired
  • The || fallback didn't work because the secret has a non-empty (but invalid) value
  • Use default github.token which has sufficient permissions via job-level contents: write
  • Fixes release job checkout failure in Publish workflow

Root Cause

secrets.CI_GITHUB_TOKEN is set in repo settings but the token is expired/invalid. GitHub Actions || operator evaluates truthiness — a non-empty string is truthy, so fallback to github.token never triggered.

Test plan

  • Merge and verify Publish workflow passes (both test + release jobs)
  • Verify semantic-release creates releases correctly with default token

🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.

## 📋 Pull Request Information **Original PR:** https://github.com/mrgoonie/human-mcp/pull/14 **Author:** [@mrgoonie](https://github.com/mrgoonie) **Created:** 2/28/2026 **Status:** ✅ Merged **Merged:** 2/28/2026 **Merged by:** [@mrgoonie](https://github.com/mrgoonie) **Base:** `main` ← **Head:** `dev` --- ### 📝 Commits (1) - [`9afc4e9`](https://github.com/mrgoonie/human-mcp/commit/9afc4e91fdfb6c94ebc318749e5d404719b235a8) fix(ci): use default github.token for release job checkout and semantic-release ### 📊 Changes **1 file changed** (+1 additions, -2 deletions) <details> <summary>View changed files</summary> 📝 `.github/workflows/publish.yml` (+1 -2) </details> ### 📄 Description ## Summary - Remove `CI_GITHUB_TOKEN` from release job entirely — secret exists but is invalid/expired - The `||` fallback didn't work because the secret has a non-empty (but invalid) value - Use default `github.token` which has sufficient permissions via job-level `contents: write` - Fixes release job checkout failure in Publish workflow ## Root Cause `secrets.CI_GITHUB_TOKEN` is set in repo settings but the token is expired/invalid. GitHub Actions `||` operator evaluates truthiness — a non-empty string is truthy, so fallback to `github.token` never triggered. ## Test plan - [ ] Merge and verify Publish workflow passes (both test + release jobs) - [ ] Verify semantic-release creates releases correctly with default token --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>
kerem 2026-03-03 15:56:49 +03:00
Sign in to join this conversation.
No Branch/Tag specified
Branches Tags
main
dev
v2.15.1
v2.15.0
v2.14.0
v2.13.0
v2.12.1
v2.12.0
v2.11.0
v2.10.1
v2.10.0
v2.9.0
v2.8.4
v2.8.3
v2.8.2
v2.8.1
v2.8.0
v2.7.0
v2.6.0
v2.5.0
v2.4.1
v2.4.0
v2.3.0
v2.2.0
v2.1.0
v2.0.0
v1.4.0
v1.3.0
v1.2.1
v1.2.0
v1.1.0
v1.0.2
v1.0.1
v1.0.0
Labels
Clear labels   
pull-request

Mirrored from GitHub Pull Request

No labels
pull-request
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/human-mcp#14
No description provided.