AstroEco is Contributing…
Display your GitHub pull requests using astro-loader-github-prs
updated
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
-
#14712
91780cfThanks @florian-lefebvre! - Fixes a case where build'sprocess.envwould be inlined in the server output -
#14713
666d5a7Thanks @florian-lefebvre! - Improves fallbacks generation when using the experimental Fonts API
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
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
-
#14446
ece667aThanks @florian-lefebvre! - RemovesentryPointsonastro:build:ssrhook (Integration API) - (v6 upgrade guidance) -
#14426
861b9ccThanks @florian-lefebvre! - Removes the deprecatedemitESMImage()function - (v6 upgrade guidance) -
#14446
ece667aThanks @florian-lefebvre! - Removesroutesonastro:build:donehook (Integration API) - (v6 upgrade guidance) -
#14462
9fdfd4cThanks @florian-lefebvre! - Removes the oldapp.render()signature (Adapter API) - (v6 upgrade guidance) -
#14462
9fdfd4cThanks @florian-lefebvre! - Removesprefetch()withoption - (v6 upgrade guidance) -
#14432
b1d87ecThanks @florian-lefebvre! - DeprecatesAstroingetStaticPaths()- (v6 upgrade guidance) -
#14457
049da87Thanks @florian-lefebvre! - Updates trailing slash behavior of endpoint URLs - (v6 upgrade guidance) -
#14494
727b0a2Thanks @florian-lefebvre! - Updates Markdown heading ID generation - (v6 upgrade guidance) -
#14461
55a1a91Thanks @florian-lefebvre! - Deprecatesimport.meta.env.ASSETS_PREFIX- (v6 upgrade guidance) -
#14586
669ca5bThanks @ocavue! - Changes the values allowed inparamsreturned bygetStaticPaths()- (v6 upgrade guidance) -
#14421
df6d2d7Thanks @florian-lefebvre! - Removes the previously deprecatedAstro.glob()- (v6 upgrade guidance) -
#14462
9fdfd4cThanks @florian-lefebvre! - Removes thehandleFormsprop for the<ClientRouter />component - (v6 upgrade guidance) -
#14427
e131261Thanks @florian-lefebvre! - Increases minimum Node.js version to 22.12.0 - (v6 upgrade guidance) -
#14400
c69c7deThanks @ellielok! - Removes the deprecated<ViewTransitions />component - (v6 upgrade guidance) -
#14406
4f11510Thanks @florian-lefebvre! - Changes the default routing configuration value ofi18n.routing.redirectToDefaultLocalefromtruetofalse- (v6 upgrade guidance) -
#14477
25fe093Thanks @florian-lefebvre! - Removesrewrite()from Actions context - (v6 upgrade guidance) -
#14445
ecb0b98Thanks @florian-lefebvre! - Astro v6.0 upgrades to Vite v7.0 as the development server and production bundler - (v6 upgrade guidance) -
#14485
6f67c6eThanks @florian-lefebvre! - Updatesimport.meta.envvalues to always be inlined - (v6 upgrade guidance) -
#14480
36a461bThanks @florian-lefebvre! - Updates<script>and<style>tags to render in the order they are defined - (v6 upgrade guidance) -
#14407
3bda3ceThanks @ascorbic! - Removes legacy content collection support - (v6 upgrade guidance)
Minor Changes
-
#14550
9c282b5Thanks @ascorbic! - Adds support for live content collectionsLive 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()andgetCollection(). 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.tsfile (alongside yoursrc/content.config.tsif you have one) to define your live collections with a live content loader using the newdefineLiveCollection()function from theastro:contentmodule: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()andgetLiveEntry()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.liveContentCollectionsflag from yourastro.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
- #14427
e131261Thanks @florian-lefebvre! - Increases minimum Node.js version to 22.12.0 - (v6 upgrade guidance)
create-astro@5.0.0-alpha.0
Major Changes
- #14427
e131261Thanks @florian-lefebvre! - Increases minimum Node.js version to 22.12.0 - (v6 upgrade guidance)
@astrojs/cloudflare@13.0.0-alpha.0
Major Changes
- #14445
ecb0b98Thanks @florian-lefebvre! - Astro v6.0 upgrades to Vite v7.0 as the development server and production bundler - (v6 upgrade guidance)
Patch Changes
- Updated dependencies [
ece667a,861b9cc,ece667a,9fdfd4c,9fdfd4c,b1d87ec,049da87,727b0a2,55a1a91,669ca5b,df6d2d7,9fdfd4c,e131261,c69c7de,4f11510,25fe093,9c282b5,ecb0b98,6f67c6e,36a461b,3bda3ce]:- astro@6.0.0-alpha.0
- @astrojs/underscore-redirects@1.0.0
@astrojs/mdx@5.0.0-alpha.0
Major Changes
-
#14494
727b0a2Thanks @florian-lefebvre! - Updates Markdown heading ID generation - (v6 upgrade guidance) -
#14427
e131261Thanks @florian-lefebvre! - Increases minimum Node.js version to 22.12.0 - (v6 upgrade guidance) -
#14445
ecb0b98Thanks @florian-lefebvre! - Astro v6.0 upgrades to Vite v7.0 as the development server and production bundler - (v6 upgrade guidance)
Patch Changes
- Updated dependencies [
ece667a,861b9cc,ece667a,9fdfd4c,9fdfd4c,b1d87ec,049da87,727b0a2,55a1a91,669ca5b,df6d2d7,9fdfd4c,e131261,c69c7de,4f11510,25fe093,9c282b5,ecb0b98,6f67c6e,36a461b,3bda3ce]:- astro@6.0.0-alpha.0
- @astrojs/markdown-remark@7.0.0-alpha.0
@astrojs/netlify@7.0.0-alpha.0
Major Changes
- #14445
ecb0b98Thanks @florian-lefebvre! - Astro v6.0 upgrades to Vite v7.0 as the development server and production bundler - (v6 upgrade guidance)
Patch Changes
- Updated dependencies [
ece667a,861b9cc,ece667a,9fdfd4c,9fdfd4c,b1d87ec,049da87,727b0a2,55a1a91,669ca5b,df6d2d7,9fdfd4c,e131261,c69c7de,4f11510,25fe093,9c282b5,ecb0b98,6f67c6e,36a461b,3bda3ce]:- astro@6.0.0-alpha.0
- @astrojs/underscore-redirects@1.0.0
@astrojs/preact@5.0.0-alpha.0
Major Changes
-
#14427
e131261Thanks @florian-lefebvre! - Increases minimum Node.js version to 22.12.0 - (v6 upgrade guidance) -
#14445
ecb0b98Thanks @florian-lefebvre! - Astro v6.0 upgrades to Vite v7.0 as the development server and production bundler - (v6 upgrade guidance)
@astrojs/react@5.0.0-alpha.0
Major Changes
-
#14427
e131261Thanks @florian-lefebvre! - Increases minimum Node.js version to 22.12.0 - (v6 upgrade guidance) -
#14445
ecb0b98Thanks @florian-lefebvre! - Astro v6.0 upgrades to Vite v7.0 as the development server and production bundler - (v6 upgrade guidance)
@astrojs/solid-js@6.0.0-alpha.0
Major Changes
-
#14427
e131261Thanks @florian-lefebvre! - Increases minimum Node.js version to 22.12.0 - (v6 upgrade guidance) -
#14445
ecb0b98Thanks @florian-lefebvre! - Astro v6.0 upgrades to Vite v7.0 as the development server and production bundler - (v6 upgrade guidance)
@astrojs/svelte@8.0.0-alpha.0
Major Changes
-
#14427
e131261Thanks @florian-lefebvre! - Increases minimum Node.js version to 22.12.0 - (v6 upgrade guidance) -
#14445
ecb0b98Thanks @florian-lefebvre! - Astro v6.0 upgrades to Vite v7.0 as the development server and production bundler - (v6 upgrade guidance)
Patch Changes
- Updated dependencies [
ece667a,861b9cc,ece667a,9fdfd4c,9fdfd4c,b1d87ec,049da87,727b0a2,55a1a91,669ca5b,df6d2d7,9fdfd4c,e131261,c69c7de,4f11510,25fe093,9c282b5,ecb0b98,6f67c6e,36a461b,3bda3ce]:- astro@6.0.0-alpha.0
@astrojs/vue@6.0.0-alpha.0
Major Changes
- #14445
ecb0b98Thanks @florian-lefebvre! - Astro v6.0 upgrades to Vite v7.0 as the development server and production bundler - (v6 upgrade guidance)
Patch Changes
- Updated dependencies [
ece667a,861b9cc,ece667a,9fdfd4c,9fdfd4c,b1d87ec,049da87,727b0a2,55a1a91,669ca5b,df6d2d7,9fdfd4c,e131261,c69c7de,4f11510,25fe093,9c282b5,ecb0b98,6f67c6e,36a461b,3bda3ce]:- astro@6.0.0-alpha.0
@astrojs/markdown-remark@7.0.0-alpha.0
Major Changes
- #14494
727b0a2Thanks @florian-lefebvre! - Updates Markdown heading ID generation - (v6 upgrade guidance)
Patch Changes
- Updated dependencies [
e131261]:- @astrojs/prism@4.0.0-alpha.0
@astrojs/db@0.19.0-alpha.0
Minor Changes
- #14445
ecb0b98Thanks @florian-lefebvre! - Astro v6.0 upgrades to Vite v7.0 as the development server and production bundler - (v6 upgrade guidance)
@astrojs/alpinejs@0.5.0-alpha.0
Minor Changes
- #14445
ecb0b98Thanks @florian-lefebvre! - Astro v6.0 upgrades to Vite v7.0 as the development server and production bundler - (v6 upgrade guidance)
@astrojs/markdoc@1.0.0-alpha.0
Minor Changes
-
#14494
727b0a2Thanks @florian-lefebvre! - Updates Markdown heading ID generation - (v6 upgrade guidance) -
#14427
e131261Thanks @florian-lefebvre! - Increases minimum Node.js version to 22.12.0 - (v6 upgrade guidance) -
#14445
ecb0b98Thanks @florian-lefebvre! - Astro v6.0 upgrades to Vite v7.0 as the development server and production bundler - (v6 upgrade guidance)
Patch Changes
- Updated dependencies [
ece667a,861b9cc,ece667a,9fdfd4c,9fdfd4c,b1d87ec,049da87,727b0a2,55a1a91,669ca5b,df6d2d7,9fdfd4c,e131261,c69c7de,4f11510,25fe093,9c282b5,ecb0b98,6f67c6e,36a461b,3bda3ce]:- astro@6.0.0-alpha.0
- @astrojs/markdown-remark@7.0.0-alpha.0
- @astrojs/prism@4.0.0-alpha.0
@astrojs/upgrade@0.7.0-alpha.0
Minor Changes
- #14427
e131261Thanks @florian-lefebvre! - Increases minimum Node.js version to 22.12.0 - (v6 upgrade guidance)
@astrojs/node@10.0.0-alpha.0
Patch Changes
- Updated dependencies [
ece667a,861b9cc,ece667a,9fdfd4c,9fdfd4c,b1d87ec,049da87,727b0a2,55a1a91,669ca5b,df6d2d7,9fdfd4c,e131261,c69c7de,4f11510,25fe093,9c282b5,ecb0b98,6f67c6e,36a461b,3bda3ce]:- astro@6.0.0-alpha.0
@astrojs/vercel@10.0.0-alpha.0
Patch Changes
- Updated dependencies [
ece667a,861b9cc,ece667a,9fdfd4c,9fdfd4c,b1d87ec,049da87,727b0a2,55a1a91,669ca5b,df6d2d7,9fdfd4c,e131261,c69c7de,4f11510,25fe093,9c282b5,ecb0b98,6f67c6e,36a461b,3bda3ce]:- astro@6.0.0-alpha.0
@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
- #14421
df6d2d7Thanks @florian-lefebvre! - Removes the previously deprecatedAstro.glob()- (v6 upgrade guidance)
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 |
|---|---|
![]() |
![]() |
This also has the added benefit of running our E2E tests on a different browser.
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
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
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
Changes
Since the branch is in pre-mode, I think that's all we need?
Testing
N/A
Docs
N/A
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
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
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.
This PR fixes various typos I spotted in the project.
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.
Changes
- See withastro/roadmap#1039 (comment)
- Updates implementation based on capsize instead of fontaine
Testing
Should pass, manual
Docs
Changeset
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:envVite plugin had some caching logic that retained the dev behavior in build, resulting in inliningprocess.envin the build output in some cases - This PR refactors this Vite plugin to avoid this situation
Testing
Manual, should pass
Docs
Changeset
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 🙌
This PR fixes a few typos I spotted in the project.
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.
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
changesjob output it looks like it should have run.
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% | ![]() |
![]() |
| 100% | ![]() |
![]() |
I'm not sure if this PR warrants a minor version bump or not, let me know if it does.
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:
And skipped on Windows:
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
- #3511
8727df1Thanks @astrobot-houston! - Updates theseti:gitlabicon to match latest version from Seti UI Icons
This PR contains the following updates:
Release Notes
withastro/astro (@astrojs/solid-js)
v5.1.2
Patch Changes
- #14621
e3175d9Thanks @GameRoMan! - Updatesviteversion to fix CVE
withastro/astro (@astrojs/svelte)
v7.2.1
Patch Changes
- #14621
e3175d9Thanks @GameRoMan! - Updatesviteversion to fix CVE
withastro/astro (@astrojs/vue)
v5.1.2
Patch Changes
- #14621
e3175d9Thanks @GameRoMan! - Updatesviteversion to fix CVE
vercel/vercel (@vercel/routing-utils)
v5.2.1
Patch Changes
- Add experimental support for routes.json (#14138)
sveltejs/svelte (svelte)
v5.43.2
Patch Changes
- fix: treat each blocks with async dependencies as uncontrolled (#17077)
v5.43.1
Patch Changes
- fix: transform
$bindableafterawaitexpressions (#17066)
v5.43.0
Minor Changes
- feat: out-of-order rendering (#17038)
Patch Changes
- fix: settle batch after DOM updates (#17054)
v5.42.3
Patch Changes
-
fix: handle
<svelte:head>rendered asynchronously (#17052) -
fix: don't restore batch in
#await(#17051)
v5.42.2
Patch Changes
-
fix: better error message for global variable assignments (#17036)
-
chore: tweak memoizer logic (#17042)
v5.42.1
Patch Changes
- fix: ignore fork
discard()aftercommit()(#17034)
v5.42.0
Minor Changes
- feat: experimental
forkAPI (#17004)
Patch Changes
cloudflare/workers-sdk (wrangler)
v4.45.3
Patch Changes
-
#11117
6822aafThanks @emily-shen! - fix: show local/remote status before D1 command confirmationsD1 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
bce8142Thanks @petebacondarwin! - Ensure that process.env is case-insensitive on WindowsThe object that holds the environment variables in
process.envdoes not care about the case of its keys
in Windows. For example,process.env.SystemRootandprocess.env.SYSTEMROOTwill refer to the same value.Previously, when merging fields from
.envfiles 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
-
#11097
55657ebThanks @penalosa! - Extract internal APIs into a new@cloudflare/workers-utilspackage -
#11118
d47f166Thanks @zebp! - Fix validation of thepersistfield of observabilitylogsandtracesconfiguration
v4.45.1
Patch Changes
-
#10959
d0208feThanks @devin-ai-integration! - Fixed conflict between--envand--expiresflags inwrangler r2 object put.--enow aliases--envonly, and NOT--expires. -
#10915
dbe51c1Thanks @devin-ai-integration! - Fixed self-bindings (service bindings to the same worker) showing as [not connected] in wrangler dev. Self-bindings now correctly show as [connected] since a worker is always available to itself. -
#10913
d4f2dafThanks @devin-ai-integration! - Fixed duplicate warning messages appearing during wrangler dev when configuration changes or state transitions occur
v4.45.0
Minor Changes
-
#11030
1a8088aThanks @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-provisionflag. It currently works for R2, D1, and KV bindings.To use this feature, add a binding to your config file without a resource ID:
wrangler devwill automatically create these resources for you locally, and when you next runwrangler deployWrangler 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
4bd4c29Thanks @danielrs! - Better Wrangler subdomain defaults warning.Improves the warnings that we show users when either
worker_devorpreview_urlsare missing. -
#10927
31e1330Thanks @dom96! - Implementspython_modules.excludeswrangler config field[python_modules] excludes = ["**/*.pyc", "**/__pycache__"]
-
#10741
2f57345Thanks @penalosa! - Remove obsolete--x-remote-bindingsflag -
Updated dependencies [
ca6c010]:- miniflare@4.20251011.1
v4.44.0
Minor Changes
-
#10939
d4b4c90Thanks @danielrs! - Configpreview_urlsdefaults toworkers_devvalue.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
trueorfalse, we
default to the resolved value of config.workers_dev. Should result in a
clearer user experience. -
#11027
1a2bbf8Thanks @jamesopstad! - Statically replace the value ofprocess.env.NODE_ENVwithdevelopmentfor development builds andproductionfor production builds if it is not set. Else, use the given value. This ensures that libraries, such as React, that branch code based onprocess.env.NODE_ENVcan be properly tree shaken. -
#9705
0ee1a68Thanks @hiendv! - Add params type to Workflow type generation. E.g.interface Env { MY_WORKFLOW: Workflow< Parameters<import("./src/index").MyWorkflow["run"]>[0]["payload"] >; }
-
#10867
dd5f769Thanks @austin-mc! - Add media binding support
Patch Changes
-
#11018
5124818Thanks @dario-piotrowicz! - Improve potential errors thrown bystartRemoteProxySessionby including more information -
#11019
6643bd4Thanks @dario-piotrowicz! - Fixobservability.logs.persistbeing flagged as an unexpected field during the wrangler config file validation -
#10768
8211bc9Thanks @dario-piotrowicz! - Update logs handling to use the newhandleStructuredLogsminiflare option -
#10997
3bb034fThanks @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
43503c7Thanks @emily-shen! - fix: cleanup any running containers again on wrangler dev exit -
#11000
a6de9dbThanks @jonboulle! - always load container image into local store during buildBuildKit supports different build drivers. When using the more modern
docker-containerdriver (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 callinggetImageRepoTags), 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 imageExplicitly setting the
--loadflag (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
d39c8b5Thanks @pombosilva! - Make Workflows instances list command cursor based -
#10892
7d0417bThanks @dario-piotrowicz! - improve the diffing representation forwrangler deploy(run under--x-remote-diff-check) -
Updated dependencies [
36d7054,dd5f769,ee7d710,8211bc9]:- miniflare@4.20251011.0
- @cloudflare/unenv-preset@2.7.8
v4.43.0
Minor Changes
- #10911
940b44dThanks @devin-ai-integration! - feat:wrangler init --from-dashnow generateswrangler.jsoncconfig files instead ofwrangler.tomlfiles
Patch Changes
-
#10938
e52d0ecThanks @penalosa! - Acquire Cloudflare Access tokens for additional requests made during awrangler dev --remotesession -
#10923
2429533Thanks @emily-shen! - fix: updatedocker manifest inspectto use full image registry uri when checking if the image exists remotely -
#10521
88b5b7fThanks @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_namefrom the config file on upload - Fixing bindings view for specific versions to not display TOML
v4.42.2
Patch Changes
-
#10881
ce832d5Thanks @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
d0ab919Thanks @lrapoport-cf! - Clarify thatwrangler check startupgenerates a local CPU profile -
Updated dependencies [
42e256f,4462bc1]:- miniflare@4.20251008.0
v4.42.1
Patch Changes
-
#10865
26adce7Thanks @WillTaylorDev! - Respect keep_vars for wrangler versions upload. -
#10833
196ccbfThanks @cmackenzie1! - Validate Pipeline entity names in Wrangler config before sending to the API. -
#10856
1334102Thanks @anonrig! - Removes unnecessary calls to "node:os" -
Updated dependencies [
51f9dc1,f29b0b0,1334102]:- miniflare@4.20251004.0
- @cloudflare/unenv-preset@2.7.7
v4.42.0
Minor Changes
- #10735
103fbf0Thanks @petebacondarwin! - Allow WRANGLER_SEND_ERROR_REPORTS env var to override whether to report Wrangler crashes to Sentry
Patch Changes
-
#10757
59d5911Thanks @dario-piotrowicz! - fixconsole.debuglogs not being logged at theinfolevel (as users expect) -
Updated dependencies [
2594130]:- @cloudflare/unenv-preset@2.7.6
v4.41.0
Minor Changes
-
#10507
21a0befThanks @dario-piotrowicz! - Add strict mode for thewrangler deploycommandAdd a new flag:
--strictthat makes thewrangler deploycommand 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
7f2386eThanks @penalosa! - Add prompt to resource creation flow allowing for newly created resources to be remote.
Patch Changes
-
#10822
4c06766Thanks @edmundhung! - fix: skip banner when using--jsonflag inwrangler pages deploymentcommands -
#10838
d3aee31Thanks @edmundhung! - fix: skip banner when using--jsonflag inwrangler queues subscriptioncommands -
#10829
59e8ef0Thanks @edmundhung! - fix: skip banner when using--jsonflag inwrangler pipelinescommands -
#10764
79a6b7dThanks @emily-shen! - containers: defaultmax_instancesto 20 instead of 1. -
#10844
7a4d0daThanks @mikenomitch! - Adds new Container instance types, and renamedevtoliteandstandardtostandard-1. The new instance_types are now:Instance Type vCPU Memory Disk lite (previously dev) 1/16 256 MiB 2 GB basic 1/4 1 GiB 4 GB standard-1 (previously standard) 1/2 4 GiB 8 GB standard-2 1 6 GiB 12 GB standard-3 2 8 GiB 16 GB standard-4 4 12 GiB 20 GB -
#10634
62656bdThanks @emily-shen! - fix: error if the container image uri has an account id that doesn't match the current account -
#10761
886e577Thanks @petebacondarwin! - switch zone route warning to an info message -
#10734
8d7f32eThanks @penalosa! - Improve formatting of logged errors in some cases -
#10832
f9d37dbThanks @petebacondarwin! - retry subdomain requests to be more resilient to flakes -
#10770
835d6f7Thanks @danielrs! - Enabling or disablingworkers_devis often an indication that
the user is also trying to enable or disablepreview_urls. Warn the
user when these enter mixed state. -
#10764
79a6b7dThanks @emily-shen! - fix: respect the log level set by wrangler when logging using @cloudflare/cli -
Updated dependencies [
c8d5282,bffd2a9]:- miniflare@4.20251001.0
v4.40.3
Patch Changes
-
#10602
ff82d80Thanks @tukiminya! - fix: update Secrets Store command status from alpha to open-beta -
#10623
7a6381cThanks @IRCody! - Handle more cases for correctly resolving the full uri for an image when using containers push. -
#10779
325d22eThanks @hoodmane! - Add fallthrough: true for python_modules data rule -
#10112
8d07576Thanks @devin-ai-integration! - fix: allow Workflow bindings when calling getPlatformProxy()Workflow bindings are not supported in practice when using
getPlatformProxy().
But their existence in a Wrangler config file should not prevent other bindings from working.
Previously, callinggetPlatformProxy()would crash if there were any Workflow bindings defined.
Now, instead, you get a warning telling you that these bindings are not available. -
#10769
0a554f9Thanks @penalosa! - Mark more errors asUserErrorto disable Sentry reporting -
#10679
6244a9eThanks @KianNH! - Fix rendering for nested objects incontainers listandcontainers info [ID] -
#10785
d09cab3Thanks @pombosilva! - Workflows names and instance IDs are now properly validated with production limits. -
Updated dependencies [
6ff41a6,0c208e1,2432022,d0801b1,0a554f9]:- miniflare@4.20250927.0
- @cloudflare/unenv-preset@2.7.5
v4.40.2
Patch Changes
- #10771
b455281Thanks @penalosa! - Fix Worker Loader binding type
v4.40.1
Patch Changes
- #10668
a57149fThanks @danielrs! - Support the deletion of secrets with complex names
v4.40.0
Minor Changes
- #10743
a7ac751Thanks @jonesphillip! - Changes--fileSizeMBto--file-sizeforwrangler r2 bucket catalogcompaction command.
Small fixes for pipelines commands.
Patch Changes
-
#10706
81fd733Thanks @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
Minor Changes
-
#10647
555a6daThanks @efalcao! - VPC service binding support -
#10612
97a72ccThanks @jonesphillip! - Added new pipelines commands (pipelines, streams, sinks, setup), moved old pipelines commands behind --legacy -
#10652
acd48edThanks @edmundhung! - Rename Hyperdrive local connection string environment variable fromWRANGLER_HYPERDRIVE_LOCAL_CONNECTION_STRING_<BINDING_NAME>toCLOUDFLARE_HYPERDRIVE_LOCAL_CONNECTION_STRING_<BINDING_NAME>. The old variable name is still supported but will now show a deprecation warning. -
#10721
55a10a3Thanks @penalosa! - Stabilise Worker Loader bindings
Patch Changes
-
#10724
b4a4311Thanks @penalosa! - Use Cap'n Web inworkers-sdk -
#10701
dc1d0d6Thanks @penalosa! - Fix hotkeys double render -
Updated dependencies [
555a6da,262393a,3ec1f65,a434352,328e687,b4a4311]:- miniflare@4.20250923.0
v4.38.0
Minor Changes
-
#10654
a4e2439Thanks @laplab! - Switch to WRANGLER_R2_SQL_AUTH_TOKEN env variable for R2 SQL secret. Update the response format for R2 SQL -
#10676
f76da43Thanks @penalosa! - Supportctx.exportsin wrangler types -
#10651
6caf938Thanks @edevil! - Added new attribute "allowed_sender_addresses" to send email binding.
Patch Changes
-
#10674
1cc258eThanks @penalosa! - Fix remote/local display for KV/D1/R2 & Browser bindings -
#10678
b30263eThanks @penalosa! - Remove dummy auth from SDK setup -
#10678
b30263eThanks @penalosa! - AddWRANGLER_TRACE_IDenvironment variable to support internal testing -
#10561
769ffb1Thanks @danielrs! - Do not show subdomain status mismatch warnings on first deploy. -
Updated dependencies [
b59e3e1,e9b0c66,6caf938,88132bc]:- miniflare@4.20250917.0
- @cloudflare/unenv-preset@2.7.4
v4.37.1
Patch Changes
-
#10658
3029b9aThanks @1000hz! - Fixed an issue with service tags not being applied properly to Workers when the Wrangler configuration file did not include a top-levelnameproperty. -
#10657
31ec996Thanks @penalosa! - Disable remote bindings with the--localflag -
Updated dependencies [
783afeb]:- miniflare@4.20250913.0
v4.37.0
Minor Changes
-
#10546
d53a0bcThanks @1000hz! - On deploy or version upload, Workers with multiple environments are tagged with metadata that groups them together in the Cloudflare Dashboard. -
#10596
735785eThanks @penalosa! - Add Miniflare & Wrangler support for unbound Durable Objects -
#10622
15c34e2Thanks @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
Minor Changes
-
#10604
135e066Thanks @penalosa! - Enable Remote Bindings without the need for the--x-remote-bindingsflag -
#10558
30f558eThanks @laplab! - Add commands to send queries and manage R2 SQL product. -
#10574
d8860acThanks @efalcao! - Add support for VPC services CRUD viawrangler vpc service -
#10119
336a75dThanks @dxh9845! - Add support for dynamically loading 'external' Miniflare plugins for unsafe Worker bindi
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.
This PR contains the following updates:
Release Notes
Microsoft/vsce (@vscode/vsce)
v2.32.0
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
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
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
Changed
x-sortimprovements- CSP build
allowGlobalsnow defaults tofalseinstead oftrue
shikijs/shiki (shiki)
v3.15.0
🚀 Features
- lang-ansi: Fallback for missing theme ANSI colors - by @Chanakyasinde and @antfu in #1095 (f36ea)
- transformers: Support
meta.indentfor indent guides - by @L33Z22L11 in #1087 (d8f89)
🐞 Bug Fixes
- Allow singleton highlighter recovery after invalid language error - by @Maxiemad in #1091 (218c9)
- vitepress-twoslash: Prevent popper show/hide on dragging - by @bluwy in #1090 (29522)
View changes on GitHub
v3.14.0
🚀 Features
🐞 Bug Fixes
- colorized-brackets: Fix default color does not work with colorized-brackets - by @oatmealproblem in #1082 (f4d3f)
View changes on GitHub
ekalinin/sitemap.js (sitemap)
v8.0.2
Bug Fixes
- fix #464: Support
xsi:schemaLocationin custom namespaces - thanks @dzakki- Extended custom namespace validation to accept namespace-qualified attributes (like
xsi:schemaLocation) in addition toxmlnsdeclarations - The validation regex now matches both
xmlns:prefix="uri"andprefix:attribute="value"patterns - Enables proper W3C schema validation while maintaining security validation for malicious content
- Added comprehensive tests including security regression tests
- Extended custom namespace validation to accept namespace-qualified attributes (like
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
tinylibs/tinyexec (tinyexec)
v1.0.2
What's Changed
- refactor: migrate to tsdown by @sxzz in #50
- feat: OIDC publish by @outslept in #52
- docs: clarify documentation by @outslept in #54
- chore: set engine constraint by @43081j in #56
- test: migrate to vitest by @43081j in #58
- fix: read stdout/stderr in parallel by @43081j in #59
New Contributors
- @sxzz made their first contribution in #50
- @outslept made their first contribution in #52
Full Changelog: tinylibs/tinyexec@1.0.1...1.0.2
vercel/turborepo (turbo)
v2.6.0: Turborepo v2.6.0
What's Changed
Docs
- docs: clarification on Transit Nodes docs by @maschwenk in #9181
- docs: add GitHub Actions reusable workflow documentation for remote caching by @anthonyshew in #10923
- docs: generate blog release OG images by @anthonyshew in #10936
- docs: fix correct package name from eslint-config-turbo to eslint-plugin-turbo by @tetzng in #10954
- docs: align tailwindcss 4 guide to the with-tailwind example by @esauri in #10963
- docs: fix typos and formatting issues in Playwright guide by @yamcodes in #10980
- docs: adjust compute hours saved component initial value by @anthonyshew in #10958
- docs: clarify passthrough args comparison by @emilbjorklund in #10990
- docs: fix profile images on home page by @anthonyshew in #10993
- feat: microfrontends by @anthonyshew in #10982
- docs: Clarify passtrhough args cache miss by @eug-vs in #11026
- fix: path validation in
microfrontends.jsonby @anthonyshew in #11006 - feat(microfrontends): schema.json for microfrontends.json by @anthonyshew in #11008
create-turbo
- feat: update
create-turboBun prompt text by @anthonyshew in #10918
eslint
- fix(eslint-config-turbo): use module.exports for ESLint v8 compatibility by @anthonyshew in #10902
- perf: ~8.6x faster ESLint rule by @anthonyshew in #10943
Examples
- Update package.json by @Satheeshsk369 in #10892
- docs: fix JSDoc type for ESLint config in basic example by @victor-code19 in #10727
- refactor(examples): enhance
with-nestjs(#8131) by @Neosoulink in #10964 - examples: Upgrade core-team-maintained examples to Next.js 16 by @anthonyshew in #11014
Changelog
- chore: remove missing turbow.js references by @pauloZion1 in #10893
- fix(turborepo-lockfiles): handle missing optional dependencies in Bun lockfiles by @anthonyshew in #10909
- fix: update
uisuggested value in error message for turbo.json by @hugomassing in #10896 - chore: remove unused
originfield from auth structs by @anthonyshew in #10910 - feat: new OAuth flow for Turborepo CLI with Vercel by @anthonyshew in #10911
- fix(lockfiles): include bundled dependencies in Bun lockfile subgraphs by @anthonyshew in #10915
- test: increase coverage for lockfiles by @anthonyshew in #10633
- fix: update remote cache OAuth refresh flow by @anthonyshew in #10916
- feat(tui): task list search with
/by @anthonyshew in #10908 - fix: --graph=foo.dot should not require graphviz installed by @blast-hardcheese in #10942
- chore: update devcontainer configuration by @anthonyshew in #10955
- fix:
injectWorkspacePackagesforturbo prunewith pnpm by @anthonyshew in #10945 - fix: adjust binary call for microfrontends proxy on Windows by @mknichel in #10962
- Add worktrees.json configuration to .cursor directory by @Copilot in #10986
- fix: windows symlinking bug by @anthonyshew in #10992
- fix: added Linux env vars to global passthroughs by @aviramha in #10984
- fix: recursive transitive closure analysis in npm lockfile parser by @anthonyshew in #10988
- ci(fix): dynamically set ports in proxy integration tests by @anthonyshew in #11009
- feat: Add support for custom microfrontends.json naming by @kitfoster in #11022
New Contributors
- @Satheeshsk369 made their first contribution in #10892
- @robobun made their first contribution in #10729
- @hugomassing made their first contribution in #10896
- @victor-code19 made their first contribution in #10727
- @blast-hardcheese made their first contribution in #10942
- @tetzng made their first contribution in #10954
- @esauri made their first contribution in #10963
- @Copilot made their first contribution in #10986
- @emilbjorklund made their first contribution in #10990
- @aviramha made their first contribution in #10984
- @eug-vs made their first contribution in #11026
- @kitfoster made their first contribution in #11022
Full Changelog: vercel/turborepo@v2.5.8...v2.6.0
typescript-eslint/typescript-eslint (typescript-eslint)
v8.46.3
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
v1.105.1: September 2025 Recovery 1
The update addresses these issues.
For the complete release notes go to Updates on code.visualstudio.com.
v1.105.0: September 2025
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
The update addresses these issues.
v1.104.2: August 2025 Recovery 2
The update addresses these issues.
v1.104.1: August 2025 Recovery 1
The update addresses these issues.
v1.104.0: August 2025
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
The update addresses these issues.
v1.103.1: July 2025 Recovery 1
The update adds GPT-5 prompt improvements, support for GPT-5 mini, and addresses these issues.
v1.103.0: July 2025
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
The update addresses these issues.
For the complete release notes go to Updates on code.visualstudio.com.
v1.102.2: June 2025 Recovery 2
The update addresses these issues.
For the complete release notes go to Updates on code.visualstudio.com.
v1.102.1: June 2025 Recovery 1
The update addresses these issues.
For the complete release notes go to Updates on code.visualstudio.com.
v1.102.0: June 2025
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
The update addresses these issues.
For the complete release notes go to Updates on code.visualstudio.com.
v1.101.1: May 2025 Recovery 1
The update addresses these issues.
For the complete release notes go to Updates on code.visualstudio.com.
v1.101.0: May 2025
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
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
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
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
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
-
Chat performance
-
Editor experience
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
The update addresses these issues.
For the complete release notes go to Updates on code.visualstudio.com.
v1.99.2: March 2025 Recovery 2
The update addresses these issues.
For the complete release notes go to Updates on code.visualstudio.com.
v1.99.1: March 2025 Recovery 1
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
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.
Description
Add the plugin starlight-page-actions to the plugin list
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






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