Skip to content

fix: publish fallback package when npm is blocked#104

Merged
KryptosAI merged 1 commit into
mainfrom
codex/release-fallback-artifact
Jun 19, 2026
Merged

fix: publish fallback package when npm is blocked#104
KryptosAI merged 1 commit into
mainfrom
codex/release-fallback-artifact

Conversation

@KryptosAI

Copy link
Copy Markdown
Owner

Summary

  • Keep the existing npm token and Trusted Publishing release paths unchanged.
  • When both npm auth paths are unavailable, pack a distinct fallback version like 0.20.3-github.<run>.
  • Upload the tarball as an Actions artifact and publish it as a GitHub prerelease asset with a direct install command.

Validation

  • Parsed .github/workflows/release.yml with Ruby YAML loader.

@github-actions

Copy link
Copy Markdown

🔭 MCP Observatory — All clear ✅

All checks passed. No security issues, no schema quality warnings.

📊 Summary

Gate: fail · 0 tools · 0 prompts · 0 resources


🔭 MCP Observatory — test your MCP servers for breaking changes · ⭐ Star

@KryptosAI KryptosAI merged commit f7fd819 into main Jun 19, 2026
2 checks passed
@KryptosAI KryptosAI deleted the codex/release-fallback-artifact branch June 19, 2026 04:38
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