Skip to content

gitea-mcp-server: update checksum for 1.3.0 release - #288966

Closed
stefanb wants to merge 1 commit into
mainfrom
gitea-mcp-server-update-checksum-for-1.3.0-release
Closed

gitea-mcp-server: update checksum for 1.3.0 release#288966
stefanb wants to merge 1 commit into
mainfrom
gitea-mcp-server-update-checksum-for-1.3.0-release

Conversation

@stefanb

@stefanb stefanb commented Jun 20, 2026

Copy link
Copy Markdown
Member

Ref:


  • Have you followed the guidelines for contributing?
  • Have you ensured that your commits follow the commit style guide?
  • Have you checked that there aren't other open pull requests for the same formula update/change?
  • Have you built your formula locally with HOMEBREW_NO_INSTALL_FROM_API=1 brew install --build-from-source <formula>?
  • Is your test running fine brew test <formula>?
  • Does your build pass brew audit --strict <formula> (after doing HOMEBREW_NO_INSTALL_FROM_API=1 brew install --build-from-source <formula>)? If this is a new formula, does it pass brew audit --new <formula>?

  • AI was used to generate or assist with generating this PR. Please specify below how you used AI to help you, and what steps you have taken to manually verify the changes.

@stefanb stefanb added the checksum mismatch SHA-256 doesn't match the download label Jun 20, 2026
@github-actions github-actions Bot added the go Go use is a significant feature of the PR or issue label Jun 20, 2026
@daeho-ro

Copy link
Copy Markdown
Member

Changed again?

curl -sL https://gitea.com/gitea/gitea-mcp/archive/v1.3.0.tar.gz | shasum -a 256
959918a26527e629a7101678f15c8039a0c327e779ee6492e9c2485fb76e270c

@stefanb

stefanb commented Jun 20, 2026

Copy link
Copy Markdown
Member Author

Gitea seems to change checksum on every request:

$ curl -sL https://gitea.com/gitea/gitea-mcp/archive/v1.3.0.tar.gz | shasum -a 256
a0dca84ed80002c48b3ec80211001e9f57861e42fdd637ee8e5a085514112242  -
$ curl -sL https://gitea.com/gitea/gitea-mcp/archive/v1.3.0.tar.gz | shasum -a 256
c8d752978c9f9361767d8f2861624fc86a8e37f92feaa2ebdaf649559ea39ef8  -
$ curl -sL https://gitea.com/gitea/gitea-mcp/archive/v1.3.0.tar.gz | shasum -a 256
971995fad1c9b907c9d1b1b0d6c56b9e6b528e39e3c5ed16538e7f6debfeabfb  -

@chenrui333

Copy link
Copy Markdown
Member

I think gitea artifact checksum change is some sort of known issue, I filed an upstream issue before.

@stefanb

stefanb commented Jun 21, 2026

Copy link
Copy Markdown
Member Author

@cho-m

cho-m commented Jun 28, 2026

Copy link
Copy Markdown
Member

The current url is redirecting to login page. Also clicking on archive downloads via website goes to:

Failed to download the archive: Unexpected token '<', "<!DOCTYPE "... is not valid JSON

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.

@cho-m

cho-m commented Jun 28, 2026

Copy link
Copy Markdown
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 gitea which is on dl.gitea.com

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>.

@stefanb

stefanb commented Jun 29, 2026

Copy link
Copy Markdown
Member Author

@stefanb stefanb closed this Jun 29, 2026
@github-actions
github-actions Bot deleted the gitea-mcp-server-update-checksum-for-1.3.0-release branch June 29, 2026 07:55
@stefanb stefanb added the superseded PR was replaced by another PR label Jun 29, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

checksum mismatch SHA-256 doesn't match the download go Go use is a significant feature of the PR or issue superseded PR was replaced by another PR

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants