apply after diff not creating a Github PR

[ringods]

I have a working UpdateCLI setup to bump some Go dependencies in my go.mod file. A local diff shows the expected updates.

Now trying to run this on a weekly basis (and a workflow-dispatch trigger to test manually) via Github Actions. I started with the Github Actions workflow from the end of this page:

https://www.updatecli.io/docs/automate/github_action/

This triggers a diff and an apply sequentially.

My run succeeds, but no Github PR is created. Tracking what might be wrong, my assumption is the following.

diff

The diff action checks out the repo again, finds the outdated dependencies, updates these but halts there.

#########################################################
# DEPS(GO): BUMP MODULE GITHUB.COM/PULUMI/PULUMI/PKG/V3 #
#########################################################

source: source#module
-------------
Searching for version matching pattern ">=3.116.1"
✔ version v3.191.0 found for the GO module "github.com/pulumi/pulumi/pkg/v3"

target: target#module
-------------

**Dry Run enabled**

⚠ - go.mod should update Module path "github.com/pulumi/pulumi/pkg/v3" version from "v3.116.1" to "v3.191.0"

apply

I guess the apply action uses the same checked out version but now already finds it updated:

#########################################################
# DEPS(GO): BUMP MODULE GITHUB.COM/PULUMI/PULUMI/SDK/V3 #
#########################################################

source: source#module
-------------
Searching for version matching pattern ">=3.191.0"
✔ version v3.191.0 found for the GO module "github.com/pulumi/pulumi/sdk/v3"

target: target#module
-------------
✔ - go.mod already has Module "github.com/pulumi/pulumi/sdk/v3" set to version "v3.191.0"

So no PR is created as a result.

Any subsequent run is even worse because the diff of the new run also detects that the dependency is updated. Does it use a cache of some sort? Does UpdateCLI not clean up the checked out repository by default?

To be complete, here is the list of my direct dependencies from the latest commit in my repo:

module github.com/ringods/pulumi-tool-d2

go 1.23.0

toolchain go1.24.1

require (
	github.com/pulumi/pulumi/pkg/v3 v3.116.1
	github.com/pulumi/pulumi/sdk/v3 v3.116.1
	golang.org/x/exp v0.0.0-20240719175910-8a7402abbf56
	oss.terrastruct.com/d2 v0.6.5
)

[ringods]

In the meantime, I also tried the following commands:

updatecli compose diff --clean
updatecli compose diff --clean=true

but neither performs any cleanup of the UpdateCLI working folder.

[olblak]

If a target is linked to a scm using the scmid then it's reset automatically in diff mode
Is it possible that you already published the changes on a previous iteration?

do you already have a branch named like updatecli_main_xxx

⚠ - go.mod should update Module path "github.com/pulumi/pulumi/pkg/v3" version from "v3.116.1" to "v3.191.0"

It's only displayed the first time it changes something, following iteration will work from the temporary branch.

Could you share your updatecli manifest?

[olblak]

I wonder if you specified the scmid and the actionid if you are using the Golang autodiscovery plugin such ash

https://github.com/updatecli/policies/blob/42f76010f7ed647fb5934022a40b7a2ce58ba55e/updatecli/policies/autodiscovery/golang/updatecli.d/default.tpl#L10 and https://github.com/updatecli/policies/blob/main/updatecli/policies/autodiscovery/golang/updatecli.d/_scm.github.yaml

[olblak]

Or just a scmid per target

updatecli/updatecli/updatecli.d/devcontainer.yaml

Line 51 in e82aa7f

scmid: default

If you use the declarative approach

[ringods]

@olblak I wasn't aware of the branch already being created. After deleting the branch and triggering the GH workflow again, a PR is correctly created.

[olblak]

Normally updatecli should have reopen the pull request