feat(ci): auto-trigger Glama build on every GitHub release#411
Closed
ajitpratap0 wants to merge 0 commit intomainfrom
Closed
feat(ci): auto-trigger Glama build on every GitHub release#411ajitpratap0 wants to merge 0 commit intomainfrom
ajitpratap0 wants to merge 0 commit intomainfrom
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
Owner
Author
|
All changes from this PR are already in main via #410. Closing as superseded. |
506d952 to
e4ae22c
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
.github/workflows/glama-sync.ymlthat fires automatically on every published GitHub releaseglama.jsonversion in sync with the release tagHow it works
Two jobs run in parallel on
release: published:bump-glama-version(continue-on-error: true)vprefix from the release tagglama.json.versionfield viajq[skip ci]back to the release branchtrigger-glama-buildintent=buildpinnedCommitSha=${{ github.sha }}— pins build to exact release commitmcp-proxy -- /app/gosqlx-mcp --stdioGLAMA_SESSION_COOKIEis not configuredRequired one-time setup
Glama's admin API is session-authenticated (no public API). Store the browser session cookie as a repository secret:
https://glama.ai/mcp/servers/ajitpratap0/GoSQLX/admin/dockerfileglama.ai→ Headers → copy the Cookie header valueGLAMA_SESSION_COOKIETest plan
GLAMA_SESSION_COOKIEsecret (see setup above)🤖 Generated with Claude Code