Skip to content

AstroEco is Contributing…

Display your GitHub pull requests using astro-loader-github-prs

withastro/starlight

updated

withastro/astro

This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to main, this PR will be updated.

Releases

astro@5.15.5

Patch Changes

withastro/astro

Changes

Mirrors #14728 but applied to next branch

Testing

no tests

Docs

no docs needed

withastro/astro

Changes

This shortens all of the major changesets to only their first line, and adds a heading to the specific entry with full info and guidance in the v6 upgrade guide deploy preview

Testing

No tests. Only affects the generated CHANGELOG.md

Docs

No additional docs needed

withastro/astro

This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to next, this PR will be updated.

⚠️⚠️⚠️⚠️⚠️⚠️

next is currently in pre mode so this branch has prereleases rather than normal releases. If you want to exit prereleases, run changeset pre exit on next.

⚠️⚠️⚠️⚠️⚠️⚠️

Releases

astro@6.0.0-alpha.0

Major Changes

Minor Changes

  • #14550 9c282b5 Thanks @ascorbic! - Adds support for live content collections

    Live content collections are a new type of content collection that fetch their data at runtime rather than build time. This allows you to access frequently updated data from CMSs, APIs, databases, or other sources using a unified API, without needing to rebuild your site when the data changes.

    Live collections vs build-time collections

    In Astro 5.0, the content layer API added support for adding diverse content sources to content collections. You can create loaders that fetch data from any source at build time, and then access it inside a page via getEntry() and getCollection(). The data is cached between builds, giving fast access and updates.

    However, there was no method for updating the data store between builds, meaning any updates to the data needed a full site deploy, even if the pages are rendered on demand. This meant that content collections were not suitable for pages that update frequently. Instead, these pages tended to access the APIs directly in the frontmatter. This worked, but it led to a lot of boilerplate, and meant users didn't benefit from the simple, unified API that content loaders offer. In most cases, users tended to individually create loader libraries shared between pages.

    Live content collections (introduced experimentally in Astro 5.10) solve this problem by allowing you to create loaders that fetch data at runtime, rather than build time. This means that the data is always up-to-date, without needing to rebuild the site.

    How to use

    To use live collections, create a new src/live.config.ts file (alongside your src/content.config.ts if you have one) to define your live collections with a live content loader using the new defineLiveCollection() function from the astro:content module:

    import { defineLiveCollection } from 'astro:content';
    import { storeLoader } from '@mystore/astro-loader';
    
    const products = defineLiveCollection({
      loader: storeLoader({
        apiKey: process.env.STORE_API_KEY,
        endpoint: 'https://api.mystore.com/v1',
      }),
    });
    
    export const collections = { products };

    You can then use the getLiveCollection() and getLiveEntry() functions to access your live data, along with error handling (since anything can happen when requesting live data!):

    ---
    import { getLiveCollection, getLiveEntry, render } from 'astro:content';
    // Get all products
    const { entries: allProducts, error } = await getLiveCollection('products');
    if (error) {
      // Handle error appropriately
      console.error(error.message);
    }
    
    // Get products with a filter (if supported by your loader)
    const { entries: electronics } = await getLiveCollection('products', { category: 'electronics' });
    
    // Get a single product by ID (string syntax)
    const { entry: product, error: productError } = await getLiveEntry('products', Astro.params.id);
    if (productError) {
      return Astro.redirect('/404');
    }
    
    // Get a single product with a custom query (if supported by your loader) using a filter object
    const { entry: productBySlug } = await getLiveEntry('products', { slug: Astro.params.slug });
    const { Content } = await render(product);
    ---
    
    <h1>{product.data.title}</h1>
    <Content />

    Upgrading from experimental live collections

    If you were using the experimental feature, you must remove the experimental.liveContentCollections flag from your astro.config.* file:

     export default defineConfig({
       // ...
    -  experimental: {
    -    liveContentCollections: true,
    -  },
     });

    No other changes to your project code are required as long as you have been keeping up with Astro 5.x patch releases, which contained breaking changes to this experimental feature. If you experience problems with your live collections after upgrading to Astro v6 and removing this flag, please review the Astro CHANGELOG from 5.10.2 onwards for any potential updates you might have missed, or follow the current v6 documentation for live collections.

Patch Changes

  • Updated dependencies [727b0a2]:
    • @astrojs/markdown-remark@7.0.0-alpha.0

@astrojs/prism@4.0.0-alpha.0

Major Changes

create-astro@5.0.0-alpha.0

Major Changes

@astrojs/cloudflare@13.0.0-alpha.0

Major Changes

Patch Changes

@astrojs/mdx@5.0.0-alpha.0

Major Changes

Patch Changes

@astrojs/netlify@7.0.0-alpha.0

Major Changes

Patch Changes

@astrojs/preact@5.0.0-alpha.0

Major Changes

@astrojs/react@5.0.0-alpha.0

Major Changes

@astrojs/solid-js@6.0.0-alpha.0

Major Changes

@astrojs/svelte@8.0.0-alpha.0

Major Changes

Patch Changes

@astrojs/vue@6.0.0-alpha.0

Major Changes

Patch Changes

@astrojs/markdown-remark@7.0.0-alpha.0

Major Changes

Patch Changes

  • Updated dependencies [e131261]:
    • @astrojs/prism@4.0.0-alpha.0

@astrojs/db@0.19.0-alpha.0

Minor Changes

@astrojs/alpinejs@0.5.0-alpha.0

Minor Changes

@astrojs/markdoc@1.0.0-alpha.0

Minor Changes

Patch Changes

@astrojs/upgrade@0.7.0-alpha.0

Minor Changes

@astrojs/node@10.0.0-alpha.0

Patch Changes

@astrojs/vercel@10.0.0-alpha.0

Patch Changes

@astrojs/check@0.9.6-alpha.0

Patch Changes

  • Updated dependencies [df6d2d7]:
    • @astrojs/language-server@2.16.1-alpha.0

@astrojs/language-server@2.16.1-alpha.0

Patch Changes

withastro/starlight

Description

Continuing on the effort to speed up CI, I noticed that on Windows, the E2E tests took 3 minutes to install some dependendcies before even starting to download Chrome.

After checking the Playwright core codebase, it turns out that this is due to the installation of the Server Media Foundation windows feature on Windows Server.

Altho, something I noticed is that this is only required for Chromium-based browsers.

Therefore, this PR changes the Windows E2E tests on CI to use Firefox instead of Chrome, which skips this step and immediately starts downloading Firefox before running the tests.

Before After
SCR-20251106-pldu SCR-20251106-pmaz

This also has the added benefit of running our E2E tests on a different browser.

withastro/astro

Changes

  • Extracted from #14609
  • As I worked on refactoring astro info, the scope unexpectedly exploded
  • This PR extracts some of the changes that are required by #14609 but can be done before:
    • Moves where the polyfill is applied (doesn't matter much, removed in v6)
    • Moves some abstractions as they are not local anymore (eg. not only for astro docs) but shared across several commands
    • Updates some abstractions in preparation for other usages

Testing

Updated, should pass

Docs

N/A, refactor

withastro/astro

Changes

  • When Astro.glob() was removed on next, language tools were not part of the repo yet
  • Removes Astro.glob() handling in the language server

Testing

N/A, blocked by #14717

Docs

Updates the changeset scope

withastro/starlight

Description

  • Closes #
  • What does this PR change? Give us a brief description.
  • Did you change something visual? A before/after screenshot can be helpful.

Removing three showcase sites as they result in status code errors using https://lychee.cli.rs/

Running lychee https://starlight.astro.build/resources/showcase/ outputs

Issues found in 1 input. Find details below.

[https://starlight.astro.build/resources/showcase/]:
[522] https://astro-ghostcms.xyz/ | Rejected status code (this depends on your "accept" configuration): Unknown status code
[ERROR] https://dev.vrchatfrance.fr/ | Network error: error sending request for url (https://dev.vrchatfrance.fr/) Maybe a certificate error?
[ERROR] https://docs.ryzekit.com/ | Network error: error sending request for url (https://docs.ryzekit.com/) Maybe a certificate error?

🔍 247 Total (in 40s) ✅ 244 OK 🚫 3 Errors

withastro/astro

Changes

Since the branch is in pre-mode, I think that's all we need?

Testing

N/A

Docs

N/A

withastro/astro

Changes

  • Astro officially only supports node >=22.12, and in practice ^20.19.5 as well. But that's not enough for our language tools tests
  • Allows bypassing the version check

Testing

Should pass

Docs

N/A, internal

withastro/astro

Changes

See https://github.com/netlify/primitives/releases/tag/functions-v5.0.0. The breaking changes do not apply here, as we're only using the type exports, which are unchanged.

Without accounting for deduping, this removes 310 transitive dependencies and 82 MB from the @astrojs/netlify dependency tree.

Testing

N/A — no user-facing changes

Docs

N/A — no user-facing changes

withastro/astro

Changes

Adds clientEntrypoint to the object returned by getContainerRenderer() in framework integrations. This makes the return value an AstroRenderer, so this also deprecates the ContainerRenderer type in favour of that. In several integrations there is already a getRenderer function that returns this, but this isn't standardised, and some need arguments. This PR tries to wrap or re-export these where appropriate.

It seems we were already specifying AstroRenderer as the type passed to loadRenderers, so this doesn't need changing.

The reason to do this is to support client hydration in getContainerRenderer(). The objects returned from these can be used with the loadRenderers helper in a Vite environment, instead of needing users to manually load the correct renderer entrypoints. Previously this didn't return the client entrypoint value, so it required users to manually call container.addClientRenderer() with the appropriate client renderer entrypoint to support hydration.

Testing

Our tests don't use Vitest so we can't test this directly. Instead, I added this to examples/container-with-vitest and tested that.

Docs

The docs don't currently state that client-side hydration is unsupported when using getContainerRenderer, so this doesn't need changing.

withastro/starlight

This PR fixes various typos I spotted in the project.

withastro/astro

Currently, when creating a new changeset via command npx @changesets/cli, an error is thrown:

🦋 ...
🦋  === Summary of changesets ===
🦋  minor:  astro
🦋
🦋  Note: All dependents of these packages that will be incompatible with the new version will be patch bumped when this changeset is applied.
🦋
🦋  Is this your desired changeset? (Y/n) · true
🦋  error Error [ERR_REQUIRE_ESM]: require() of ES Module C:\Users\xxx\GitHub\astro\prettier.config.js from C:\Users\xxx\AppData\Local\npm-cache\_npx\c21dc4ee7bbf9939\node_modules\prettier\third-party.js not supported.
🦋  error Instead change the require of prettier.config.js in C:\Users\xxx\AppData\Local\npm-cache\_npx\c21dc4ee7bbf9939\node_modules\prettier\third-party.js to a dynamic import() which is available in all CommonJS modules.
🦋  error     at module2.exports (C:\Users\xxx\AppData\Local\npm-cache\_npx\c21dc4ee7bbf9939\node_modules\prettier\third-party.js:83:61)
🦋  error     at loadJs2 (C:\Users\xxx\AppData\Local\npm-cache\_npx\c21dc4ee7bbf9939\node_modules\prettier\third-party.js:8050:22)
🦋  error     at Explorer.loadFileContent (C:\Users\xxx\AppData\Local\npm-cache\_npx\c21dc4ee7bbf9939\node_modules\prettier\third-party.js:8449:36)
🦋  error     at Explorer.createCosmiconfigResult (C:\Users\xxx\AppData\Local\npm-cache\_npx\c21dc4ee7bbf9939\node_modules\prettier\third-party.js:8453:40)
🦋  error     at Explorer.loadSearchPlace (C:\Users\xxx\AppData\Local\npm-cache\_npx\c21dc4ee7bbf9939\node_modules\prettier\third-party.js:8438:35)
🦋  error     at async Explorer.searchDirectory (C:\Users\xxx\AppData\Local\npm-cache\_npx\c21dc4ee7bbf9939\node_modules\prettier\third-party.js:8428:31) {
🦋  error   code: 'ERR_REQUIRE_ESM'
🦋  error }

This PR resolves that issue by renaming config file prettier.config.js to prettier.config.mjs.
This is in line with the README.md file of the Prettier Pugin for Astro which also suggest to use prettier.config.mjs as config file.

withastro/astro

Changes

Testing

Should pass, manual

Docs

Changeset

withastro/astro

Changes

  • Reported on withastro/docs#12648
  • During an Astro build, Vite is started in dev and build several times, sometimes even in parallel
  • The astro:env Vite plugin had some caching logic that retained the dev behavior in build, resulting in inlining process.env in the build output in some cases
  • This PR refactors this Vite plugin to avoid this situation

Testing

Manual, should pass

Docs

Changeset

withastro/starlight

Description

I have added some more or less interesting blog posts to my blog and noticed that some of them are not yet listed on the awesome community content site. So I decided to create this PR adding them in chronological order 🙌

withastro/astro

This PR fixes a few typos I spotted in the project.

withastro/astro

Changes

  • The description of the "Content-intellisense" setting in the VS Code extension refers to the relevant configuration file option as "experimental.contentCollectionIntellisense". This is incorrect; I changed it to say "experimental.contentIntellisense".
  • Grammar fix ("require" → "requires").

(This is my first pull request to Astro, apologies in advanced if I missed anything!)

Testing

No tests were added, this is just a documentation fix.

Docs

No docs were added, this is just a documentation fix.

withastro/starlight

Description

  • I noticed I messed up the paths in the filters added in #3520 so this PR fixes them
  • I’m also not 100% confident it is set up correctly yet. I noticed a11y checks were skipped in #3510 even though based on the changes job output it looks like it should have run.
withastro/starlight

Description

We were setting margin-bottom as -2px when at the same time we had a bottom border of 2px. Using this indirect margin was causing the tab container to be greater in height than it's wrapper when we zoomed out from the default zoom level. This introduced an unnecessary scroll bar.

Zoom Level Before After
90% Screenshot 2025-11-03 at 4 01 35 PM Screenshot 2025-11-03 at 4 01 43 PM
100% Screenshot 2025-11-03 at 3 53 30 PM Screenshot 2025-11-03 at 3 53 57 PM

I'm not sure if this PR warrants a minor version bump or not, let me know if it does.

withastro/starlight

Description

Follow-up of #3507 (comment) that also uninstalls man-db in the Linux e2e tests to prevent potential long delays after package installations.

This is done only on Linux:

image

And skipped on Windows:

image
withastro/starlight

This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to main, this PR will be updated.

Releases

@astrojs/starlight@0.36.3

Patch Changes

withastro/astro

This PR contains the following updates:

Package Change Age Confidence
@astrojs/solid-js (source) ^5.1.1 -> ^5.1.2 age confidence
@astrojs/svelte (source) ^7.2.0 -> ^7.2.1 age confidence
@astrojs/vue (source) ^5.1.1 -> ^5.1.2 age confidence
@cloudflare/workers-types ^4.20251011.0 -> ^4.20251014.0 age confidence
@netlify/blobs ^10.1.0 -> ^10.3.1 age confidence
@netlify/vite-plugin ^2.7.2 -> ^2.7.8 age confidence
@types/send (source) ^0.17.5 -> ^0.17.6 age confidence
@vercel/routing-utils (source) ^5.2.0 -> ^5.2.1 age confidence
devalue ^5.4.1 -> ^5.4.2 age confidence
rollup (source) ^4.52.4 -> ^4.52.5 age confidence
solid-js (source) ^1.9.9 -> ^1.9.10 age confidence
svelte (source) ^5.40.2 -> ^5.43.2 age confidence
vite (source) ^6.4.0 -> ^6.4.1 age confidence
wrangler (source) 4.43.0 -> 4.45.3 age confidence

Release Notes

withastro/astro (@​astrojs/solid-js)

v5.1.2

Compare Source

Patch Changes
withastro/astro (@​astrojs/svelte)

v7.2.1

Compare Source

Patch Changes
withastro/astro (@​astrojs/vue)

v5.1.2

Compare Source

Patch Changes
netlify/primitives (@​netlify/blobs)

v10.3.1

Compare Source

v10.3.0

Compare Source

vercel/vercel (@​vercel/routing-utils)

v5.2.1

Compare Source

Patch Changes
  • Add experimental support for routes.json (#​14138)
sveltejs/svelte (svelte)

v5.43.2

Compare Source

Patch Changes
  • fix: treat each blocks with async dependencies as uncontrolled (#​17077)

v5.43.1

Compare Source

Patch Changes
  • fix: transform $bindable after await expressions (#​17066)

v5.43.0

Compare Source

Minor Changes
Patch Changes
  • fix: settle batch after DOM updates (#​17054)

v5.42.3

Compare Source

Patch Changes
  • fix: handle <svelte:head> rendered asynchronously (#​17052)

  • fix: don't restore batch in #await (#​17051)

v5.42.2

Compare Source

Patch Changes
  • fix: better error message for global variable assignments (#​17036)

  • chore: tweak memoizer logic (#​17042)

v5.42.1

Compare Source

Patch Changes
  • fix: ignore fork discard() after commit() (#​17034)

v5.42.0

Compare Source

Minor Changes
Patch Changes
  • fix: always allow setContext before first await in component (#​17031)

  • fix: less confusing names for inspect errors (#​17026)

cloudflare/workers-sdk (wrangler)

v4.45.3

Patch Changes
  • #​11117 6822aaf Thanks @​emily-shen! - fix: show local/remote status before D1 command confirmations

    D1 commands (execute, export, migrations apply, migrations list, delete, time-travel) now display whether they're running against local or remote databases before showing confirmation prompts. This prevents confusion about which database will be affected by the operation.

  • #​11077 bce8142 Thanks @​petebacondarwin! - Ensure that process.env is case-insensitive on Windows

    The object that holds the environment variables in process.env does not care about the case of its keys
    in Windows. For example, process.env.SystemRoot and process.env.SYSTEMROOT will refer to the same value.

    Previously, when merging fields from .env files we were replacing this native object with a vanilla
    JavaScript object, that is case-insensitive, and so sometimes environment variables appeared to be missing
    when in reality they just had different casing.

v4.45.2

Patch Changes

v4.45.1

Compare Source

Patch Changes

v4.45.0

Compare Source

Minor Changes
  • #​11030 1a8088a Thanks @​penalosa! - Enable automatic resource provisioning by default in Wrangler. This is still an experimental feature, but we're turning on the flag by default to make it easier for people to test it and try it out. You can disable the feature using the --no-x-provision flag. It currently works for R2, D1, and KV bindings.

    To use this feature, add a binding to your config file without a resource ID:

    {
    	"kv_namespaces": [{ "binding": "MY_KV" }],
    	"d1_databases": [{ "binding": "MY_DB" }],
    	"r2_buckets": [{ "binding": "MY_R2" }],
    }

    wrangler dev will automatically create these resources for you locally, and when you next run wrangler deploy Wrangler will call the Cloudflare API to create the requested resources and link them to your Worker. They'll stay linked across deploys, and you don't need to add the resource IDs to the config file for future deploys to work. This is especially good for shared templates, which now no longer need to include account-specific resource ID when adding a binding.

Patch Changes
  • #​11037 4bd4c29 Thanks @​danielrs! - Better Wrangler subdomain defaults warning.

    Improves the warnings that we show users when either worker_dev or preview_urls are missing.

  • #​10927 31e1330 Thanks @​dom96! - Implements python_modules.excludes wrangler config field

    [python_modules]
    excludes = ["**/*.pyc", "**/__pycache__"]
  • #​10741 2f57345 Thanks @​penalosa! - Remove obsolete --x-remote-bindings flag

  • Updated dependencies [ca6c010]:

    • miniflare@​4.20251011.1

v4.44.0

Compare Source

Minor Changes
  • #​10939 d4b4c90 Thanks @​danielrs! - Config preview_urls defaults to workers_dev value.

    Originally, we were defaulting config.preview_urls to true, but we
    were accidentally enabling Preview URLs for users that only had
    config.workers_dev=false.

    Then, we set the default value of config.preview_urls to false, but we
    were accidentally disabling Preview URLs for users that only had
    config.workers_dev=true.

    Rather than defaulting config.preview_urls to true or false, we
    default to the resolved value of config.workers_dev. Should result in a
    clearer user experience.

  • #​11027 1a2bbf8 Thanks @​jamesopstad! - Statically replace the value of process.env.NODE_ENV with development for development builds and production for production builds if it is not set. Else, use the given value. This ensures that libraries, such as React, that branch code based on process.env.NODE_ENV can be properly tree shaken.

  • #​9705 0ee1a68 Thanks @​hiendv! - Add params type to Workflow type generation. E.g.

    interface Env {
    	MY_WORKFLOW: Workflow<
    		Parameters<import("./src/index").MyWorkflow["run"]>[0]["payload"]
    	>;
    }
  • #​10867 dd5f769 Thanks @​austin-mc! - Add media binding support

Patch Changes
  • #​11018 5124818 Thanks @​dario-piotrowicz! - Improve potential errors thrown by startRemoteProxySession by including more information

  • #​11019 6643bd4 Thanks @​dario-piotrowicz! - Fix observability.logs.persist being flagged as an unexpected field during the wrangler config file validation

  • #​10768 8211bc9 Thanks @​dario-piotrowicz! - Update logs handling to use the new handleStructuredLogs miniflare option

  • #​10997 3bb034f Thanks @​nikitassharma! - When either WRANGLER_OUTPUT_FILE_PATH or WRANGLER_OUTPUT_FILE_DIRECTORY are set
    in the environment, then command failures will append a line to the output file
    encoding the error code and message, if present.

  • #​10986 43503c7 Thanks @​emily-shen! - fix: cleanup any running containers again on wrangler dev exit

  • #​11000 a6de9db Thanks @​jonboulle! - always load container image into local store during build

    BuildKit supports different build drivers. When using the more modern docker-container driver (which is now the default on some systems, e.g. a standard Docker installation on Fedora Linux), it will not automatically load the built image into the local image store. Since wrangler expects the image to be there (e.g. when calling getImageRepoTags), it will thus fail, e.g.:

    ⎔ Preparing container image(s)...
    [+] Building 0.3s (8/8) FINISHED                                                                                                                                                                                                     docker-container:default
    
    [...]
    
    WARNING: No output specified with docker-container driver. Build result will only remain in the build cache. To push result image into registry use --push or to load image into docker use --load
    
    ✘ [ERROR] failed inspecting image locally: Error response from daemon: failed to find image cloudflare-dev/sandbox:f86e40e4: docker.io/cloudflare-dev/sandbox:f86e40e4: No such image
    
    

    Explicitly setting the --load flag (equivalent to -o type=docker) during the build fixes this and should make the build a bit more portable without requiring users to change their default build driver configuration.

  • #​10994 d39c8b5 Thanks @​pombosilva! - Make Workflows instances list command cursor based

  • #​10892 7d0417b Thanks @​dario-piotrowicz! - improve the diffing representation for wrangler deploy (run under --x-remote-diff-check)

  • Updated dependencies [36d7054, dd5f769, ee7d710, 8211bc9]:

v4.43.0

Compare Source

Minor Changes
Patch Changes
  • #​10938 e52d0ec Thanks @​penalosa! - Acquire Cloudflare Access tokens for additional requests made during a wrangler dev --remote session

  • #​10923 2429533 Thanks @​emily-shen! - fix: update docker manifest inspect to use full image registry uri when checking if the image exists remotely

  • #​10521 88b5b7f Thanks @​penalosa! - Improves the Wrangler auto-provisioning feature (gated behind the experimental flag --x-provision) by:

    • Writing back changes to the user's config file (not necessary, but can make it resilient to binding name changes)
    • Fixing --dry-run, which previously threw an error when your config file had auto provisioned resources
    • Improve R2 bindings display to include the bucket_name from the config file on upload
    • Fixing bindings view for specific versions to not display TOML

v4.42.2

Compare Source

Patch Changes
  • #​10881 ce832d5 Thanks @​garvit-gupta! - Add table-level compaction commands for R2 Data Catalog:

    • wrangler r2 bucket catalog compaction enable <bucket> [namespace] [table]
    • wrangler r2 bucket catalog compaction disable <bucket> [namespace] [table]

    This allows you to enable and disable automatic file compaction for a specific R2 data catalog table.

  • #​10888 d0ab919 Thanks @​lrapoport-cf! - Clarify that wrangler check startup generates a local CPU profile

  • Updated dependencies [42e256f, 4462bc1]:

    • miniflare@​4.20251008.0

v4.42.1

Compare Source

Patch Changes

v4.42.0

Compare Source

Minor Changes
Patch Changes

v4.41.0

Compare Source

Minor Changes
  • #​10507 21a0bef Thanks @​dario-piotrowicz! - Add strict mode for the wrangler deploy command

    Add a new flag: --strict that makes the wrangler deploy command be more strict and not deploy workers when the deployment could be potentially problematic. This "strict mode" currently only affects non-interactive sessions where conflicts with the remote settings for the worker (for example when the worker has been re-deployed via the dashboard) will cause the deployment to fail instead of automatically overriding the remote settings.

  • #​10710 7f2386e Thanks @​penalosa! - Add prompt to resource creation flow allowing for newly created resources to be remote.

Patch Changes

v4.40.3

Compare Source

Patch Changes

v4.40.2

Compare Source

Patch Changes

v4.40.1

Compare Source

Patch Changes

v4.40.0

Compare Source

Minor Changes
  • #​10743 a7ac751 Thanks @​jonesphillip! - Changes --fileSizeMB to --file-size for wrangler r2 bucket catalog compaction command.
    Small fixes for pipelines commands.
Patch Changes
  • #​10706 81fd733 Thanks @​1000hz! - Fixed an issue that caused some Workers to have an incorrect service tag applied when using a redirected configuration file (as used by the Cloudflare Vite plugin). This resulted in these Workers not being correctly grouped with their sibling environments in the Cloudflare dashboard.

  • Updated dependencies [06e9a48]:

    • miniflare@​4.20250924.0

v4.39.0

Compare Source

Minor Changes
  • #​10647 555a6da Thanks @​efalcao! - VPC service binding support

  • #​10612 97a72cc Thanks @​jonesphillip! - Added new pipelines commands (pipelines, streams, sinks, setup), moved old pipelines commands behind --legacy

  • #​10652 acd48ed Thanks @​edmundhung! - Rename Hyperdrive local connection string environment variable from WRANGLER_HYPERDRIVE_LOCAL_CONNECTION_STRING_<BINDING_NAME> to CLOUDFLARE_HYPERDRIVE_LOCAL_CONNECTION_STRING_<BINDING_NAME>. The old variable name is still supported but will now show a deprecation warning.

  • #​10721 55a10a3 Thanks @​penalosa! - Stabilise Worker Loader bindings

Patch Changes

v4.38.0

Compare Source

Minor Changes
Patch Changes

v4.37.1

Compare Source

Patch Changes
  • #​10658 3029b9a Thanks @​1000hz! - Fixed an issue with service tags not being applied properly to Workers when the Wrangler configuration file did not include a top-level name property.

  • #​10657 31ec996 Thanks @​penalosa! - Disable remote bindings with the --local flag

  • Updated dependencies [783afeb]:

    • miniflare@​4.20250913.0

v4.37.0

Compare Source

Minor Changes
  • #​10546 d53a0bc Thanks @​1000hz! - On deploy or version upload, Workers with multiple environments are tagged with metadata that groups them together in the Cloudflare Dashboard.

  • #​10596 735785e Thanks @​penalosa! - Add Miniflare & Wrangler support for unbound Durable Objects

  • #​10622 15c34e2 Thanks @​nagraham! - Modify R2 Data Catalog compaction commands to enable/disable for Catalog (remove table/namespace args), and require Cloudflare API token on enable.

Patch Changes
  • Updated dependencies [735785e]:
    • miniflare@​4.20250906.2

v4.36.0

Compare Source

Minor Changes

Configuration

📅 Schedule: Branch creation - Between 12:00 AM and 03:59 AM, only on Monday ( * 0-3 * * 1 ) (UTC), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.


  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

withastro/astro

This PR contains the following updates:

Package Change Age Confidence Type Update Pending
@astrojs/compiler (source) ^2.10.3 -> ^2.13.0 age confidence dependencies patch
@jridgewell/sourcemap-codec (source) ^1.4.15 -> ^1.5.5 age confidence dependencies patch
@types/mocha (source) ^10.0.1 -> ^10.0.10 age confidence devDependencies patch
@types/semver (source) ^7.3.13 -> ^7.7.1 age confidence devDependencies patch
@types/vscode (source) ^1.82.0 -> ^1.105.0 age confidence devDependencies patch
@types/yargs (source) ^17.0.33 -> ^17.0.34 age confidence devDependencies patch
@vscode/vsce (source) 2.30.0 -> 2.32.0 age confidence devDependencies minor
alpinejs (source) ^3.15.0 -> ^3.15.1 age confidence dependencies patch
canvas-confetti ^1.9.3 -> ^1.9.4 age confidence dependencies patch
chokidar ^4.0.1 -> ^4.0.3 age confidence dependencies patch
eslint (source) ^9.38.0 -> ^9.39.1 age confidence devDependencies minor
fast-glob ^3.2.12 -> ^3.3.3 age confidence dependencies patch
fast-xml-parser ^5.3.0 -> ^5.3.1 age confidence dependencies patch
mocha (source) ^10.2.0 -> ^10.8.2 age confidence devDependencies patch
sass ^1.93.2 -> ^1.93.3 age confidence dependencies patch
semver ^7.3.8 -> ^7.7.3 age confidence dependencies patch
shiki (source) ^3.13.0 -> ^3.15.0 age confidence dependencies minor
sitemap ^8.0.0 -> ^8.0.2 age confidence dependencies patch
solid-js (source) ^1.9.9 -> ^1.9.10 age confidence dependencies patch
svelte (source) ^4.2.10 -> ^4.2.20 age confidence dependencies patch
svelte (source) ^5.41.3 -> ^5.43.3 age confidence dependencies patch 5.43.5 (+1)
tinyexec ^1.0.1 -> ^1.0.2 age confidence dependencies patch
turbo (source) ^2.5.8 -> ^2.6.0 age confidence devDependencies minor
typescript-eslint (source) ^8.46.2 -> ^8.46.3 age confidence devDependencies patch
vite (source) ^6.4.0 -> ^6.4.1 age confidence devDependencies patch
vscode ^1.90.0 -> ^1.999.0 age confidence engines minor
vscode-html-languageservice ^5.5.2 -> ^5.6.0 age confidence dependencies patch
vscode-languageserver-textdocument (source) ^1.0.11 -> ^1.0.12 age confidence dependencies patch
vscode-languageserver-textdocument (source) ^1.0.11 -> ^1.0.12 age confidence devDependencies patch
vscode-tmgrammar-test ^0.1.2 -> ^0.1.3 age confidence devDependencies patch
vscode-uri ^3.0.8 -> ^3.1.0 age confidence devDependencies patch
vue (source) ^3.5.22 -> ^3.5.23 age confidence dependencies patch 3.5.24
yaml (source) ^2.5.0 -> ^2.8.1 age confidence dependencies patch

Release Notes

Microsoft/vsce (@​vscode/vsce)

v2.32.0

Compare Source

Changes:
  • #​1034: Revert "Update deprecated dependencies"
  • #​1032: fix: probabilistic trigger v8 crash
  • #​1028: Remove need-more-info-closer workflow

This list of changes was auto generated.

v2.31.1

Compare Source

Changes:
  • #​1027: Update deprecated dependencies
  • #​1025: Don't package default readme if a path is provided and default is ignored
  • #​1024: add executes code property

This list of changes was auto generated.

v2.31.0

Compare Source

Changes:
  • #​1022: Throw error if provided readmePath or provided changelogPath could not be found
  • #​1020: Throw when unused files pattern in package.json
  • #​1015: Support "ls --tree"

This list of changes was auto generated.

alpinejs/alpine (alpinejs)

v3.15.1

Compare Source

Changed

  • x-sort improvements
  • CSP build allowGlobals now defaults to false instead of true
eslint/eslint (eslint)

v9.39.1

Compare Source

v9.39.0

Compare Source

NaturalIntelligence/fast-xml-parser (fast-xml-parser)

v5.3.1

Compare Source

sass/dart-sass (sass)

v1.93.3

Compare Source

  • Fix a performance regression that was introduced in 1.92.0.
shikijs/shiki (shiki)

v3.15.0

Compare Source

   🚀 Features
   🐞 Bug Fixes
    View changes on GitHub

v3.14.0

Compare Source

   🚀 Features
   🐞 Bug Fixes
    View changes on GitHub
ekalinin/sitemap.js (sitemap)

v8.0.2

Compare Source

Bug Fixes
  • fix #​464: Support xsi:schemaLocation in custom namespaces - thanks @​dzakki
    • Extended custom namespace validation to accept namespace-qualified attributes (like xsi:schemaLocation) in addition to xmlns declarations
    • The validation regex now matches both xmlns:prefix="uri" and prefix:attribute="value" patterns
    • Enables proper W3C schema validation while maintaining security validation for malicious content
    • Added comprehensive tests including security regression tests
Example Usage

The following now works correctly (as documented in README):

const sms = new SitemapStream({
  xmlns: {
    custom: [
      'xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"',
      'xsi:schemaLocation="http://www.sitemaps.org/schemas/sitemap/0.9 http://www.sitemaps.org/schemas/sitemap/0.9/sitemap.xsd"'
    ]
  }
});
Testing
  • ✅ All existing tests passing
  • ✅ 8 new tests added covering positive and security scenarios
  • ✅ 100% backward compatible with 8.0.1
Files Changed

2 files changed: 144 insertions, 5 deletions

sveltejs/svelte (svelte)

v5.43.3

Compare Source

Patch Changes
  • fix: ensure fork always accesses correct values (#​17098)

  • fix: change title only after any pending work has completed (#​17061)

  • fix: preserve symbols when creating derived rest properties (#​17096)

tinylibs/tinyexec (tinyexec)

v1.0.2

Compare Source

What's Changed

New Contributors

Full Changelog: tinylibs/tinyexec@1.0.1...1.0.2

vercel/turborepo (turbo)

v2.6.0: Turborepo v2.6.0

Compare Source

What's Changed

Docs
create-turbo
eslint
Examples
Changelog

New Contributors

Full Changelog: vercel/turborepo@v2.5.8...v2.6.0

typescript-eslint/typescript-eslint (typescript-eslint)

v8.46.3

Compare Source

This was a version bump only for typescript-eslint to align it with other projects, there were no code changes.

You can read about our versioning strategy and releases on our website.

microsoft/vscode (vscode)

v1.999.0

Compare Source

v1.105.1: September 2025 Recovery 1

Compare Source

The update addresses these issues.

For the complete release notes go to Updates on code.visualstudio.com.

v1.105.0: September 2025

Compare Source

Welcome to the September 2025 release of Visual Studio Code. There are many updates in this version that we hope you'll like, some of the key highlights include:

OS integration Developer productivity Agent tools
Get notified about task completion and chat responses
Show more
Resolve merge conflicts with AI assistance
Show more
Install MCP servers from the MCP marketplace
Show more
Native authentication experience on macOS
Show more
Pick up where you left off with the recent chats
Show more
Use fully-qualified tool names to avoid conflicts
Show more

v1.104.3: August 2025 Recovery 3

Compare Source

The update addresses these issues.

v1.104.2: August 2025 Recovery 2

Compare Source

The update addresses these issues.

v1.104.1: August 2025 Recovery 1

Compare Source

The update addresses these issues.

v1.104.0: August 2025

Compare Source

Welcome to the August 2025 release of Visual Studio Code. There are many updates in this version that we hope you'll like, some of the key highlights include:

Model flexibility Security Productivity
Let VS Code select the best model
Show more
Confirm edits for sensitive files
Show more
Remove distractions from chat file edits
Show more
Contribute models through VS Code extensions
Show more
Let agents run terminal commands safely
Show more
Use AGENTS.md to add chat context
Show more

v1.103.2: July 2025 Recovery 2

Compare Source

The update addresses these issues.

v1.103.1: July 2025 Recovery 1

Compare Source

The update adds GPT-5 prompt improvements, support for GPT-5 mini, and addresses these issues.

v1.103.0: July 2025

Compare Source


Welcome to the July 2025 release of Visual Studio Code. There are many updates in this version that we hope you'll like, some of the key highlights include:

MCP Chat Productivity
Revamped tool picker experience
Show more
Use GPT-5 in VS Code
Show more
Check out multiple branches simultaneously with Git worktrees
Show more
Enable more than 128 tools per agent request
Show more
Restore to a previous good state with chat checkpoints
Show more
Manage coding agent sessions in a dedicated view
Show more

v1.102.3: June 2025 Recovery 3

Compare Source

The update addresses these issues.

For the complete release notes go to Updates on code.visualstudio.com.

v1.102.2: June 2025 Recovery 2

Compare Source

The update addresses these issues.

For the complete release notes go to Updates on code.visualstudio.com.

v1.102.1: June 2025 Recovery 1

Compare Source

The update addresses these issues.

For the complete release notes go to Updates on code.visualstudio.com.

v1.102.0: June 2025

Compare Source

Welcome to the June 2025 release of Visual Studio Code. There are many updates in this version that we hope you'll like, some of the key highlights include:

Chat

  • Explore and contribute to the open sourced GitHub Copilot Chat extension (Read our blog post).
  • Generate custom instructions that reflect your project's conventions (Show more).
  • Use custom modes to tailor chat for tasks like planning or research (Show more).
  • Automatically approve selected terminal commands (Show more).
  • Edit and resubmit previous chat requests (Show more).

MCP

  • MCP support is now generally available in VS Code (Show more).
  • Easily install and manage MCP servers with the MCP view and gallery (Show more).
  • MCP servers as first-class resources in profiles and Settings Sync (Show more).

Editor experience

  • Delegate tasks to Copilot coding agent and let it handle them in the background (Show more).
  • Scroll the editor on middle click (Show more).
    If you'd like to read these release notes online, go to Updates on code.visualstudio.com. Insiders: Want to try new features as soon as possible? You can download the nightly Insiders build and try the latest updates as soon as they are available.

v1.101.2: May 2025 Recovery 2

Compare Source

The update addresses these issues.

For the complete release notes go to Updates on code.visualstudio.com.

v1.101.1: May 2025 Recovery 1

Compare Source

The update addresses these issues.

For the complete release notes go to Updates on code.visualstudio.com.

v1.101.0: May 2025

Compare Source

Welcome to the May 2025 release of Visual Studio Code. There are many updates in this version that we hope you'll like, some of the key highlights include:

MCP

  • Expand your agent coding flow with support for prompts, resources, and sampling (Show more).
  • Access MCP servers that require authentication (Show more).
  • Debug MCP servers with development mode (Show more).
  • Publish MCP servers from an extension (Show more).

Chat

  • Group and manage related tools by combining them in a tool set (Show more).

Source Control

  • View files in Source Control Graph view (Show more).
  • Assign and track work for GitHub Copilot Coding Agent from within VS Code (Show more).

If you'd like to read these release notes online, go to Updates on code.visualstudio.com.

Want to try new features as soon as possible? You can download the nightly Insiders build and try the latest updates as soon as they are available.

v1.100.3: April 2025 Recovery 3

Compare Source

The update addresses these issues, including a fix for a security vulnerability.

For the complete release notes go to Updates on code.visualstudio.com.

v1.100.2: April 2025 Recovery 2

Compare Source

The update addresses these issues, including a fix for a security vulnerability.

For the complete release notes go to Updates on code.visualstudio.com.

v1.100.1: April 2025 Recovery 1

Compare Source

The update addresses these issues, including a fix for a security vulnerability.

For the complete release notes go to Updates on code.visualstudio.com.

v1.100.0: April 2025

Compare Source

Welcome to the April 2025 release of Visual Studio Code. There are many updates in this version that we hope you'll like, some of the key highlights include:

  • Chat

    • Custom instructions and reusable prompts (more...).
    • Smarter results with tools for GitHub, extensions, and notebooks (more...).
    • Image and Streamable HTTP support for MCP (more...).
  • Chat performance

    • Faster responses on repeat chat requests (more...).
    • Faster edits in agent mode (more...).
  • Editor experience

    • Improved multi-window support for chat and editors (more...).
    • Staged changes now easier to identify (more...).

For the complete release notes go to Updates on code.visualstudio.com.

Insiders: Want to try new features as soon as possible? You can download the nightly Insiders build and try the latest updates as soon as they are available.

v1.99.3: March 2025 Recovery 3

Compare Source

The update addresses these issues.

For the complete release notes go to Updates on code.visualstudio.com.

v1.99.2: March 2025 Recovery 2

Compare Source

The update addresses these issues.

For the complete release notes go to Updates on code.visualstudio.com.

v1.99.1: March 2025 Recovery 1

Compare Source

The update has a fix for the security vulnerability in this issue.

For the complete release notes go to Updates on code.visualstudio.com.

v1.99.0: March 2025

Compare Source

Welcome to the March 2025 release of Visual Studio Code. There are many updates in


Configuration

📅 Schedule: Branch creation - Between 12:00 AM and 03:59 AM, only on Monday ( * 0-3 * * 1 ) (UTC), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.


  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

withastro/starlight

Description

Add the plugin starlight-page-actions to the plugin list

withastro/starlight

This PR is auto-generated by a GitHub action to update the file icons and file tree definitions available in Starlight.


Last fetched:  |  Scheduled refresh: Every Saturday

See Customizing GitHub Activity Pages to configure your own

Inspired by prs.atinux.com