Fix PyPI publish workflow to run independently of GoReleaser
- Add 'if: always()' to publish-pypi job so it runs even if goreleaser fails - Remove 'go test' from .goreleaser.yml since CI already runs tests - This ensures MCP server gets published even if binary release has issues
This commit is contained in:
3
.github/workflows/release.yml
vendored
3
.github/workflows/release.yml
vendored
@@ -37,7 +37,8 @@ jobs:
|
|||||||
|
|
||||||
publish-pypi:
|
publish-pypi:
|
||||||
runs-on: ubuntu-latest
|
runs-on: ubuntu-latest
|
||||||
needs: goreleaser # Run after Go release succeeds
|
needs: goreleaser
|
||||||
|
if: always() # Run even if goreleaser fails
|
||||||
steps:
|
steps:
|
||||||
- name: Checkout
|
- name: Checkout
|
||||||
uses: actions/checkout@v4
|
uses: actions/checkout@v4
|
||||||
|
|||||||
@@ -7,8 +7,6 @@ before:
|
|||||||
hooks:
|
hooks:
|
||||||
# Ensure dependencies are up to date
|
# Ensure dependencies are up to date
|
||||||
- go mod tidy
|
- go mod tidy
|
||||||
# Run tests before building
|
|
||||||
- go test ./...
|
|
||||||
|
|
||||||
builds:
|
builds:
|
||||||
- id: bd
|
- id: bd
|
||||||
|
|||||||
Reference in New Issue
Block a user