Skip to content

fix(ci): per-module prerelease tags in nightly workflow - #147

Closed
kwit75 wants to merge 2 commits into
developfrom
fix/nightly-per-module-prerelease
Closed

kwit75 wants to merge 2 commits into
developfrom
fix/nightly-per-module-prerelease

Conversation

@kwit75

@kwit75 kwit75 commented Mar 2, 2026

Copy link
Copy Markdown
Collaborator

Summary

  • Replace single nightly-YYYYMMDD tag/release with per-module prerelease tags
  • Each module gets its own GitHub Release marked as prerelease:
    • server-v1.0.3-prerelease
    • client-typescript-v1.0.1-prerelease
    • client-python-v1.0.1-prerelease
    • client-mcp-v0.1.0-prerelease
    • vscode-v0.0.1-prerelease
  • Tags are force-updated on re-runs (same as before with nightly tag)
  • Matches the release workflow's per-module pattern

Test plan

  • Trigger nightly via workflow_dispatch
  • Verify 5 separate prerelease tags are created
  • Verify each has the correct artifacts attached

Dmitrii Karataev added 2 commits March 2, 2026 11:20
Replace single nightly-YYYYMMDD tag with per-module prerelease tags:
server-v1.0.3-prerelease, client-typescript-v1.0.1-prerelease, etc.

Each module gets its own GitHub Release marked as prerelease, matching
the release workflow's per-module pattern.
generate_release_notes fails on force-updated tags (no diff to compare).
Use a static body instead.
@kwit75

kwit75 commented Mar 2, 2026

Copy link
Copy Markdown
Collaborator Author

Closing in favor of #145 (fix/workflow) which covers the same changes plus additional improvements.

@kwit75 kwit75 closed this Mar 2, 2026
@kwit75
kwit75 deleted the fix/nightly-per-module-prerelease branch March 2, 2026 19:24
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant