[Bug]: Issue with Semantic Release pipeline

[ryderstorm]

Summary

The repo name needs to be updated in the chainguard workflow

Steps to Reproduce

See details in https://github.com/liatrio-labs/spec-driven-workflow/actions/runs/18607893370/job/53060795946#step:3:6

Expected Behavior

Semantic release job succeeds

Actual Behavior

Semantic release job failed because of a repo name mismatch after we renamed this repo.

Logs / Output

Python Version

No response

Operating System

No response

Related Prompt/Task IDs

No response

Additional Context

No response

Pre-Submission Checks

• I searched existing issues for duplicates
• I included clear reproduction steps

[ryderstorm]

@claude clean up this issue. then open a PR to fix the problem.

[claude]

Claude finished @ryderstorm's task —— View job • claude/issue-13-20251018-0030 • Create PR ➔

---

Tasks

• Read repository guidelines (CLAUDE.md)
• Locate the chainguard workflow file
• Identify the incorrect repo name
• Update the repo name to the correct value
• Commit and push changes
• Provide PR creation link

Summary

Fixed the semantic release pipeline issue by updating the repository name in the Chainguard configuration file.

What I Did

• Found the incorrect repo name spec-driven-workflow-mcp in .github/chainguard/main-semantic-release.sts.yaml:3
• Updated it to the correct name spec-driven-workflow
• Committed and pushed the fix to the branch

Changes Made

File: .github/chainguard/main-semantic-release.sts.yaml

• Line 3: Changed subject_pattern from repo:liatrio-labs/spec-driven-workflow-mcp:ref:refs/heads/main to repo:liatrio-labs/spec-driven-workflow:ref:refs/heads/main

This fixes the repo name mismatch that was causing the semantic release job to fail after the repository was renamed.

---

Job run | Branch