Repository navigation
Labels
Description
🤖 Generated by the Agentic Engineer (interactive Claude Code session)
Problem
#408 releases a patch for build(deps) commits, which covers the three runtime dependencies (@sveltejs/adapter-node, drizzle-orm, pg). Svelte, SvelteKit, Vite, Tailwind and the enhanced-img plugin are dev dependencies, so their updates arrive as build(deps-dev) and release nothing, yet adapter-node bundles them into the server build guests use. #407 named this as a known limit; this issue closes it.
Evidence
- Two open Dependabot PRs are exactly this case: build(deps-dev): bump vite from 8.3.2 to 8.3.4 #419 (Vite 8.3.2 → 8.3.4) and build(deps-dev): bump svelte from 5.57.1 to 5.57.2 #420 (Svelte 5.57.1 → 5.57.2). Once merged, neither cuts a release.
- adapter-node bundles what is in
devDependenciesand leavesdependenciesexternal, so the fix must not move these packages intodependencies: that would change what the production image has to install.
Hypothesis
If updates to the bundled framework and compiler packages release a patch on their own, they reach guests within one release cycle, and a framework regression surfaces right after the update that caused it, not inside a later unrelated release.
Success signal and window
- Within two weekly Dependabot cycles after merge, the next update to an allow-listed bundled package cuts a patch release that the platform then serves.
- Lint, type-check, test and database-tooling updates still release nothing.
Smallest useful change
- Keep an explicit allow-list of the bundled packages (Svelte, SvelteKit, the Svelte Vite plugin, Vite, Tailwind and its Vite plugin, enhanced-img, the self-hosted fonts and icons) and release a patch for updates to exactly those, without moving them between
dependenciesanddevDependencies. One option is a Dependabot group for them whose commits the release rule matches; confirm the release tool can match it before choosing. - Pin the allow-list with a test, so a newly added bundled package cannot fall outside it.
- Use the same mechanism as ascoachingogvaner#316 where it fits, so both sites behave the same way.
Acceptance criteria
- Updates to allow-listed bundled packages release a patch; tooling-only
build(deps-dev),ci,docsandchorecommits do not. -
dependencies,devDependenciesand the bundled server output are unchanged by the classification. - A test fails when a bundled package is outside the allow-list.
-
AGENTS.mdnames which commits cut a release.
Rough size
S.
Metadata
Metadata
Assignees
Labels
Type
Fields
Priority
None yet
Effort
None yet
Projects
- StatusShow more project fields✅ Done
Activity
chore: agent-claim #422 nonce=1c2e75478bd139f7797ef5df692b74d1
fix(release): release updates to bundled framework and compiler packa…
devantler commentedon Oct 17, 2026
Delivered by #424 (merged 2026-10-17T09:49Z); the Node image is pinned by #425 (#423).
build(deps)update merged just before them.fix(release)rather than the PR's editedci(release)title, so it cut v1.15.21, a rebuild with no change guests can see.site-bundlepackage releases a patch by itself, and toolingbuild(deps-dev)andci(deps)updates do not. Check the first Dependabot cycle after 2026-10-24.