Skip to content

Fix release workflow to create GitHub releases#358

Merged
bokelley merged 6 commits intomainfrom
bokelley/test-schema-release
Dec 24, 2025
Merged

Fix release workflow to create GitHub releases#358
bokelley merged 6 commits intomainfrom
bokelley/test-schema-release

Conversation

@bokelley
Copy link
Contributor

Summary

Add publish step to the release workflow so that GitHub releases are created automatically when version packages are merged.

Problem

The createGithubReleases: true option only triggers when there's a publish command. Without it, the changesets action logs:

"Not publishing because no publish script found."

Solution

Added publish: echo "Published" as a no-op publish step to trigger release creation.

Note

I manually created the v2.5.1 release that was missed: https://github.com/adcontextprotocol/adcp/releases/tag/v2.5.1

🤖 Generated with Claude Code

bokelley and others added 6 commits December 24, 2025 07:57
Add publish command to trigger GitHub release creation.
Without a publish step, createGithubReleases doesn't run.

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude Opus 4.5 <[email protected]>
Update .gitignore to:
- Ignore dist/* but allow dist/schemas/ directory
- Ignore dist/schemas/latest/ (rebuilt on every dev build)
- Ignore dist/schemas/v*/ (symlinks, not tracked in git)
- Preserve released version directories (2.5.0/, 2.5.1/, etc.)

This ensures released schema versions persist across CI runs while
development changes only affect the latest/ directory.

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude Opus 4.5 <[email protected]>
The previous commit incorrectly built 2.5.0 and 2.5.1 from current
source schemas. This commit rebuilds them from their actual git tags
to preserve the exact schemas that were released.

Key differences:
- 2.5.0: No bundled/ directory (feature added later), different schema structure
- 2.5.1: Has bundled/ directory with schemas as they were at release time

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude Opus 4.5 <[email protected]>
When running --release, the build script now stages the new versioned
schema directory (e.g., dist/schemas/2.6.0/) for git commit. This
ensures the changesets workflow includes the released schemas in the
"Version Packages" commit.

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude Opus 4.5 <[email protected]>
The regular `npm run build` (used by Docker) should use development
mode to:
1. Preserve existing committed released directories (2.5.0/, 2.5.1/)
2. Only rebuild latest/ from current source
3. Create symlinks pointing to the latest released version

Only `npm run version` (used during changeset releases) should use
--release mode to create new versioned directories.

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude Opus 4.5 <[email protected]>
@bokelley bokelley merged commit 9b635a4 into main Dec 24, 2025
6 checks passed
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