Port #567

[ScharfViktor]

Bumps github.com/nats-io/nats.go from 1.39.1 to 1.41.0.

• Release notes
• Commits

---

updated-dependencies:

• dependency-name: github.com/nats-io/nats.go dependency-version: 1.41.0 dependency-type: direct:production update-type: version-update:semver-minor ...

Description

Related Issue

• Fixes <issue_link>

Motivation and Context

How Has This Been Tested?

• test environment:
• test case 1:
• test case 2:
• ...

Screenshots (if appropriate):

Types of changes

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to change)
• Technical debt
• Tests only (no source changes)

Checklist:

• Code changes
• Unit tests added
• Acceptance tests added
• Documentation added

[micbar]

We should not bump this on the stable branch.

[ScharfViktor]

We should not bump this on the stable branch.

then we get error:

make clean
- activitylog: clean
go: inconsistent vendoring in /Users/v.scharf/Work/opencloud/opencloud:
        github.com/nats-io/nats.go@v1.41.0: is explicitly required in go.mod, but not marked as explicit in vendor/modules.txt
        github.com/nats-io/nats.go@v1.39.1: is marked as explicit in vendor/modules.txt, but not explicitly required in go.mod

        To ignore the vendor directory, use -mod=readonly or -mod=mod.
        To sync the vendor directory, run:
                go mod vendor
make[1]: *** [clean] Error 1
make: *** [clean] Error 1

when I run go mod vendor -> I update to github.com/nats-io/nats.go v1.41.0

[micbar]

maybe this package has also been bumped in reva.

[ScharfViktor]

maybe this package has also been bumped in reva.

no, they're not up to date there.
https://github.com/opencloud-eu/reva/blob/stable-2.29/go.mod#L59-L60

should I do it? and create new reva release and new bump?