Paul Meyer

This is still an issue. Run into it today while testing.

I've encountered this problem multiple times writing my thesis. See [this question on tex.stackexchange.com](https://tex.stackexchange.com/questions/648289/latexmk-fails-after-max-runs-due-to-cyclic-author-replacement-in-citation) for detailed description.

Thanks for your answer, @greybax. I didn't opened this issue because I couldn't get my workflow running, but because I think the action should terminate with an error if the...

@taylorwaggoner - Yes, I thought this would be a good idea after a major version release and the links were broken, too. Based on your question I assume that this...

To further support these changes, here are some examples for popular repos ignoring `go.work.sum`: https://github.com/hashicorp/nomad/pull/13193 https://github.com/gravitational/teleport/pull/12098 https://github.com/sourcegraph/sourcegraph/pull/36049

> Why not `**go.sum`? The sum file is used to check locally, I think. > [ Typically your module's go.sum file should be committed along with your go.mod file.](https://github.com/golang/go/wiki/Modules#should-i-commit-my-gosum-file-as-well-as-my-gomod-file)

/remove-lifecycle stale

> Go 1.22 can go straight to master True, I've cherry picked the 1.22 update into https://github.com/NixOS/nixpkgs/pull/293580.

Any updates on this issue? We're still seeing this on a daily basis.

Sorry @mmerkes, I missed your comment. Here is the config we are using (this is Kubernetes v1.26.3): ```yaml apiVersion: apps/v1 kind: DaemonSet metadata: annotations: deprecated.daemonset.template.generation: "1" meta.helm.sh/release-name: constellation-services meta.helm.sh/release-namespace: kube-system...