Hacktoberfest 2026: los issues que los mantenedores marcaron para octubre, abiertos y aptos para principiantes. Explorar issues de Hacktoberfest

Pinnable dev host slot for child CI — versioned host bundle URLs or a first-class local-host runner

Abierto
  • ¿Algo no está bien?
#613 0 comentarios 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 1 día

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
5/5
Tiempo estimado
Más de una semana
Aptitud para principiantes
25/100
Tipo de issue
Nueva funcionalidad
Claridad
Bien especificado
Estado de actividad
Activo
Stack tecnológico
typescript
Área
ci-cd, devtools

Línea de trabajo

Start with ADR 0034 and the referenced issues #531, #579, #609, and #610 to understand the pinning and manifest-slot decisions. Then trace the dev:ssr host resolution in everything-dev and compare the two proposed approaches: versioned host bundle URLs or a local-host runner. Done means a design is recorded in an ADR and child CI continues testing the pinned host version across parent redeploys.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

enhancement ready-for-agent

Context

Split out of #531 (closed today) — the evidence review showed the reported 403 mechanism was never a host-injection defect; the amplifier was this design gap, which remains unimplemented:

A child's dev:ssr stack composes the parent's production host from the CDN's "current" slot — overwritten on every parent deploy:

[Config] Could not load local target for \"app.host\", using production
→ https://cdn.everything.dev/bundles/dev.everything.near/everything.dev/host/
  • The CDN serves only "current" root files; `versions/*.json` entries are metadata, not addressable bundles.
  • The child's `platform` pin does not control the dev host slot (per #531's evidence: the child pinned rc.17 while the host slot had moved).
  • Children have no `host` workspace, so `host: { development: "local:…" }` is not an option.

Consequence: child dev:ssr CI breaks whenever the parent redeploys, for reasons invisible in the child's diff. The Oct 20–24 incident (#531) is the case study — the child's suite went red against a parent deploy it could neither see nor pin, then stayed red through three child upgrades before the mitigations landed.

Ask

Per ADR 0034 ("one pin, everything derives"), either:

  1. Versioned host bundle URLs — serve host bundles at addressable per-release paths, with the child dev stack resolving `app.host` from its pinned platform release manifest; or
  2. A first-class local-host runner in everything-dev, so `host: { development: "local:…" }` works for children without a host workspace.

Either makes a child's dev:ssr suite test the host version its platform pin names instead of whatever the parent deployed most recently. #531's mitigations (skew gates, #580) closed the observed failure modes; this closes the recurrence class.

Acceptance

  • A child dev:ssr stack composes the host version its platform pin names (slot-addressed or local runner).
  • A parent redeploy between two child CI runs cannot change what the child's dev stack tests against.
  • The design decision is recorded in an ADR amendment (ADR 0034 or a new ADR), covering how the dev host slot interacts with the release-scoped manifest slots (#609/#610).

Relations

  • Split from #531 (evidence + timeline there).
  • Unblocks #579's gating half to hold: children can't have stable regression gating while their dev host floats.
  • Builds on: #609/#610 (immutable manifest slots, slot-first pin resolution).
Lenguaje dominante
TypeScript
Estrellas
5
Forks
3
Merge medio
9 h 37 min
PR fusionados (30 d)
157

Preparar el entorno

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de NEARBuilders/everything-dev

Todos los issues de NEARBuilders/everything-dev

Issues similares

Más issues de TypeScript

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.