Hacktoberfest 2026: as issues que os mantenedores marcaram para outubro, abertas e boas para iniciantes. Ver issues do Hacktoberfest

Keep dependency updates compatible with the OpenAI continuation patch

Aberta
  • Algo errado?
#1,212 0 comentários 0 reações 0 responsáveis Ver no GitHub

Mantenedores costumam responder em até 1 dia

Ninguém assumiu esta issue ainda.

Avaliação

Dificuldade
5/5
Tempo estimado
Mais de uma semana
Facilidade para iniciantes
35/100
Tipo de issue
Bug
Clareza
Razoavelmente clara
Status de atividade
Ativa
Stack de tecnologia
github-actions, typescript
Domínio
ci-cd, devops, testing-qa

Direção de pesquisa

Comece reproduzindo a etapa agendada pnpm up "@tanstack/*" --latest e execute tests/openai-responses-tool-continuation.test.ts com o patch de dependências atual. Inspecione o workflow do updater, a configuração do pnpm e o tratamento de patches descritos na issue. Está concluído quando a família TanStack AI puder ser atualizada sem regredir o comportamento de continuação e o workflow chegar a lint e build.

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

Descrição

source-audit

Evidence

The scheduled Update TanStack Dependencies run failed before lint or build on August 30. The exact pnpm up "@tanstack/*" --latest step exits with ERR_PNPM_UNUSED_PATCH because it moves @tanstack/openai-base away from the patched 0.10.5 version.

I reproduced the same failure from current main at 6584b153. In an isolated worktree, allowing unused patches let the update finish and changed @tanstack/ai-openai from 0.22.0 to 0.22.3, with @tanstack/openai-base moving from patched 0.10.5 to unpatched 0.10.8. The focused tests/openai-responses-tool-continuation.test.ts test then failed because the second request had no previous_response_id. The current patch is still required for sequential server-tool turns with provider-side reasoning.

Exact title, body, workflow, patch-package, and keyword searches found no open issue or PR that owns this failure.

Expected impact

The weekly dependency updater is currently guaranteed to fail whenever it tries the latest TanStack AI family. It never reaches the repository lint or build steps, so unrelated TanStack dependency updates also stop. Simply setting allowUnusedPatches or deleting the patch would make the workflow advance while regressing the Builder tool-continuation contract.

Proposed direction

Keep the focused continuation test as the release gate, then choose one owner for the patched AI family:

  1. Preferred long-term direction: ship the continuation behavior upstream, update the AI packages to the first release containing it, prove the focused test passes without the local patch, and delete the patch.
  2. Until that release exists: upgrade the pinned pnpm from 11.1.0 to a version that supports update.ignoreDeps and exclude the cohesive TanStack AI package set from the scheduled bulk updater. Upgrade that set separately, carrying the patch forward only after its focused test and the full suite pass.

Alternatives and tradeoffs

  • Manually port the 321-line patch to every new openai-base release. This keeps AI packages moving, but each port needs careful review against upstream adapter changes and should not be committed straight to main by a broad scheduled update.
  • Let pnpm up ignore unused patches. This unblocks the job but silently removes required runtime behavior, and the isolated focused test already proves the regression.
  • Exclude only @tanstack/ai-openai. This may still let related direct or transitive AI packages move out of a tested version set, so excluding and reviewing the cohesive AI family is safer.

Decision needed

@tannerlinsley, should we first upgrade pnpm and hold the TanStack AI family out of the weekly bulk updater, or prioritize landing the continuation behavior upstream and keep the weekly job blocked until a release contains it?

Linguagem predominante
TypeScript
Estrelas
1.1k
Forks
400
Merge médio
15h 38min
PRs com merge (30d)
54

Preparar o ambiente

Este projeto não oferece contêiner de desenvolvimento, Dockerfile nem guia de contribuição, então a configuração fica por sua conta: comece pelo README e veja nosso guia da primeira contribuição para os passos gerais.

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 TanStack/tanstack.com

Todas as issues de TanStack/tanstack.com

Issues semelhantes

Mais issues de TypeScript

Receba novas issues na sua caixa de entrada

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