Open
Conversation
- Add Host header validation against configured allowedDomains - Rename validate-forwarded-headers.ts to validate-headers.ts - Read error pages from disk first before falling back to experimentalErrorPageHost - Update test fixtures with appropriate allowedDomains configuration
Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
* add triage workflow, skills * update workflow * update workflow * update @flue/cli and @flue/client to latest * update @flue/cli and @flue/client to latest * add logging for git push * add back issue template * add back issue template * limit flue triage to issues created after 2026-02-11 * add better support for skipped reproductions * update workflow * update model * update skills * update skills * update skills * update agents.md * update agents.md * update agents.md * fix bad commit * updates * updates * update agents.md * update @flue/cli to 0.0.17 and @flue/client to 0.0.9 * use build scripts correctly * use anthropic/claude-opus-4 model identifier * update workflow * update workflow * update workflow --------- Co-authored-by: Fred K. Schott <fschott@cloudflare.com>
* Fix a flaky content collection test * Horrible editor experience bites again * forgot how astro works
* update workflow * update workflow * update workflow * update workflow * update workflow * update @flue/cli to 0.0.18 and @flue/client to 0.0.10 --------- Co-authored-by: Fred K. Schott <fschott@cloudflare.com>
* fix(cloudflare): remove worker output for fully static sites When all non-internal routes are prerendered, the _worker.js directory is now removed from the build output since it's not needed for static deployments. - Detect fully static sites in astro:routes:resolved - Remove _worker.js directory in astro:build:done for static sites - Change staticOutput support from 'unsupported' to 'stable' - Add test fixture and test for static output * fix: remove unused HookParameters import * Update lockfile * fix: require at least one non-internal route to be considered fully static
Co-authored-by: Matt Kane <m@mk.gg>
Co-authored-by: Sarah Rainsberger <5098874+sarah11918@users.noreply.github.com>
* fix broken commit/push workflow * update workflow --------- Co-authored-by: Fred K. Schott <fschott@cloudflare.com>
* fix(issue-triage): add "needs repro" label when reproduction fails * add priority and package labeling * let auto-triage run on old issues --------- Co-authored-by: Fred K. Schott <fschott@cloudflare.com>
* fix(config): preserve boolean allowedHosts * Update .changeset/short-pears-hammer.md Co-authored-by: Florian Lefebvre <contact@florian-lefebvre.dev> --------- Co-authored-by: Florian Lefebvre <contact@florian-lefebvre.dev>
* fix bad labeling logic * fix bad labeling logic * add gitbot token * Update issue-triage.ts * Change label formatting from bold to quotes --------- Co-authored-by: Fred K. Schott <fschott@cloudflare.com>
* fix: wait to bind shortcuts * add changeset * follow changeset style guidelines
* fix(markdoc): sync custom attributes between tags and nodes with shared names
In Markdoc, `table` exists as both a tag (`{% table %}`) and a node
(the inner table structure). When users configure custom attributes on
`nodes.table` or `tags.table`, the AST propagates those attributes to
both the tag and node, but validation only checks the schema for each
type independently. This caused "Invalid attribute" errors when
attributes were declared on only one side.
Add `syncTagNodeAttributes()` to automatically merge attribute
declarations between tags and nodes that share the same name after
config setup, so users can define attributes on either side.
Fixes #14220
* chore: clarify why explicit types are needed on builtinTags/builtinNodes
- **New:** Docker sandbox for issue triage: Run the LLM (OpenCode server) inside an isolated Docker container during triage workflows so untrusted reproduction code never has access to secrets. Adds a Dockerfile.sandbox, a GHCR build workflow, and updates the triage workflow to use --sandbox. Moves the compiler clone into .compiler/ (gitignored) so it's accessible inside the container's bind mount. - **New:** Add a `verify` step to the triage pipeline that checks whether reported behavior is intentional before attempting a fix. Fixes issues where the bot just trusted the submitting user's expected behavior as truth vs. potentially confused/incorrect on expected behavior. - **New:** Make diagnose and fix skills aware of the withastro/compiler repo (cloned as a sibling in CI). Fixes issues tracked back to the compiler, where the bot was trying to work around the issue in our astro codebase instead of pointing responsibility to the compiler. - **New:** Add a feasibility check to the fix skill for browser/runtime compatibility. Hopefully fixes issues where the bot suggests code that wouldn't run on modern browsers. - Fix: For some reason the reproduction instructions were gone (or never there?) so we hadn't been downloading repos/stackblitz, and probably spending quite a lot of time trying to figure out the bug without a reproduction. Kind of surprised by the success rate at reproductions, given this, but I guess everyone is including enough detail without it for the LLM to go off of. - Chore: Ensure all skills explicitly read report.md before appending to it - Chore: Simplify the diagnose skill's review step - Chore: Refactor issue-triage.ts into composable helper functions. - Chore: Ignore triage folder from eslint - Chore: Tidy up AGENTS.md, simplified the project layout section - Chore: Bump @flue/cli to 0.0.20 and @flue/client to 0.0.12
) * docs: fix test command syntax in AGENTS.md to use astro-scripts directly Replace package.json script references (test:unit, test:match, etc.) with direct astro-scripts test invocations. Add 'exec' to pnpm commands so astro-scripts is resolved as a bin, not a script name. Document key flags (--match, --parallel, --watch, --timeout, --only). * docs: improve triage skill reproduce step with path validation Clarify that triageDir must be passed as a positional argument to create-astro, and add a verification step to confirm the project was created at the expected path before proceeding. * fix: use cp from examples/ instead of create-astro for triage scaffolding create-astro pulls the latest published Astro from npm, which doesn't match the monorepo version during beta. Copy from examples/ instead to ensure the workspace-linked version is always used. * update @flue/cli to 0.0.31 --------- Co-authored-by: Fred K. Schott <fschott@cloudflare.com>
* update workflows * pass issueDetails to comment.md * fix(triage): detect committed fix changes using git diff instead of git status The fix skill may commit its changes directly, leaving git status --porcelain empty. Use git diff main --stat to detect both committed and uncommitted changes before pushing the fix branch. * fix(triage): use pnpm install --no-frozen-lockfile in reproduce skill * chore: update @flue/cli to 0.0.32 and @flue/client to 0.0.18 --------- Co-authored-by: Fred K. Schott <fschott@cloudflare.com>
Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
* fix(deps): update all non-major dependencies * Discard changes to examples/blog/package.json * fix: lockfile --------- Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com> Co-authored-by: Florian Lefebvre <contact@florian-lefebvre.dev>
* perf: switch to clack spinner This is an incremental change as part of the wider move to clack. * perf: switch to clack for box rendering Switches to using clack for rendering boxes in the terminal. Part of the wider migration to clack. * perf: switch to clack for confirm prompts Switches to using clack for confirm prompts rather than `prompts` package. Part of the wider clack migration. * chore: use new spinner API * chore: use bold confirm messages * fix * fix * upgrade clack * update clack * improve * improve * changeset --------- Co-authored-by: Florian Lefebvre <contact@florian-lefebvre.dev>
Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
* Switch to @changesets/changelog-git * Fix lint * Patch changesets GitHub info batching
* chore: update docs links * Update packages/astro/CHANGELOG.md Co-authored-by: Armand Philippot <git@armand.philippot.eu> --------- Co-authored-by: Armand Philippot <git@armand.philippot.eu>
Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
Co-authored-by: rohan436 <rohan.santhoshkumar@googlemail.com>
Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
Co-authored-by: Matthew Phillips <matthewphillips@cloudflare.com> Co-authored-by: Matthew Phillips <matthewphillips@cloudflare.com>
* fix(add): restore tsconfig diff preview in astro add * Update .changeset/green-dingos-care.md Co-authored-by: Florian Lefebvre <contact@florian-lefebvre.dev> --------- Co-authored-by: Florian Lefebvre <contact@florian-lefebvre.dev>
Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
…15803) * fix(cloudflare): provisions the SESSION KV binding when the effective session driver is actually Cloudflare KV * Create nervous-keys-grin.md
Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
…in (#15850) Options like `configPath`, `inspectorPort`, `persistState`, `remoteBindings`, and `auxiliaryWorkers` were accepted by the type system but never passed to `cfVitePlugin()`, making them no-ops. Also fixes the `addWatchFile` path resolution for `configPath` which used `createRequire(import.meta.url)` — resolving relative to the adapter's package directory instead of the project root. Fixes #15846 Co-authored-by: Claude Opus 4.6 <noreply@anthropic.com>
* feat(cloudflare): add prerenderEnvironment config option * feat(cloudflare): dev server prerender middleware * chore: add changeset * fix changeset * Update .changeset/cloudflare-prerender-environment.md Co-authored-by: Sarah Rainsberger <5098874+sarah11918@users.noreply.github.com> * fix(cloudflare): register prerender middleware after Vite security checks * feat(cloudflare): route dev prerender handling through Astro core middleware * fix: remove additional astro environment * adds tests * update lockfile * fix: add todo comment back * move dev prerender environment from core to adapter * fix: remove unnecessary astro environment invalidation in routes plugin * Remove unused settingsSymbol * fix: add astro changeset for dev prerender core handling * Don't skip dots * Update .changeset/astro-dev-prerender-core-fixes.md Co-authored-by: Sarah Rainsberger <5098874+sarah11918@users.noreply.github.com> --------- Co-authored-by: Sarah Rainsberger <5098874+sarah11918@users.noreply.github.com> Co-authored-by: Matthew Phillips <matthewphillips@cloudflare.com> Co-authored-by: Matthew Phillips <matthew@matthewphillips.info>
Co-authored-by: astro-security[bot] <astro-security[bot]@users.noreply.github.com>
Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
* Update minimumReleaseAgeExclude config for Starlight * Update pnpm-workspace.yaml Co-authored-by: Chris Swithinbank <swithinbank@gmail.com> --------- Co-authored-by: Chris Swithinbank <swithinbank@gmail.com>
…15815) * fix(cloudflare): prebundle SSR deps needed for Starlight dev * fix(cloudflare): drop server entry from optimizeDeps * docs(changeset): add cloudflare optimize deps note * Improve changeset * fix(cloudflare): only prebundle content runtime in dev
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
See Commits and Changes for more details.
Created by
pull[bot]
Can you help keep this open source service alive? 💖 Please sponsor : )