Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

chore(deps): update all non-major dependencies #130

Open
wants to merge 1 commit into
base: main
Choose a base branch
from
Open

chore(deps): update all non-major dependencies #130

wants to merge 1 commit into from
+536 −495

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Mar 3, 2025 •
edited
Loading

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
@types/node (source) 22.13.5 -> 22.13.9 age adoption passing confidence
astro (source) 5.2.5 -> 5.4.2 age adoption passing confidence
pnpm (source) 10.4.1 -> 10.6.0 age adoption passing confidence
tsup (source) 8.3.6 -> 8.4.0 age adoption passing confidence
turbo (source) 2.4.2 -> 2.4.4 age adoption passing confidence
typescript (source) 5.7.3 -> 5.8.2 age adoption passing confidence

Release Notes

withastro/astro (astro)

v5.4.2

Compare Source

Patch Changes

v5.4.1

Compare Source

Patch Changes

  • #​13336 8f632ef Thanks @​ematipico! - Fixes a regression where some asset utilities were move across monorepo, and not re-exported anymore.

  • #​13320 b5dabe9 Thanks @​{! - Adds support for typing experimental session data

    You can add optional types to your session data by creating a src/env.d.ts file in your project that extends the global App.SessionData interface. For example:

    declare namespace App {
  interface SessionData {

      id: string;
      email: string;
    };
    lastLogin: Date;
  }
}

    Any keys not defined in this interface will be treated as any.

    Then when you access Astro.session in your components, any defined keys will be typed correctly:

v5.4.0

Compare Source

Minor Changes
Config helpers

Two new helper functions exported from astro/config:

  • mergeConfig() allows users to merge partially defined Astro configurations on top of a base config while following the merge rules of updateConfig() available for integrations.
  • validateConfig() allows users to validate that a given value is a valid Astro configuration and fills in default values as necessary.

These helpers are particularly useful for integration authors and for developers writing scripts that need to manipulate Astro configurations programmatically.

Programmatic build

The build API now receives a second optional BuildOptions argument where users can specify:

  • devOutput (default false): output a development-based build similar to code transformed in astro dev.
  • teardownCompiler (default true): teardown the compiler WASM instance after build.

These options provide more control when running Astro builds programmatically, especially for testing scenarios or custom build pipelines.

  • #​13278 4a43c4b Thanks @​ematipico! - Adds a new configuration option server.allowedHosts and CLI option --allowed-hosts.

    Now you can specify the hostnames that the dev and preview servers are allowed to respond to. This is useful for allowing additional subdomains, or running the dev server in a web container.

    allowedHosts checks the Host header on HTTP requests from browsers and if it doesn't match, it will reject the request to prevent CSRF and XSS attacks.

    astro dev --allowed-hosts=foo.bar.example.com,bar.example.com
    astro preview --allowed-hosts=foo.bar.example.com,bar.example.com
    // astro.config.mjs
import { defineConfig } from 'astro/config';

export default defineConfig({
  server: {
    allowedHosts: ['foo.bar.example.com', 'bar.example.com'],
  },
});

    This feature is the same as Vite's server.allowHosts configuration.

  • #​13254 1e11f5e Thanks @​p0lyw0lf! - Adds the ability to process and optimize remote images in Markdown files

    Previously, Astro only allowed local images to be optimized when included using ![]() syntax in plain Markdown files. Astro's image service could only display remote images without any processing.

    Now, Astro's image service can also optimize remote images written in standard Markdown syntax. This allows you to enjoy the benefits of Astro's image processing when your images are stored externally, for example in a CMS or digital asset manager.

    No additional configuration is required to use this feature! Any existing remote images written in Markdown will now automatically be optimized. To opt-out of this processing, write your images in Markdown using the HTML <img> tag instead. Note that images located in your public/ folder are still never processed.

Patch Changes

  • #​13256 509fa67 Thanks @​p0lyw0lf! - Adds experimental responsive image support in Markdown

    Previously, the experimental.responsiveImages feature could only provide responsive images when using the <Image /> and <Picture /> components.

    Now, images written with the ![]() Markdown syntax in Markdown and MDX files will generate responsive images by default when using this experimental feature.

    To try this experimental feature, set experimental.responsiveImages to true in your astro.config.mjs file:

    {
   experimental: {
      responsiveImages: true,
   },
}

    Learn more about using this feature in the experimental responsive images feature reference.

    For a complete overview, and to give feedback on this experimental API, see the Responsive Images RFC.

  • #​13323 80926fa Thanks @​ematipico! - Updates esbuild and vite to the latest to avoid false positives audits warnings caused by esbuild.

  • #​13313 9e7c71d Thanks @​martrapp! - Fixes an issue where a form field named "attributes" shadows the form.attributes property.

  • #​12052 5be12b2 Thanks @​Fryuni! - Fixes incorrect config update when calling updateConfig from astro:build:setup hook.

    The function previously called a custom update config function made for merging an Astro config. Now it calls the appropriate mergeConfig() utility exported by Vite that updates functional options correctly.

  • #​13303 5f72a58 Thanks @​ematipico! - Fixes an issue where the dev server was applying second decoding of the URL of the incoming request, causing issues for certain URLs.

  • Updated dependencies [1e11f5e, 1e11f5e]:

v5.3.1

Compare Source

Patch Changes

  • #​13233 32fafeb Thanks @​joshmkennedy! - Ensures consistent behaviour of Astro.rewrite/ctx.rewrite when using base and trailingSlash options.

  • #​13003 ea79054 Thanks @​chaegumi! - Fixes a bug that caused the vite.base value to be ignored when running astro dev

  • #​13299 2e1321e Thanks @​bluwy! - Uses tinyglobby for globbing files

  • #​13233 32fafeb Thanks @​joshmkennedy! - Ensures that Astro.url/ctx.url is correctly updated with the base path after rewrites.

    This change fixes an issue where Astro.url/ctx.url did not include the configured base path after Astro.rewrite was called. Now, the base path is correctly reflected in Astro.url.

    Previously, any rewrites performed through Astro.rewrite/ctx.rewrite failed to append the base path to Astro.url/ctx.rewrite, which could lead to incorrect URL handling in downstream logic. By fixing this, we ensure that all routes remain consistent and predictable after a rewrite.

    If you were relying on the work around of including the base path in astro.rewrite you can now remove it from the path.

v5.3.0

Compare Source

Minor Changes

  • #​13210 344e9bc Thanks @​VitaliyR! - Handle HEAD requests to an endpoint when a handler is not defined.

    If an endpoint defines a handler for GET, but does not define a handler for HEAD, Astro will call the GET handler and return the headers and status but an empty body.

  • #​13195 3b66955 Thanks @​MatthewLymer! - Improves SSR performance for synchronous components by avoiding the use of Promises. With this change, SSR rendering of on-demand pages can be up to 4x faster.

  • #​13145 8d4e566 Thanks @​ascorbic! - Adds support for adapters auto-configuring experimental session storage drivers.

    Adapters can now configure a default session storage driver when the experimental.session flag is enabled. If a hosting platform has a storage primitive that can be used for session storage, the adapter can automatically configure the session storage using that driver. This allows Astro to provide a more seamless experience for users who want to use sessions without needing to manually configure the session storage.

Patch Changes

  • #​13145 8d4e566 Thanks @​ascorbic! - ⚠️ BREAKING CHANGE FOR EXPERIMENTAL SESSIONS ONLY ⚠️

    Changes the experimental.session option to a boolean flag and moves session config to a top-level value. This change is to allow the new automatic session driver support. You now need to separately enable the experimental.session flag, and then configure the session driver using the top-level session key if providing manual configuration.

    defineConfig({
  // ...
  experimental: {
-    session: {
-      driver: 'upstash',
-    },
+    session: true,
  },
+  session: {
+    driver: 'upstash',
+  },
});

    You no longer need to configure a session driver if you are using an adapter that supports automatic session driver configuration and wish to use its default settings.

    defineConfig({
  adapter: node({
    mode: "standalone",
  }),
  experimental: {
-    session: {
-      driver: 'fs',
-      cookie: 'astro-cookie',
-    },
+    session: true,
  },
+  session: {
+    cookie: 'astro-cookie',
+  },
});

    However, you can still manually configure additional driver options or choose a non-default driver to use with your adapter with the new top-level session config option. For more information, see the experimental session docs.

  • #​13101 2ed67d5 Thanks @​corneliusroemer! - Fixes a bug where HEAD and OPTIONS requests for non-prerendered pages were incorrectly rejected with 403 FORBIDDEN

v5.2.6

Compare Source

Patch Changes
pnpm/pnpm (pnpm)

v10.6.0

Compare Source

Minor Changes

  • pnpm-workspace.yaml can now hold all the settings that .npmrc accepts. The settings should use camelCase #​9211.

    pnpm-workspace.yaml example:

    verifyDepsBeforeRun: install
optimisticRepeatInstall: true
publicHoistPattern:
  - "*types*"
  - "!@&#8203;types/react"

  • Projects using a file: dependency on a local tarball file (i.e. .tgz, .tar.gz, .tar) will see a performance improvement during installation. Previously, using a file: dependency on a tarball caused the lockfile resolution step to always run. The lockfile will now be considered up-to-date if the tarball is unchanged.

Patch Changes
  • pnpm self-update should not leave a directory with a broken pnpm installation if the installation fails.
  • fast-glob replace with tinyglobby to reduce the size of the pnpm CLI dependencies #​9169.
  • pnpm deploy should not remove fields from the deployed package's package.json file #​9215.
  • pnpm self-update should not read the pnpm settings from the package.json file in the current working directory.
  • Fix pnpm deploy creating a package.json without the imports and license field #​9193.
  • pnpm update -i should list only packages that have newer versions #​9206.
  • Fix a bug causing entries in the catalogs section of the pnpm-lock.yaml file to be removed when dedupe-peer-dependents=false on a filtered install. #​9112

v10.5.2

Compare Source

Patch Changes
  • The pnpm config set command should change the global .npmrc file by default.
    This was a regression introduced by #​9151 and shipped in pnpm v10.5.0.

v10.5.1

Compare Source

Patch Changes
  • Throw an error message if a pnpm-workspaces.yaml or pnpm-workspaces.yml file is found instead of a pnpm-workspace.yaml #​9170.
  • Fix the update of pnpm-workspace.yaml by the pnpm approve-builds command #​9168.
  • Normalize generated link paths in package.json #​9163
  • Specifying overrides in pnpm-workspace.yaml should work.
  • pnpm dlx should ignore settings from the package.json file in the current working directory #​9178.

v10.5.0

Compare Source

Minor Changes

  • Allow to set the "pnpm" settings from package.json via the pnpm-workspace.yaml file #​9121.

  • Added support for automatically syncing files of injected workspace packages after pnpm run #​9081. Use the sync-injected-deps-after-scripts setting to specify which scripts build the workspace package. This tells pnpm when syncing is needed. The setting should be defined in a .npmrc file at the root of the workspace. Example:

    sync-injected-deps-after-scripts[]=compile

  • The packages field in pnpm-workspace.yaml became optional.

Patch Changes
  • pnpm link with no parameters should work as if --global is specified #​9151.
  • Allow scope registry CLI option without --config. prefix such as --@&#8203;scope:registry=https://scope.example.com/npm #​9089.
  • pnpm link <path> should calculate relative path from the root of the workspace directory #​9132.
  • Fix a bug causing catalog snapshots to be removed from the pnpm-lock.yaml file when using --fix-lockfile and --filter. #​8639
  • Fix a bug causing catalog protocol dependencies to not re-resolve on a filtered install #​8638.
egoist/tsup (tsup)

v8.4.0

Compare Source

   🚀 Features
   🐞 Bug Fixes
    View changes on GitHub
vercel/turborepo (turbo)

v2.4.4: Turborepo v2.4.4

Compare Source

What's Changed

Docs
Changelog

New Contributors

Full Changelog: vercel/turborepo@v2.4.3...v2.4.4

v2.4.3: Turborepo v2.4.3

Compare Source

What's Changed

Docs
create-turbo
@​turbo/codemod
eslint
@​turbo/repository
Examples
Changelog

New Contributors

Full Changelog: vercel/turborepo@v2.3.7...v2.4.3

microsoft/TypeScript (typescript)

v5.8.2

Compare Source

Configuration

📅 Schedule: Branch creation - "* 0-3 * * 1" in timezone Europe/Copenhagen, 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.

@cloudflare-workers-and-pages Cloudflare Workers and Pages
Copy link

cloudflare-workers-and-pages bot commented Mar 3, 2025 •
edited
Loading

Deploying lesetid with  Cloudflare Pages  Cloudflare Pages

Latest commit: b8121f6
Status: ✅  Deploy successful!
Preview URL: https://63fc0f4a.lesetid.pages.dev
Branch Preview URL: https://renovate-all-minor-patch.lesetid.pages.dev

View logs

@renovate renovate bot requested a review from luxass as a code owner March 3, 2025 00:30
@renovate renovate bot added the dependencies Pull requests that update a dependency label Mar 3, 2025
@renovate renovate bot assigned luxass Mar 3, 2025
@github-actions github-actions bot added pkg: remark-lesetid Related to remark-lesetid package pkg: lesetid labels Mar 3, 2025
@renovate renovate bot force-pushed the renovate/all-minor-patch branch from 9b32f45 to b943e2d Compare March 3, 2025 18:38
@github-actions github-actions bot removed pkg: remark-lesetid Related to remark-lesetid package pkg: lesetid labels Mar 3, 2025
@renovate renovate bot force-pushed the renovate/all-minor-patch branch from b943e2d to b6609a5 Compare March 3, 2025 21:40
@github-actions github-actions bot added pkg: remark-lesetid Related to remark-lesetid package pkg: lesetid labels Mar 3, 2025
@renovate renovate bot force-pushed the renovate/all-minor-patch branch from b6609a5 to 149762b Compare March 4, 2025 00:51
@github-actions github-actions bot removed pkg: remark-lesetid Related to remark-lesetid package pkg: lesetid labels Mar 4, 2025
@renovate renovate bot force-pushed the renovate/all-minor-patch branch from 149762b to 58bdf54 Compare March 4, 2025 09:02
@github-actions github-actions bot added pkg: remark-lesetid Related to remark-lesetid package pkg: lesetid labels Mar 4, 2025
@renovate renovate bot force-pushed the renovate/all-minor-patch branch 4 times, most recently from 6fd7836 to 6effbf4 Compare March 6, 2025 16:35
@github-actions github-actions bot removed pkg: remark-lesetid Related to remark-lesetid package pkg: lesetid labels Mar 6, 2025
@renovate renovate bot force-pushed the renovate/all-minor-patch branch from 6effbf4 to 4bbfb7f Compare March 7, 2025 21:07
@github-actions github-actions bot added pkg: remark-lesetid Related to remark-lesetid package pkg: lesetid labels Mar 7, 2025
@renovate renovate bot force-pushed the renovate/all-minor-patch branch from 4bbfb7f to e4e4c5a Compare March 8, 2025 01:18
@github-actions github-actions bot removed pkg: remark-lesetid Related to remark-lesetid package pkg: lesetid labels Mar 8, 2025
@renovate renovate bot force-pushed the renovate/all-minor-patch branch from e4e4c5a to 7fd4b40 Compare March 8, 2025 08:33
@github-actions github-actions bot added pkg: remark-lesetid Related to remark-lesetid package pkg: lesetid labels Mar 8, 2025
@renovate renovate bot force-pushed the renovate/all-minor-patch branch from 7fd4b40 to 0d18a23 Compare March 10, 2025 21:07
@github-actions github-actions bot removed pkg: remark-lesetid Related to remark-lesetid package pkg: lesetid labels Mar 10, 2025
@renovate renovate bot force-pushed the renovate/all-minor-patch branch from 0d18a23 to eeddc02 Compare March 11, 2025 15:42
@github-actions github-actions bot added pkg: remark-lesetid Related to remark-lesetid package pkg: lesetid labels Mar 11, 2025
@renovate renovate bot force-pushed the renovate/all-minor-patch branch from eeddc02 to b8121f6 Compare March 13, 2025 12:40
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@luxass luxass Awaiting requested review from luxass luxass is a code owner

Assignees

@luxass luxass

Labels
dependencies Pull requests that update a dependency pkg: lesetid pkg: remark-lesetid Related to remark-lesetid package
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
1 participant
@luxass