- Delete existing release before creating new one to avoid conflicts - Remove llmx-responses-api-proxy from dotslash config (not needed) - Add 'Create GitHub Release' step to upload platform binaries - Configure npm authentication by writing token to setup-node's .npmrc - Use internal package identifier 'llmx' in workflow scripts This fixes the release workflow to properly: 1. Clean up previous failed releases 2. Create GitHub release with all platform binaries 3. Add DotSlash manifest file (llmx) without conflicts 4. Publish to npm as @valknarthing/llmx with proper authentication 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude <noreply@anthropic.com>
821 B
821 B