dependabot / dependabot/dependabot-core

Change summary for aws-sdk-go-v2 show wrong commits / diff

Open
#12,938 0 comments 0 reactions 0 assignees View on GitHub
L: go:modules T: bug 🐞
Dominant language
Ruby
Stars
5.8k
Forks
1.5k
Avg merge
2d 18h
Merged PRs (30d)
149

Description

### Is there an existing issue for this?

- [x] I have searched the existing issues

### Package ecosystem

gomod

### Package manager version

_No response_

### Language version

Go 1.24.6

### Manifest location and content before the Dependabot update

_No response_

### dependabot.yml content

```version: 2
updates:
- package-ecosystem: "gomod"
directory: "/"
schedule:
interval: "daily"
groups:
aws-sdk:
patterns:
- "github.com/aws/aws-sdk-go-v2"
- "github.com/aws/aws-sdk-go-v2/*"
extensions:
patterns:
- "golang.org/x/*"
```

### Updated dependency

Repo: https://github.com/aws/aws-sdk-go-v2

We use `github.com/aws/aws-sdk-go-v2/service/sqs` in our codebase.

### What you expected to see, versus what you actually saw

What I saw:

Image

These are commits from 2023. The `compare view` link goes to `https://github.com/aws/aws-sdk-go-v2/compare/service/kms/v1.41.2...service/s3/v1.42.0` which shows that Dependabot has done the diff on the wrong tags.

The correct URL (and base for the listed commits) would have been https://github.com/aws/aws-sdk-go-v2/compare/service/sqs/v1.41.2...service/sqs/v1.42.0

I expected to only show the commits from the update.

### Native package manager behavior

_No response_

### Images of the diff or a link to the PR, issue, or logs

Image

### Smallest manifest that reproduces the issue

_No response_

Contributor guide

Open the contributing guide

Research direction

Start with the reported dependabot.yml configuration and reproduce the grouped gomod update for github.com/aws/aws-sdk-go-v2/service/sqs. Trace how the update builds its compare URL and commit list, then verify that both use the service/sqs/v1.41.2 and service/sqs/v1.42.0 tags rather than unrelated AWS service tags.

Written by the indexing model from the issue text.

Assessment

Tech stack
go
Domain
tooling
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.