gitea-mcp-server: update checksum for 1.3.0 release - #288966
Closed
stefanb wants to merge 1 commit into
Closed
Conversation
This was referenced Jun 20, 2026
Member
|
Changed again? |
Member
Author
|
Gitea seems to change checksum on every request: |
Member
|
I think gitea artifact checksum change is some sort of known issue, I filed an upstream issue before. |
Member
|
The current url is redirecting to login page. Also clicking on archive downloads via website goes to:
Seems like Gitea's git archive usage is broken. In this case, it may be more stable to use a git checkout and add comment on Gitea issues. |
Member
|
Archive url is on upstream "expensive" list which requires login. It's been there for a while so I'm guessing a recent change may have fixed the block: This will impact all Gitea-based formulae other than ❯ curl "https://gitea.com/gitea/gitea-mcp/archive/v1.3.0.tar.gz"
<a href="/user/login?redirect_to=%2Fgitea%2Fgitea-mcp%2Farchive%2Fv1.3.0.tar.gz">See Other</a>.
❯ curl "https://gitea.com/gitea/runner/archive/v1.0.8.tar.gz"
<a href="/user/login?redirect_to=%2Fgitea%2Frunner%2Farchive%2Fv1.0.8.tar.gz">See Other</a>.
❯ curl "https://gitea.com/gitea/tea/archive/v0.14.1.tar.gz"
<a href="/user/login?redirect_to=%2Fgitea%2Ftea%2Farchive%2Fv0.14.1.tar.gz">See Other</a>. |
7 tasks
Member
Author
|
Superseded by |
github-actions
Bot
deleted the
gitea-mcp-server-update-checksum-for-1.3.0-release
branch
June 29, 2026 07:55
pull Bot
pushed a commit
to MuntasirSZN/homebrew-core
that referenced
this pull request
Jun 29, 2026
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.
Ref:
HOMEBREW_NO_INSTALL_FROM_API=1 brew install --build-from-source <formula>?brew test <formula>?brew audit --strict <formula>(after doingHOMEBREW_NO_INSTALL_FROM_API=1 brew install --build-from-source <formula>)? If this is a new formula, does it passbrew audit --new <formula>?