Yoshiki Fujikane

@t-kikuc Thank you for the comment 🙏 I fixed them. - fix description for the usecase [3ab416e](https://github.com/pipe-cd/pipecd/pull/5127/commits/3ab416e3d56ed7190f295d5e7423c06ab1f1d907) - clarified the options as isolated ones. - removed the one that is...

This incident was due to a part of PipeCD not considering the kustomize specifications. It can mainly occur when deploying a helm chart using kustomize (< 5.3.0) & enable-helm. Also,...

# Investigation ## Overview The premise is that during driftdetection, a Git repository is cloned and then pulled and reused. Additionally, a common manifest cache is used for driftdetection, plan...

I think there are some solutions, but mainly making a fix for the drift detection process. 1. clone the repo from the git provider for every drift detections 2. select...

📝 It might be useful to add some metadata as git trailer https://git-scm.com/docs/git-interpret-trailers#_description

We will fix actions-event-register after releasing this fix. Follow https://github.com/pipe-cd/pipecd/issues/5307 for it.

Ref: #4980

@kiratlog Thank you for the PR. At first, we need to clarify the authentication method for the helm chart registry. Could you investigate it more, other than basic authentication? If...

@hongky-1994 I found that the difference in behavior between the demo.pipecd.dev, and this fix. Filtering events by status appears to reset the state. Could you check it? 1. On the...

[Root cause] Resources in the old namespace cannot be deleted because the namespace is not included in the conditions for searching the deletion target resources. Inside PipeCD, resources are identified...