Renaming of project has caused code archive SHAs to change about terminal-to-html HOT 4 CLOSED

For a moment I thought you were reporting that the archive's we published in v3.1.0 had been changed because of the rename. But then I noticed the URL you've reported is GitHub’s URL for downloading a tgz of the repo contents for a given tag, not the actual v3.1.0 release.

Is there some standard tooling that's broken, that uses that URL?

from terminal-to-html.

For a moment I thought you were reporting that the archive's we published in v3.1.0 had been changed because of the rename. But then I noticed the URL you've reported is GitHub’s URL for downloading a tgz of the repo contents for a given tag, not the actual v3.1.0 release.

The links that I pasted above do correspond with the 'Source code (tar.gz)' links on the release page, right?

Is there some standard tooling that's broken, that uses that URL?

Nothing standard per se; I bumped into this because Bazel Buildbarn uses the URL to the tarball in its workspace. I've updated the workspace file in the meantime.

from terminal-to-html.

Ah interesting! It does correspond to the source code, but I think that top level directory is automatically added by GitHub and is probably the cause of the SHA change 😢 I'm not sure it's possible to rename a project in GitHub and not break the SHAs for those "Source Code" links in the releases.

from terminal-to-html.

I don't think there's a way we can fix this, at least with the capabilities GitHub provides, so I'm going to close this. Sorry!

from terminal-to-html.