fix(deps): update astro monorepo (major) #44

renovate · 2024-05-01T09:10:43Z

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
@astrojs/mdx (source)	`1.1.5` -> `3.1.3`
@astrojs/vercel (source)	`5.2.0` -> `7.7.2`
astro (source)	`3.6.5` -> `4.12.3`

Release Notes

withastro/astro (@astrojs/mdx)

Patch Changes

#11263 7d59750 Thanks @wackbyte! - Refactor to use Astro's integration logger for logging

`v3.1.0`

Compare Source

Minor Changes

#11144 803dd80 Thanks @ematipico! - The integration now exposes a function called getContainerRenderer, that can be used inside the Container APIs to load the relative renderer.

import { experimental_AstroContainer as AstroContainer } from 'astro/container';
import ReactWrapper from '../src/components/ReactWrapper.astro';
import { loadRenderers } from 'astro:container';
import { getContainerRenderer } from '@&#8203;astrojs/react';

test('ReactWrapper with react renderer', async () => {
  const renderers = await loadRenderers([getContainerRenderer()]);
  const container = await AstroContainer.create({
    renderers,
  });
  const result = await container.renderToString(ReactWrapper);

  expect(result).toContain('Counter');
  expect(result).toContain('Count: <!-- -->5');
});

`v3.0.1`

Compare Source

Patch Changes

#10813 3cc3e2c Thanks @Xetera! - Omitting compiler-internal symbol from user components to fix breaking error messages

`v3.0.0`

Compare Source

Major Changes

#10935 ddd8e49 Thanks @bluwy! - Refactors the MDX transformation to rely only on the unified pipeline. Babel and esbuild transformations are removed, which should result in faster build times. The refactor requires using Astro v4.8.0 but no other changes are necessary.
#10935 ddd8e49 Thanks @bluwy! - Allows integrations after the MDX integration to update markdown.remarkPlugins and markdown.rehypePlugins, and have the plugins work in MDX too.

If your integration relies on Astro's previous behavior that prevents integrations from adding remark/rehype plugins for MDX, you will now need to configure @astrojs/mdx with extendMarkdownConfig: false and explicitly specify any remarkPlugins and rehypePlugins options instead.
#10935 ddd8e49 Thanks @bluwy! - Renames the optimize.customComponentNames option to optimize.ignoreElementNames to better reflect its usecase. Its behaviour is not changed and should continue to work as before.
#10935 ddd8e49 Thanks @bluwy! - Replaces the internal remark-images-to-component plugin with rehype-images-to-component to let users use additional rehype plugins for images

Patch Changes

#10935 ddd8e49 Thanks @bluwy! - Simplifies plain MDX components as hast element nodes to further improve HTML string inlining for the optimize option
#10935 ddd8e49 Thanks @bluwy! - Allows Vite plugins to transform .mdx files before the MDX plugin transforms it
#10935 ddd8e49 Thanks @bluwy! - Updates the optimize option to group static sibling nodes as a <Fragment />. This reduces the number of AST nodes and simplifies runtime rendering of MDX pages.
#10935 ddd8e49 Thanks @bluwy! - Tags the MDX component export for quicker component checks while rendering
#10935 ddd8e49 Thanks @bluwy! - Fixes export const components keys detection for the optimize option
#10935 ddd8e49 Thanks @bluwy! - Improves optimize handling for MDX components with attributes and inline MDX components

`v2.3.1`

Compare Source

Patch Changes

#10754 3e7a12c8532411e580fcfdb8445cad8fc8499291 Thanks @rishi-raj-jain! - Fixes an issue where images in MDX required a relative specifier (e.g. ./)

Now, you can use the standard ![](img.png) syntax in MDX files for images colocated in the same folder: no relative specifier required!

There is no need to update your project; your existing images will still continue to work. However, you may wish to remove any relative specifiers from these MDX images as they are no longer necessary:
```
- ![A cute dog](./dog.jpg)
+ ![A cute dog](dog.jpg)

```
#10770 88ee63a3ba4488c60348cb821034e6d4a057efd0 Thanks @bluwy! - Removes internal MDX processor on buildEnd to free up memory

`v2.3.0`

Compare Source

Minor Changes

#10689 683d51a5eecafbbfbfed3910a3f1fbf0b3531b99 Thanks @ematipico! - Deprecate support for versions of Node.js older than v18.17.1 for Node.js 18, older than v20.0.3 for Node.js 20, and the complete Node.js v19 release line.

This change is in line with Astro's Node.js support policy.

Patch Changes

Updated dependencies [ccafa8d230f65c9302421a0ce0a0adc5824bfd55]:
- @astrojs/markdown-remark @5.1.0

`v2.2.4`

Compare Source

Patch Changes

#10673 db7f9c87035a0de780536d95cdd9facff00c3c08 Thanks @bluwy! - Removes unnecessary internal recmaInjectImportMetaEnv plugin

`v2.2.3`

Compare Source

Patch Changes

Updated dependencies [2cf116f80cb5e421ab5cc5eb4a654e7b78c1b8de, 374efcdff9625ca43309d89e3b9cfc9174351512]:
- @astrojs/markdown-remark @5.0.0

`v2.2.2`

Compare Source

Patch Changes

Updated dependencies [c585528f446ccca3d4c643f4af5d550b93c18902]:
- @astrojs/markdown-remark @4.3.2

`v2.2.1`

Compare Source

Patch Changes

Updated dependencies [19e42c368184013fc30d1e46753b9e9383bb2bdf]:
- @astrojs/markdown-remark @4.3.1

`v2.2.0`

Compare Source

Minor Changes

#10104 a31bbd7ff8f3ec62ee507f72d1d25140b82ffc18 Thanks @remcohaszing! - Changes Astro's internal syntax highlighting to use rehype plugins instead of remark plugins. This provides better interoperability with other rehype plugins that deal with code blocks, in particular with third party syntax highlighting plugins and rehype-mermaid.

This may be a breaking change if you are currently using:
- a remark plugin that relies on nodes of type html
- a rehype plugin that depends on nodes of type raw.
Please review your rendered code samples carefully, and if necessary, consider using a rehype plugin that deals with the generated element nodes instead. You can transform the AST of raw HTML strings, or alternatively use hast-util-to-html to get a string from a raw node.

Patch Changes

Updated dependencies [c081adf998d30419fed97d8fccc11340cdc512e0, 5a9528741fa98d017b269c7e4f013058028bdc5d, a31bbd7ff8f3ec62ee507f72d1d25140b82ffc18]:
- @astrojs/markdown-remark @4.3.0

`v2.1.1`

Compare Source

Patch Changes

Updated dependencies [44c957f893c6bf5f5b7c78301de7b21c5975584d]:
- @astrojs/markdown-remark @4.2.1

`v2.1.0`

Compare Source

Minor Changes

#9753 df37366556d46f7abdf82b09e33b08bd94e631b3 Thanks @OliverSpeir! - Allows remark plugins to pass options specifying how images in .mdx files will be optimized

`v2.0.6`

Compare Source

Patch Changes

Updated dependencies [53c69dcc82cdf4000aff13a6c11fffe19096cf45, 2f81cffa9da9db0e2802d303f94feaee8d2f54ec, a505190933365268d48139a5f197a3cfb5570870]:
- @astrojs/markdown-remark @4.2.0

`v2.0.5`

Compare Source

Patch Changes

#9706 1539e04a8e5865027b3a8718c6f142885e7c8d88 Thanks @bluwy! - Removes redundant HMR handling code
Updated dependencies [165cfc154be477337037185c32b308616d1ed6fa, e9a72d9a91a3741566866bcaab11172cb0dc7d31]:
- @astrojs/markdown-remark @4.1.0

`v2.0.4`

Compare Source

Patch Changes

#9652 e72efd6a9a1e2a70488fd225529617ffd8418534 Thanks @bluwy! - Removes environment variables workaround that broke project builds with sourcemaps

`v2.0.3`

Compare Source

Patch Changes

#9479 1baf0b0d3cbd0564954c2366a7278794fad6726e Thanks @sarah11918! - Updates README

`v2.0.2`

Compare Source

Patch Changes

#9452 e83b5095f Thanks @florian-lefebvre! - Upgrades vite to latest

`v2.0.1`

Compare Source

Patch Changes

#9366 1b4e91898 Thanks @lilnasy! - Updates NPM package to refer to the stable Astro version instead of a beta.
Updated dependencies [270c6cc27]:
- @astrojs/markdown-remark @4.0.1

`v2.0.0`

Compare Source

Major Changes

#9138 abf601233 Thanks @bluwy! - Updates the unified, remark, and rehype dependencies to latest. Make sure to update your custom remark and rehype plugins as well to be compatible with the latest versions.

Potentially breaking change: The default value of markdown.remarkRehype.footnoteBackLabel is changed from "Back to content" to "Back to reference 1". See the mdast-util-to-hast commit for more information.

Patch Changes

Updated dependencies [abf601233, addb57c8e, c7953645e]:
- @astrojs/markdown-remark @4.0.0

withastro/astro (@astrojs/vercel)

`v7.7.2`

Compare Source

Patch Changes

#11323 41064ce Thanks @ascorbic! - Extracts fs helpers into shared internal-helpers module
#11296 5848d97 Thanks @florian-lefebvre! - Fixes astro:env getSecret compatibility
Updated dependencies [41064ce]:
- @astrojs/internal-helpers @0.4.1

`v7.7.1`

Compare Source

Patch Changes

#11261 f5f8ed2 Thanks @matthewp! - Fix backwards compat with Astro <= 4.9
#11227 24ce898 Thanks @matthewp! - In Vercel Edge, include cookies set by Astro.cookies.set

`v7.7.0`

Compare Source

Minor Changes

#11199 2bdca27 Thanks @florian-lefebvre! - Adds support for experimental astro:env released in Astro 4.10

`v7.6.0`

Compare Source

Minor Changes

#10761 f0acd30 Thanks @ematipico! - Implements the vercel skew protection

`v7.5.4`

Compare Source

Patch Changes

#10833 8d5f3e8 Thanks @renovate! - Updates esbuild dependency to v0.20. This should not affect projects in most cases.

`v7.5.3`

Compare Source

Patch Changes

#10756 c75ededdb401cfa55e1ad2682d5e95494f49604e Thanks @Princesseuh! - Fixes widths and densities not working when using Vercel's Image Optimization.

Note that you still need to make sure that the widths you're outputting are enabled in the imageConfig property of the Vercel adapter in order for these properties to work.

`v7.5.2`

Compare Source

Patch Changes

#10611 a9a3694a98060be9a33045bb0fcf92ccf1acff6f Thanks @jacobdalamb! - Updates the supported version of Node.js

`v7.5.1`

Compare Source

Patch Changes

#10609 31590d44ef8b7c96a757e9b835144d57d767383c Thanks @matthewp! - Move nft warnings behind verbose logging

`v7.5.0`

Compare Source

Minor Changes

#10513 a573cc199a00d35410197ba4117c97764a984dc0 Thanks @tk04! - The isr.exclude configuration can now include routes with dynamic and spread parameters.

export default defineConfig({
    adapter: vercel({
        isr: {
            exclude: [
                "/blog/[title]"
                "/api/[...slug]",
            ]
        }
    })
})

`v7.4.0`

Compare Source

Minor Changes

#10476 cfbaa8a767b8794c2dcd8e164672195378be396a Thanks @lilnasy! - The special-case handling of src/vercel-edge-middleware.js file is now deprecated. This file allowed you to access the edge runtime's RequestContext object, and create the middleware locals from its fields. However, this object includes only one field - the waitUntil() function - which is now available directly as ctx.locals.vercel.edge.waitUntil().

`v7.3.6`

Compare Source

Patch Changes

Updated dependencies [1ea0a25b94125e4f6f2ac82b42f638e22d7bdffd]:
- @astrojs/internal-helpers @0.3.0

`v7.3.5`

Compare Source

Patch Changes

#10336 f2e60a96754ed1d86001fe4d5d3a0c0ef657408d Thanks @FredKSchott! - Fixes an issue that was preventing the use of sharp in some cases and causing a runtime error

`v7.3.4`

Compare Source

Patch Changes

#10231 ae2a10e1a768e31d243194694222932ffafb54cc Thanks @mingjunlu! - Fixes an issue where functions were also created for prerendered routes with functionPerRoute enabled.

`v7.3.3`

Compare Source

Patch Changes

#10215 a013182d322a3969e39d647aad75ec10f8bd1ed7 Thanks @matthewp! - Fixes edge middleware calling nested routes

`v7.3.2`

Compare Source

Patch Changes

#10194 3cc20109277813ccb9578ca87a8b0d680a73c35c Thanks @matthewp! - Fix loading client-scripts in dev with ISR

`v7.3.1`

Compare Source

Patch Changes

#10082 2ffc5721bc22631c44d90ac43ec27fdb0b5b2d1b Thanks @florian-lefebvre! - Prevents infinite redirects when Astro trailingSlash configuration is set to "always" and "vercel.json" trailingSlash configuration is set to true

`v7.3.0`

Compare Source

Minor Changes

#9987 0699f34d5c4481c027c4d29d73944f79f97008df Thanks @lilnasy! - Implements verification for edge middleware. This is a security measure to ensure that your serverless functions are only ever called by your edge middleware and not a third party.

When edgeMiddleware is enabled, the serverless function will now respond with 403 Forbidden for requests that are not verified to have come from the generated edge middleware. No user action is necessary.

`v7.2.0`

Compare Source

Minor Changes

#9714 e2fe51c828dc7ea8204788e59e3953fe36c97836 Thanks @lilnasy! - Introduces a new config option, isr, that allows you to deploy your project as an ISR function. ISR (Incremental Static Regeneration) caches your on-demand rendered pages in the same way as prerendered pages after first request.

To enable this feature, set isr to true in your Vercel adapter configuration in astro.config.mjs:
```
export default defineConfig({
  output: 'server',
  adapter: vercel({ isr: true }),
});
```

`v7.1.1`

Compare Source

Patch Changes

#9955 bc1742df9423ba66e33dcbf65fbebf67a236175d Thanks @matthewp! - Fix regression with bundling of @libsql/client

`v7.1.0`

Compare Source

Minor Changes

#9143 041fdd5c89920f7ccf944b095f29e451f78b0e28 Thanks @ematipico! - Adds experimental support for internationalization domains

Patch Changes

#9885 49e0c24d7f90d00e986533fcf546665967540ce7 Thanks @matthewp! - Better ignores for Vercel file-tracer

The Vercel adapter has a file-tracer it uses to detect which files should be moved over to the dist/ folder. When it's done, it prints warnings for things that it detected that maybe should be moved.

This change expands how we do ignores so that:
- Ignores happen within dot folders like .pnpm.
- @libsql/client is ignored, a package we know is not bundled.

`v7.0.2`

Compare Source

Patch Changes

#9809 3435b7f1e1ca38fdee8f3b89e2d2667f125d01b5 Thanks @lilnasy! - Fixes an issue where the serverless function ignored cookies added using Astro.cookies.

`v7.0.1`

Compare Source

Patch Changes

#9585 05adaaa2d217a3ecb34244d9b40603f35cef4a37 Thanks @lilnasy! - Fixes an issue where edge middleware did not work.

`v7.0.0`

Compare Source

Major Changes

#9661 d6edc7540864cf5d294d7b881eb886a3804f6d05 Thanks @ematipico! - Breaking: Minimum required Astro version is now 4.2.0.
Reorganizes internals to be more maintainable.

`v6.1.4`

Compare Source

Patch Changes

#9648 d7f1903cded3e864b392d1dd7502672d37936f11 Thanks @lilnasy! - Fixes an issue where the serverless function could not respond with a prerendered 404 page.

`v6.1.3`

Compare Source

Patch Changes

#9591 22a5405b4a4b7948458ad170b0a7bde6954058c1 Thanks @lilnasy! - Fixes an issue where 404.astro was not used in static mode.
#9598 bd8fa7acd23ba6e7afa2c435807bd5fd6b24f505 Thanks @lilnasy! - Marks the speedInsights configuration as deprecated. Vercel has migrated features of the Speed Insights API into a framework-agnostic library with @vercel/speed-insights. See Vercel Speed Insights Quickstart for instructions on how to use the library instead.

`v6.1.2`

Compare Source

Patch Changes

#9550 7b586a6e23e25653814db9adea9674ec3a9bd535 Thanks @lilnasy! - Fixes an issue where a build could not complete on Node 21.

`v6.1.1`

Compare Source

Patch Changes

#9479 1baf0b0d3cbd0564954c2366a7278794fad6726e Thanks @sarah11918! - Updates README

`v6.1.0`

Compare Source

Minor Changes

#9413 836ab6214 Thanks @jacobdalamb! - Adds support for Node 20 (currently in beta on Vercel).

Patch Changes

#9289 8aeb0b579 Thanks @lilnasy! - Fixes an issue where dots in redirects were incorrectly handled.

`v6.0.2`

Compare Source

Patch Changes

#9287 1e342e34e Thanks @lilnasy! - Fixes an issue where redirects did not work with the static adapter.
#9383 bebf5cf22 Thanks @sarah11918! - Fixes some incorrect code examples in the README documentation.
#9334 dfbc70790 Thanks @Geo25rey! - Allows the edge middleware to be an async function.

`v6.0.1`

Compare Source

Patch Changes

#9348 1685cc42b Thanks @matthewp! - Uses the latest astro as the peerDependency

`v6.0.0`

Compare Source

Major Changes

#9199 49aa215a0 Thanks @lilnasy! - The internals of the integration have been updated to support Astro 4.0. Make sure to upgrade your Astro version as Astro 3.0 is no longer supported.
#9184 a145ac07e Thanks @bluwy! - Removes deprecated analytics option. Use the webAnalytics option instead.
#9263 3cbd8ea75 Thanks @bluwy! - Removes the deprecated @astrojs/vercel/edge export. You should use @astrojs/vercel/serverless instead with the edgeMiddleware option.

withastro/astro (astro)

`v4.12.3`

Compare Source

Patch Changes

#11509 dfbca06 Thanks @bluwy! - Excludes hoisted scripts and styles from Astro components imported with ?url or ?raw
#11561 904f1e5 Thanks @ArmandPhilippot! - Uses the correct pageSize default in page.size JSDoc comment
#11571 1c3265a Thanks @bholmesdev! - BREAKING CHANGE to the experimental Actions API only. Install the latest @astrojs/react integration as well if you're using React 19 features.

Make .safe() the default return value for actions. This means { data, error } will be returned when calling an action directly. If you prefer to get the data while allowing errors to throw, chain the .orThrow() modifier.
```
import { actions } from 'astro:actions';

// Before
const { data, error } = await actions.like.safe();
// After
const { data, error } = await actions.like();

// Before
const newLikes = await actions.like();
// After
const newLikes = await actions.like.orThrow();
```

`v4.12.2`

Compare Source

Patch Changes

#11505 8ff7658 Thanks @ematipico! - Enhances the dev server logging when rewrites occur during the lifecycle or rendering.

The dev server will log the status code before and after a rewrite:
```
08:16:48 [404] (rewrite) /foo/about 200ms
08:22:13 [200] (rewrite) /about 23ms
```
#11506 026e8ba Thanks @sarah11918! - Fixes typo in documenting the slot="fallback" attribute for Server Islands experimental feature.
#11508 ca335e1 Thanks @cramforce! - Escapes HTML in serialized props
#11501 4db78ae Thanks @martrapp! - Adds the missing export for accessing the getFallback() function of the client site router.

`v4.12.1`

Compare Source

Patch Changes

#11486 9c0c849 Thanks @ematipico! - Adds a new function called addClientRenderer to the Container API.

This function should be used when rendering components using the client:* directives. The addClientRenderer API must be used
after the use of the addServerRenderer:

const container = await experimental_AstroContainer.create();
container.addServerRenderer({ renderer });
container.addClientRenderer({ name: '@&#8203;astrojs/react', entrypoint: '@&#8203;astrojs/react/client.js' });
const response = await container.renderToResponse(Component);

#11500 4e142d3 Thanks @Princesseuh! - Fixes inferRemoteSize type not working
#11496 53ccd20 Thanks @alfawal! - Hide the dev toolbar on window.print() (CTRL + P)

`v4.12.0`

Compare Source

Minor Changes

#11341 49b5145 Thanks @madcampos! - Adds support for Shiki's defaultColor option.

This option allows you to override the values of a theme's inline style, adding only CSS variables to give you more flexibility in applying multiple color themes.

Configure defaultColor: false in your Shiki config to apply throughout your site, or pass to Astro's built-in <Code> component to style an individual code block.
```
import { defineConfig } from 'astro/config';
export default defineConfig({
  markdown: {
    shikiConfig: {
      themes: {
        light: 'github-light',
        dark: 'github-dark',
      },
      defaultColor: false,
    },
  },
});
```

`v4.11.6`

Compare Source

Patch Changes

#11459 bc2e74d Thanks @mingjunlu! - Fixes false positive audit warnings on elements with the role "tabpanel".
#11472 cb4e6d0 Thanks @delucis! - Avoids targeting all files in the src/ directory for eager optimization by Vite. After this change, only JSX, Vue, Svelte, and Astro components get scanned for early optimization.
#11387 b498461 Thanks @bluwy! - Fixes prerendering not removing unused dynamic imported chunks
#11437 6ccb30e Thanks @NuroDev! - Fixes a case where Astro's config experimental.env.schema keys did not allow numbers. Numbers are still not allowed as the first character to be able to generate valid JavaScript identifiers

#11439 08baf56 Thanks @bholmesdev! - Expands the isInputError() utility from astro:actions to accept errors of any type. This should now allow type narrowing from a try / catch block.

// example.ts
import { actions, isInputError } from 'astro:actions';

try {
  await actions.like(new FormData());
} catch (error) {
  if (isInputError(error)) {
    console.log(error.fields);
  }
}

#11452 0e66849 Thanks @FugiTech! - Fixes an issue where using .nullish() in a formdata Astro action would always parse as a string
#11438 619f07d Thanks @bholmesdev! - Exposes utility types from astro:actions for the defineAction handler (ActionHandler) and the ActionError code (ActionErrorCode).
#11456 17e048d Thanks @RickyC0626! - Fixes astro dev --open unexpected behavior that spawns a new tab every time a config file is saved
#11337 0a4b31f Thanks @florian-lefebvre! - Adds a new property experimental.env.validateSecrets to allow validating private variables on the server.

By default, this is set to false and only public variables are checked on start. If enabled, secrets will also be checked on start (dev/build modes). This is useful for example in some CIs to make sure all your secrets are correctly set before deploying.
```
// astro.config.mjs
import { defineConfig, envField } from 'astro/config';

export default defineConfig({
  experimental: {
    env: {
      schema: {
        // ...
      },
      validateSecrets: true,
    },
  },
});
```

#11443 ea4bc04 Thanks @bholmesdev! - Expose new ActionReturnType utility from astro:actions. This infers the return type of an action by passing typeof actions.name as a type argument. This example defines a like action that returns likes as an object:

// actions/index.ts
import { defineAction } from 'astro:actions';

export const server = {
  like: defineAction({
    handler: () => {
      /* ... */
      return { likes: 42 };
    },
  }),
};

In your client code, you can infer this handler return value with ActionReturnType:

// client.ts
import { actions, ActionReturnType } from 'astro:actions';

type LikesResult = ActionReturnType<typeof actions.like>;
// -> { likes: number }

#11436 7dca68f Thanks @bholmesdev! - Fixes astro:actions autocompletion for the defineAction accept property
#11455 645e128 Thanks @florian-lefebvre! - Improves astro:env invalid variables errors

`v4.11.5`

Compare Source

Patch Changes

#11408 b9e906f Thanks @matthewp! - Revert change to how boolean attributes work

`v4.11.4`

Compare Source

Patch Changes

[#11362](https://togithub.com/withastr

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), 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.

codesandbox · 2024-05-01T09:10:47Z

Review or Edit in CodeSandbox

Open the branch in Web Editor • VS Code • Insiders

Open Preview

changeset-bot · 2024-05-01T09:10:47Z

⚠️ No Changeset found

Latest commit: d1a175a

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

vercel · 2024-05-01T09:10:50Z

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Comments	Updated (UTC)
xata-astro	❌ Failed (Inspect)			Jul 30, 2024 4:13pm

socket-security · 2024-05-01T09:13:07Z

🚨 Potential security issues detected. Learn more about Socket for GitHub ↗︎

To accept the risk, merge this PR and you will not be notified again.

Alert	Package	Note	Source	CI
Install scripts	npm/[email protected]	Install script: install Source: `node install/check`	`package.json`	🚫

View full report↗︎

Next steps

What is an install script?

Install scripts are run when the package is installed. The majority of malware in npm is hidden in install scripts.

Packages should not be running non-essential scripts during install and there are often solutions to problems people solve with install scripts that can be run at publish time instead.

Take a deeper look at the dependency

Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support [AT] socket [DOT] dev.

Remove the package

If you happen to install a dependency that Socket reports as Known Malware you should immediately remove it and select a different dependency. For other alert types, you may may wish to investigate alternative packages or consider if there are other ways to mitigate the specific risk posed by the dependency.

Mark a package as acceptable risk

To ignore an alert, reply with a comment starting with @SocketSecurity ignore followed by a space separated list of ecosystem/package-name@version specifiers. e.g. @SocketSecurity ignore npm/[email protected] or ignore all packages with @SocketSecurity ignore-all

@SocketSecurity ignore npm/[email protected]

coderabbitai · 2024-05-22T11:02:36Z

Important

Review skipped

Bot user detected.

To trigger a single review, invoke the @coderabbitai review command.

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

Share

Tips

Chat

There are 3 ways to chat with CodeRabbit:

Review comments: Directly reply to a review comment made by CodeRabbit. Example:
- I pushed a fix in commit <commit_id>.
- Generate unit testing code for this file.
- Open a follow-up GitHub issue for this discussion.
Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
- @coderabbitai generate unit testing code for this file.
- @coderabbitai modularize this function.
PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
- @coderabbitai generate interesting stats about this repository and render them as a table.
- @coderabbitai show all the console.log statements in this repository.
- @coderabbitai read src/utils.ts and generate unit testing code.
- @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
- @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (invoked as PR comments)

@coderabbitai pause to pause the reviews on a PR.
@coderabbitai resume to resume the paused reviews.
@coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
@coderabbitai full review to do a full review from scratch and review all the files again.
@coderabbitai summary to regenerate the summary of the PR.
@coderabbitai resolve resolve all the CodeRabbit review comments.
@coderabbitai configuration to show the current CodeRabbit configuration for the repository.
@coderabbitai help to get help.

Additionally, you can add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.

CodeRabbit Configuration File (`.coderabbit.yaml`)

You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
Please see the configuration documentation for more information.
If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

Visit our Documentation for detailed information on how to use CodeRabbit.
Join our Discord Community to get help, request features, and share feedback.
Follow us on X/Twitter for updates and announcements.

socket-security · 2024-07-03T15:13:28Z

New and removed dependencies detected. Learn more about Socket for GitHub ↗︎

Package	New capabilities	Transitives	Size	Publisher
npm/@astrojs/[email protected]	Transitive: environment, eval, filesystem, network	`+174`	19.8 MB	fredkschott
npm/@astrojs/[email protected]	Transitive: environment, eval, filesystem, network, shell, unsafe	`+111`	230 MB	fredkschott
npm/[email protected]	Transitive: environment, eval, filesystem, network, shell	`+393`	529 MB	fredkschott, matthewp, natemoo-re

🚮 Removed packages: npm/@astrojs/[email protected], npm/@astrojs/[email protected], npm/[email protected]

View full report↗︎

vercel bot had a problem deploying to Preview May 1, 2024 09:10 Failure

renovate bot force-pushed the renovate/major-astro-monorepo branch from df925c1 to 68c6ede Compare May 2, 2024 13:59

vercel bot had a problem deploying to Preview May 2, 2024 13:59 Failure

renovate bot force-pushed the renovate/major-astro-monorepo branch from 68c6ede to 0b642ec Compare May 9, 2024 11:10

vercel bot had a problem deploying to Preview May 9, 2024 11:11 Failure

renovate bot force-pushed the renovate/major-astro-monorepo branch from 0b642ec to 1242581 Compare May 9, 2024 16:40

vercel bot had a problem deploying to Preview May 9, 2024 16:41 Failure

renovate bot force-pushed the renovate/major-astro-monorepo branch from 1242581 to a1d4082 Compare May 9, 2024 19:52

vercel bot had a problem deploying to Preview May 9, 2024 19:53 Failure

renovate bot force-pushed the renovate/major-astro-monorepo branch from a1d4082 to c2075b4 Compare May 13, 2024 13:05

vercel bot had a problem deploying to Preview May 13, 2024 13:05 Failure

renovate bot force-pushed the renovate/major-astro-monorepo branch from c2075b4 to 93a9f94 Compare May 15, 2024 17:01

vercel bot had a problem deploying to Preview May 15, 2024 17:02 Failure

renovate bot force-pushed the renovate/major-astro-monorepo branch from 93a9f94 to 078e884 Compare May 16, 2024 23:07

vercel bot had a problem deploying to Preview May 16, 2024 23:07 Failure

renovate bot force-pushed the renovate/major-astro-monorepo branch from 078e884 to a34f551 Compare May 17, 2024 14:38

vercel bot had a problem deploying to Preview May 17, 2024 14:38 Failure

renovate bot force-pushed the renovate/major-astro-monorepo branch from a34f551 to 86eebe9 Compare May 22, 2024 11:02

vercel bot had a problem deploying to Preview May 22, 2024 11:02 Failure

renovate bot force-pushed the renovate/major-astro-monorepo branch from 86eebe9 to 17f57a7 Compare May 23, 2024 10:51

vercel bot had a problem deploying to Preview May 23, 2024 10:52 Failure

renovate bot force-pushed the renovate/major-astro-monorepo branch from 17f57a7 to d82c2b8 Compare May 23, 2024 16:47

vercel bot had a problem deploying to Preview May 23, 2024 16:48 Failure

renovate bot force-pushed the renovate/major-astro-monorepo branch from d82c2b8 to 03a6706 Compare May 24, 2024 18:54

vercel bot had a problem deploying to Preview May 24, 2024 18:54 Failure

renovate bot force-pushed the renovate/major-astro-monorepo branch from bd26a93 to 0bdf697 Compare June 26, 2024 10:54

vercel bot had a problem deploying to Preview June 26, 2024 10:54 Failure

renovate bot force-pushed the renovate/major-astro-monorepo branch from 0bdf697 to ecccb14 Compare June 26, 2024 16:04

vercel bot had a problem deploying to Preview June 26, 2024 16:05 Failure

renovate bot force-pushed the renovate/major-astro-monorepo branch from ecccb14 to ab7c983 Compare June 29, 2024 21:09

vercel bot had a problem deploying to Preview June 29, 2024 21:10 Failure

renovate bot force-pushed the renovate/major-astro-monorepo branch from ab7c983 to 7f3d17b Compare July 3, 2024 15:13

vercel bot had a problem deploying to Preview July 3, 2024 15:13 Failure

renovate bot force-pushed the renovate/major-astro-monorepo branch from 7f3d17b to 2c4aa91 Compare July 4, 2024 02:13

vercel bot had a problem deploying to Preview July 4, 2024 02:14 Failure

renovate bot force-pushed the renovate/major-astro-monorepo branch from 2c4aa91 to 4cd6faf Compare July 13, 2024 17:25

vercel bot had a problem deploying to Preview July 13, 2024 17:26 Failure

renovate bot force-pushed the renovate/major-astro-monorepo branch from 4cd6faf to 13dde0f Compare July 15, 2024 21:51

vercel bot had a problem deploying to Preview July 15, 2024 21:51 Failure

renovate bot force-pushed the renovate/major-astro-monorepo branch from 13dde0f to 60974f8 Compare July 16, 2024 21:38

vercel bot had a problem deploying to Preview July 16, 2024 21:38 Failure

renovate bot force-pushed the renovate/major-astro-monorepo branch from 60974f8 to c9a9ef3 Compare July 17, 2024 14:59

vercel bot had a problem deploying to Preview July 17, 2024 14:59 Failure

renovate bot force-pushed the renovate/major-astro-monorepo branch from c9a9ef3 to 30be109 Compare July 18, 2024 16:56

vercel bot had a problem deploying to Preview July 18, 2024 16:56 Failure

renovate bot force-pushed the renovate/major-astro-monorepo branch from 30be109 to be304c3 Compare July 19, 2024 01:23

vercel bot had a problem deploying to Preview July 19, 2024 01:23 Failure

renovate bot force-pushed the renovate/major-astro-monorepo branch from be304c3 to 3674c54 Compare July 19, 2024 17:29

vercel bot had a problem deploying to Preview July 19, 2024 17:30 Failure

renovate bot force-pushed the renovate/major-astro-monorepo branch from 3674c54 to 5bc8551 Compare July 25, 2024 00:50

vercel bot had a problem deploying to Preview July 25, 2024 00:50 Failure

fix(deps): update astro monorepo

d1a175a

renovate bot force-pushed the renovate/major-astro-monorepo branch from 5bc8551 to d1a175a Compare July 30, 2024 16:12

vercel bot had a problem deploying to Preview July 30, 2024 16:13 Failure

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

fix(deps): update astro monorepo (major) #44

fix(deps): update astro monorepo (major) #44

renovate bot commented May 1, 2024 •

edited

Loading

codesandbox bot commented May 1, 2024

changeset-bot bot commented May 1, 2024 •

edited

Loading

vercel bot commented May 1, 2024 •

edited

Loading

socket-security bot commented May 1, 2024 •

edited

Loading

coderabbitai bot commented May 22, 2024 •

edited

Loading

Review skipped

Chat

CodeRabbit Commands (invoked as PR comments)

CodeRabbit Configuration File (`.coderabbit.yaml`)

Documentation and Community

socket-security bot commented Jul 3, 2024 •

edited

Loading

fix(deps): update astro monorepo (major) #44

Are you sure you want to change the base?

fix(deps): update astro monorepo (major) #44

Conversation

renovate bot commented May 1, 2024 • edited Loading

Release Notes

Patch Changes

Patch Changes

Patch Changes

Minor Changes

Patch Changes

Major Changes

Patch Changes

Patch Changes

Minor Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Minor Changes

Patch Changes

Patch Changes

Minor Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Major Changes

Patch Changes

Patch Changes

Patch Changes

Minor Changes

Minor Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Minor Changes

Minor Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Minor Changes

Minor Changes

Patch Changes

Minor Changes

Patch Changes

Patch Changes

Patch Changes

Major Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Minor Changes

Patch Changes

Patch Changes

Patch Changes

Major Changes

Patch Changes

Patch Changes

Patch Changes

Minor Changes

Patch Changes

Patch Changes

Patch Changes

Configuration

codesandbox bot commented May 1, 2024

Review or Edit in CodeSandbox

changeset-bot bot commented May 1, 2024 • edited Loading

⚠️ No Changeset found

vercel bot commented May 1, 2024 • edited Loading

socket-security bot commented May 1, 2024 • edited Loading

Next steps

renovate bot commented May 1, 2024 •

edited

Loading

changeset-bot bot commented May 1, 2024 •

edited

Loading

vercel bot commented May 1, 2024 •

edited

Loading

socket-security bot commented May 1, 2024 •

edited

Loading

coderabbitai bot commented May 22, 2024 •

edited

Loading

CodeRabbit Configuration File (`.coderabbit.yaml`)