[Refactor][Build] Remove the end-of-support aws-sdk-go v1 from backend/go.mod

Fechada
  • Algo errado?
#9,196 0 comentários 0 reações 0 responsáveis Ver no GitHub

Mantenedores costumam responder em até 2 dias

Ninguém assumiu esta issue ainda.

Avaliação

Dificuldade
2/5
Tempo estimado
1-3 horas
Facilidade para iniciantes
55/100
Tipo de issue
Refatoração
Clareza
Razoavelmente clara
Status de atividade
Ativa
Stack de tecnologia
go
Domínio
build-system

Direção de pesquisa

First check #9195, which covers migrating the sole consumer in backend/plugins/kiro; this cleanup depends on that migration. Then inspect backend/go.mod and backend/.golangci.yaml, run go mod tidy, and remove the v1 dependency and temporary SA1019 exclusion. Done means backend/go.mod and backend/go.sum no longer include aws-sdk-go v1 and lint passes without the exclusion.

Escrita pelo modelo de indexação a partir do texto da issue.

Descrição

What and why to refactor

backend/go.mod still requires github.com/aws/aws-sdk-go (v1). AWS ended
support for the v1 SDK on
2025-07-31:
no more bug fixes, no more security fixes. v1.55.8 is the last release and
deprecates every package, which is how it surfaced in #9192 (lint red with
11× SA1019).

Keeping an unsupported SDK in the dependency tree means:

  • any future CVE in it will not be fixed upstream by AWS,
  • every Dependabot gomod run that touches it re-triggers the deprecation
    warnings, which currently have to be suppressed by a lint exclusion,
  • security scanners will increasingly flag it.

Describe the solution you'd like

  1. Migrate the only consumer, backend/plugins/kiro, to aws-sdk-go-v2
    (separate issue: #9195).
  2. Remove github.com/aws/aws-sdk-go from backend/go.mod / go.sum
    (go mod tidy).
  3. Remove the temporary staticcheck exclusion for SA1019 /
    plugins/kiro/ from backend/.golangci.yaml (added in #9197).
  4. Optional guard: add a depguard rule (or a simple grep in CI) that rejects
    new imports of github.com/aws/aws-sdk-go/, so v1 does not come back
    through another plugin.

@warren830 — since kiro is currently the sole user of the AWS SDK in
DevLake, looping you in here as well. If you plan further AWS-based plugins,
starting them on v2 would avoid repeating this.

Related issues

  • #9195 (code migration of the kiro plugin)
  • #9192 (Dependabot go-minor-patch group)
  • #9197 (temporary lint exclusion + CI paths fix)

Additional context

q_dev, the previous AWS-based plugin, was removed in #9079, so after the
kiro migration no code in the repository depends on v1 anymore.

Linguagem predominante
Go
Estrelas
3.2k
Forks
832
Merge médio
1d 22h
PRs com merge (30d)
75

Preparar o ambiente

Abrir no Codespaces

Inicia o contêiner de desenvolvimento do projeto no navegador, com a sua própria conta do GitHub.

  • Sem Dockerfile nem arquivo Docker Compose
  • Tem um modelo de pull request
  • Sem guia de contribuição

Primeiros passos

  1. Leia a issue inteira e depois o guia de contribuição do projeto.
  2. Comente na issue dizendo que vai assumir — evita que duas pessoas façam o mesmo trabalho.
  3. Faça um fork do repositório e trabalhe em uma branch.
  4. Abra um pull request que referencie o número da issue.

Mais de apache/devlake

Todas as issues de apache/devlake

Issues semelhantes

Mais issues de Go

Receba novas issues na sua caixa de entrada

Um resumo curto de issues do GitHub para quem está começando.