Daniel Martí

Already gained some conflicts :) friendly bump, happy to solve them

A large amount of conflicts at this point. I'll leave it to you to figure out whether you want to obey these tools - I very much think you should.

quay.io seems to be down again, for the sake of keeping record.

> For temporary setting up a repo we see a lot of different versions being used which makes it harder to push them up without rebuilding a year of releases....

quay.io seems to be back up, for those following the thread. So about four hours of downtime in total.

Had a reply from @pelletier on Slack: basically this was for performance. He's happy with removing unsafe as long as the performance doesn't drop significantly, or perhaps if we can...

At least speaking personally, for cases like https://github.com/mvdan/sh/issues/519, my intent is to show something like `devel ${GIT_SHA}` when someone does a local Go build out of a git checkout. If...

> we shouldn't make such a "locally inferred version" look like a normal version, because it's reasonably likely to be wrong or cause confusion with users. To add a more...

@4ad right, a local build can't always know what is or isn't published, as requiring a network roundtrip takes us back to square one. Your idea of trying to stick...

We do have another hash available to us, though, which changes whenever any input Go code changes: the build IDs used for the build cache. I seem to recall that...