[Bug]: Bundle pins can become unresolvable after component catalog updates
Mantenedores costumam responder em até 2 dias
Ninguém assumiu esta issue ainda.
Avaliação
- Dificuldade
- 3/5
- Tempo estimado
- 1-2 dias
- Facilidade para iniciantes
- 55/100
Direção de pesquisa
Look at the bundle resolver code, likely in a module handling extension or component resolution. The bug is that the resolver looks up by ID only, not by ID and pinned version. Find where catalog entries are fetched and version checks are performed. Start by reproducing the scenario with a test bundle and catalog. 'Done' means the resolver correctly attempts to retrieve the pinned version from its original URL even if a newer version is advertised.
Escrita pelo modelo de indexação a partir do texto da issue.
Descrição
Bug Description
Bundle 0.4.12 pins an extension to 0.4.12. Because component catalogs contain only the currently advertised release, updating the extension’s catalog entry to 0.5.1 replaces the version and download URL used by bundle resolution. The resolver looks up the extension by ID—not by ID and pinned version—so the unchanged bundle now resolves to the 0.5.1 entry. The subsequent version check rejects that selection. It never attempts to retrieve 0.4.12, even when that release remains available.
Steps to Reproduce
This scenario is derived from source inspection; runtime reproduction is still needed.
-
Prepare a bundle that pins an extension or preset to version
0.4.12. -
Make that version available through an install-enabled component catalog.
-
Update the catalog entry to advertise version
0.5.1, leaving the0.4.12release artifact available at its original URL. -
In a fresh initialized project with no affected components installed, configure that component catalog.
-
Install the original bundle using
specify bundle install <path-to-bundle.yml>. -
Observe that component resolution rejects the version mismatch before attempting to retrieve the pinned release.
Expected Behavior
The bundle retrieves and installs its pinned component version when that release remains available, regardless of whether a newer version is advertised.
If the pinned version cannot be retrieved, installation reports that clearly without silently substituting another version.
Actual Behavior
The inspected resolver compares the bundle’s pin against the selected catalog entry’s version and raises an error when they differ. It does not attempt to locate the older pinned release.
Specify CLI Version
1.0.10
AI Agent
GitHub Copilot
Operating System
To be recorded during runtime reproduction.
Python Version
To be recorded during runtime reproduction.
Error Logs
No runtime logs captured. The inspected extension resolver produces the following error for the example above:
Extension 'specassay-check' is pinned to version 0.4.12 in the bundle manifest, but the resolved version is 0.5.1. Update the bundle's pinned version or the source before installing.
Additional Context
Observed during #4703
AI Disclosure
GitHub Copilot using GPT-6 Astra (gpt-6-astra), human-supervised, assisted with source inspection, related-issue research, and drafting this report.
- Linguagem predominante
- Python
- Estrelas
- 138k
- Forks
- 12.4k
- Merge médio
- 2d 11h
- PRs com merge (30d)
- 163
Preparar o ambiente
Primeiros passos
- Leia a issue inteira e depois o guia de contribuição do projeto.
- Comente na issue dizendo que vai assumir — evita que duas pessoas façam o mesmo trabalho.
- Faça um fork do repositório e trabalhe em uma branch.
- Abra um pull request que referencie o número da issue.
Mais de github/spec-kit
-
Windows: Copilot integration hardcodes `copilot.cmd`, breaking installs that ship `copilot.exe`Abertabug-assess severity-medium
Dificuldade 2/5 1-3 horas Facilidade para iniciantes 88/100
github/spec-kit#4755 · 1 comentário ·
Mantenedores costumam responder em até 2 dias
-
triage-nice-to-have
Dificuldade 2/5 1-3 horas Facilidade para iniciantes 88/100
Mantenedores costumam responder em até 2 dias
-
[Feature]: 给 slug 添加默认值Abertaenhancement needs-triage triage-can-wait
Dificuldade 2/5 1-3 horas Facilidade para iniciantes 65/100
github/spec-kit#4627 · 3 comentários ·
Mantenedores costumam responder em até 2 dias
-
needs-triage triage-nice-to-have
Dificuldade 2/5 1-3 horas Facilidade para iniciantes 72/100
github/spec-kit#4527 · 1 comentário ·
Mantenedores costumam responder em até 2 dias
-
bug-assess severity-medium
Dificuldade 2/5 1-3 horas Facilidade para iniciantes 72/100
github/spec-kit#4273 · 3 comentários ·
Mantenedores costumam responder em até 2 dias
Todas as issues de github/spec-kit
Issues semelhantes
-
Dificuldade 2/5 1-3 horas Facilidade para iniciantes 78/100
solana-foundation/pay-kit#341 ·
Mantenedores costumam responder em até 1 dia
-
Dificuldade 2/5 1-3 horas Facilidade para iniciantes 78/100
nasa/python_cmr#123 ·
-
Dificuldade 1/5 Menos de uma hora Facilidade para iniciantes 92/100
EleutherAI/lm-evaluation-harness#4243 ·
Mantenedores costumam responder em até 1 dia
-
area: dashboard bug perceived difficulty: 3
Dificuldade 2/5 1-3 horas Facilidade para iniciantes 88/100
Nitjsefnie-Harness-Commons/daedalus#1179 ·
Mantenedores costumam responder em até 1 dia
-
Dificuldade 2/5 1-3 horas Facilidade para iniciantes 88/100
cusp-ai-oss/tojax#17 ·