search

GenSpectrum / LAPIS

An API, a query engine, and a database schema for genomic sequences; currently with a focus on SARS-CoV-2
https://lapis-three.vercel.app
GNU Affero General Public License v3.0
19 stars 5 forks source link

chore(lapis2-docs): bump the minorandpatch group in /lapis2-docs with 12 updates #819

Closed dependabot[bot] closed 2 months ago

dependabot[bot] commented 2 months ago

Bumps the minorandpatch group in /lapis2-docs with 12 updates:

Package From To
@astrojs/react 3.3.4 3.4.0
@astrojs/starlight 0.22.2 0.23.1
@astrojs/starlight-tailwind 2.0.2 2.0.3
@types/react 18.3.2 18.3.3
astro 4.8.3 4.9.2
sharp 0.33.3 0.33.4
swagger-ui 5.17.9 5.17.13
swagger-ui-react 5.17.9 5.17.13
@astrojs/check 0.6.0 0.7.0
@playwright/test 1.44.0 1.44.1
@types/node 20.12.11 20.12.12
prettier-plugin-astro 0.13.0 0.14.0

Updates @astrojs/react from 3.3.4 to 3.4.0

Release notes

Sourced from @​astrojs/react's releases.

@​astrojs/react@​3.4.0

Minor Changes

  • #11071 8ca7c73 Thanks @​bholmesdev! - Adds two new functions experimental_getActionState() and experimental_withState() to support the React 19 useActionState() hook when using Astro Actions. This introduces progressive enhancement when calling an Action with the withState() utility.

    This example calls a like action that accepts a postId and returns the number of likes. Pass this action to the experimental_withState() function to apply progressive enhancement info, and apply to useActionState() to track the result:

    import { actions } from 'astro:actions';
import { experimental_withState } from '@astrojs/react/actions';

    export function Like({ postId }: { postId: string }) {
const [state, action, pending] = useActionState(
experimental_withState(actions.like),
0 // initial likes
);
    

    return (
<form action={action}>
<input type="hidden" name="postId" value={postId} />
<button disabled={pending}>{state} ❤️</button>
</form>
);
}

    You can also access the state stored by useActionState() from your action handler. Call experimental_getActionState() with the API context, and optionally apply a type to the result:

    import { defineAction, z } from 'astro:actions';
import { experimental_getActionState } from '@astrojs/react/actions';

    export const server = {
like: defineAction({
input: z.object({
postId: z.string(),
}),
handler: async ({ postId }, ctx) => {
const currentLikes = experimental_getActionState<number>(ctx);
// write to database
return currentLikes + 1;
},
}),
};

Changelog

Sourced from @​astrojs/react's changelog.

3.4.0

Minor Changes

  • #11071 8ca7c73 Thanks @​bholmesdev! - Adds two new functions experimental_getActionState() and experimental_withState() to support the React 19 useActionState() hook when using Astro Actions. This introduces progressive enhancement when calling an Action with the withState() utility.

    This example calls a like action that accepts a postId and returns the number of likes. Pass this action to the experimental_withState() function to apply progressive enhancement info, and apply to useActionState() to track the result:

    import { actions } from 'astro:actions';
import { experimental_withState } from '@astrojs/react/actions';

    export function Like({ postId }: { postId: string }) {
const [state, action, pending] = useActionState(
experimental_withState(actions.like),
0 // initial likes
);
    

    return (
<form action={action}>
<input type="hidden" name="postId" value={postId} />
<button disabled={pending}>{state} ❤️</button>
</form>
);
}

    You can also access the state stored by useActionState() from your action handler. Call experimental_getActionState() with the API context, and optionally apply a type to the result:

    import { defineAction, z } from 'astro:actions';
import { experimental_getActionState } from '@astrojs/react/actions';

    export const server = {
like: defineAction({
input: z.object({
postId: z.string(),
}),
handler: async ({ postId }, ctx) => {
const currentLikes = experimental_getActionState<number>(ctx);
// write to database
return currentLikes + 1;
},
}),
};

Commits


Updates @astrojs/starlight from 0.22.2 to 0.23.1

Release notes

Sourced from @​astrojs/starlight's releases.

@​astrojs/starlight@​0.23.1

Patch Changes

@​astrojs/starlight@​0.23.0

Minor Changes

  • #1846 2de67039 Thanks @​delucis! - Updates @astrojs/mdx to v3 and enables MDX optimization by default

    ⚠️ Potentially breaking change: MDX optimization speeds up builds (Starlight’s docs are building ~40% faster for example), but restricts some advanced MDX features. See full details in the MDX optimization documentation.

    Most Starlight users should be unaffected, but if you are using MDX files outside of Starlight pages with the components prop, you may see issues. You can disable optimization by adding MDX manually to your integrations array in astro.config.mjs:

    import { defineConfig } from 'astro/config';
+ import mdx from '@astrojs/mdx';
import starlight from '@astrojs/starlight';

    // https://astro.build/config
export default defineConfig({
integrations: [
starlight({
title: 'My docs',
// ...
}),
    

      

    • 

        mdx(),

      
],
});

  • #1735 1a9ab50d Thanks @​HiDeoo! - Adds custom styles for <details> and <summary> elements in Markdown content.

  • #1846 2de67039 Thanks @​delucis! - ⚠️ BREAKING CHANGE: The minimum supported version of Astro is now 4.8.6

    Please update Astro and Starlight together:

    npx @astrojs/upgrade

    • @​astrojs/starlight@​0.22.4

    Patch Changes

    ... (truncated)

    Changelog

    Sourced from @​astrojs/starlight's changelog.

    0.23.1

    Patch Changes

    0.23.0

    Minor Changes

    • #1846 2de67039 Thanks @​delucis! - Updates @astrojs/mdx to v3 and enables MDX optimization by default

      ⚠️ Potentially breaking change: MDX optimization speeds up builds (Starlight’s docs are building ~40% faster for example), but restricts some advanced MDX features. See full details in the MDX optimization documentation.

      Most Starlight users should be unaffected, but if you are using MDX files outside of Starlight pages with the components prop, you may see issues. You can disable optimization by adding MDX manually to your integrations array in astro.config.mjs:

      import { defineConfig } from 'astro/config';
+ import mdx from '@astrojs/mdx';
import starlight from '@astrojs/starlight';

      // https://astro.build/config
export default defineConfig({
integrations: [
starlight({
title: 'My docs',
// ...
}),
      

        

      • 

          mdx(),

        
],
});

  • #1735 1a9ab50d Thanks @​HiDeoo! - Adds custom styles for <details> and <summary> elements in Markdown content.

  • #1846 2de67039 Thanks @​delucis! - ⚠️ BREAKING CHANGE: The minimum supported version of Astro is now 4.8.6

    Please update Astro and Starlight together:

    npx @astrojs/upgrade

    • 0.22.4

    Patch Changes

    ... (truncated)

    Commits


    Updates @astrojs/starlight-tailwind from 2.0.2 to 2.0.3

    Release notes

    Sourced from @​astrojs/starlight-tailwind's releases.

    @​astrojs/starlight-tailwind@​2.0.3

    Patch Changes

    Changelog

    Sourced from @​astrojs/starlight-tailwind's changelog.

    2.0.3

    Patch Changes

    Commits


    Updates @types/react from 18.3.2 to 18.3.3

    Commits


    Updates astro from 4.8.3 to 4.9.2

    Release notes

    Sourced from astro's releases.

    astro@4.9.2

    Patch Changes

    • #11138 98e0372 Thanks @​ematipico! - You can now pass props when rendering a component using the Container APIs:

      import { experimental_AstroContainer as AstroContainer } from 'astro/contaienr';
import Card from '../src/components/Card.astro';

      const container = await AstroContainer.create();
const result = await container.renderToString(Card, {
props: {
someState: true,
},
});

    astro@4.9.1

    Patch Changes

    astro@4.9.0

    Minor Changes

    • #11051 12a1bcc Thanks @​ematipico! - Introduces an experimental Container API to render .astro components in isolation.

      This API introduces three new functions to allow you to create a new container and render an Astro component returning either a string or a Response:

      • create(): creates a new instance of the container.
      • renderToString(): renders a component and return a string.
      • renderToResponse(): renders a component and returns the Response emitted by the rendering phase.

      The first supported use of this new API is to enable unit testing. For example, with vitest, you can create a container to render your component with test data and check the result:

      import { experimental_AstroContainer as AstroContainer } from 'astro/container';
import { expect, test } from 'vitest';
import Card from '../src/components/Card.astro';

      test('Card with slots', async () => {
const container = await AstroContainer.create();
const result = await container.renderToString(Card, {
slots: {
default: 'Card content',
},
});
      

      expect(result).toContain('This is a card');
expect(result).toContain('Card content');

    ... (truncated)

    Changelog

    Sourced from astro's changelog.

    4.9.2

    Patch Changes

    • #11138 98e0372 Thanks @​ematipico! - You can now pass props when rendering a component using the Container APIs:

      import { experimental_AstroContainer as AstroContainer } from 'astro/contaienr';
import Card from '../src/components/Card.astro';

      const container = await AstroContainer.create();
const result = await container.renderToString(Card, {
props: {
someState: true,
},
});

    4.9.1

    Patch Changes

    4.9.0

    Minor Changes

    • #11051 12a1bcc Thanks @​ematipico! - Introduces an experimental Container API to render .astro components in isolation.

      This API introduces three new functions to allow you to create a new container and render an Astro component returning either a string or a Response:

      • create(): creates a new instance of the container.
      • renderToString(): renders a component and return a string.
      • renderToResponse(): renders a component and returns the Response emitted by the rendering phase.

      The first supported use of this new API is to enable unit testing. For example, with vitest, you can create a container to render your component with test data and check the result:

      import { experimental_AstroContainer as AstroContainer } from 'astro/container';
import { expect, test } from 'vitest';
import Card from '../src/components/Card.astro';

      test('Card with slots', async () => {
const container = await AstroContainer.create();
const result = await container.renderToString(Card, {
slots: {
default: 'Card content',
},
});

    ... (truncated)

    Commits


    Updates sharp from 0.33.3 to 0.33.4

    Changelog

    Sourced from sharp's changelog.

    v0.33.4 - 16th May 2024

    • Remove experimental status from pipelineColourspace.

    • Reduce default concurrency when musl thread over-subscription detected.

    • TypeScript: add missing definitions for OverlayOptions. #4048 @​ike-gg

    • Install: add advanced option to force use of a globally-installed libvips. #4060

    • Expose bilinear resizing kernel (and interpolator). #4061

    • Ensure extend operation stays sequential for multi-page TIFF (regression in 0.32.0). #4069

    • Tighten validation of constructor text integer properties. #4071

    • Simplify internal StaySequential logic. #4074 @​kleisauke

    • Ensure negate operation occurs after profile conversion. #4096 @​adriaanmeuris

    Commits
    • 19d0e27 Release v0.33.4
    • 16b764f Prerelease v0.33.4-rc.0
    • 1593ee3 Bump devDeps
    • 668b5ba Docs: changelog and credit for #4096
    • 29336f4 Ensure negate op occurs after profile conversion (#4096)
    • b5fddd7 Install: log node-addon-api version if available
    • da655a1 Reduce default concurrency for musl thread over-subscription
    • 93c615d Bump devDeps
    • f325dc3 Refactor to use C++ boolean literals rather than macros
    • 0fde71c Ensure all contributor email addresses are valid (#4088)
    • Additional commits viewable in compare view


    Updates swagger-ui from 5.17.9 to 5.17.13

    Release notes

    Sourced from swagger-ui's releases.

    Swagger UI v5.17.13 Released!

    5.17.13 (2024-05-27)

    Bug Fixes

    Swagger UI v5.17.12 Released!

    5.17.12 (2024-05-21)

    Bug Fixes

    • config: define missing default options and their types (#9949) (04bbeaa), closes #9945
    • release: fix failed v5.17.11 release (a35a71e)
    • swagger-client: fix OpenAPI 3.1.0 dereferencing (#9950) (10e1a5f), closes #9941

    Swagger UI v5.17.10 Released!

    5.17.10 (2024-05-15)

    Bug Fixes

    • components: add support for oneOf/anyOf JSON Schema keywords in parameter-row rendering (#9934) (9037acf), closes #7912
    • oas31: fix initial rendering of the Webhooks section (#9938) (b5c84f4), closes #9937
    Commits


    Updates swagger-ui-react from 5.17.9 to 5.17.13

    Release notes

    Sourced from swagger-ui-react's releases.

    Swagger UI v5.17.13 Released!

    5.17.13 (2024-05-27)

    Bug Fixes

    Swagger UI v5.17.12 Released!

    5.17.12 (2024-05-21)

    Bug Fixes

    • config: define missing default options and their types (#9949) (04bbeaa), closes #9945
    • release: fix failed v5.17.11 release (a35a71e)
    • swagger-client: fix OpenAPI 3.1.0 dereferencing (#9950) (10e1a5f), closes #9941

    Swagger UI v5.17.10 Released!

    5.17.10 (2024-05-15)

    Bug Fixes

    • components: add support for oneOf/anyOf JSON Schema keywords in parameter-row rendering (#9934) (9037acf), closes #7912
    • oas31: fix initial rendering of the Webhooks section (#9938) (b5c84f4), closes #9937
    Commits


    Updates @astrojs/check from 0.6.0 to 0.7.0

    Release notes

    Sourced from @​astrojs/check's releases.

    @​astrojs/check@​0.7.0

    Minor Changes

    • c8af6db: Upgrades the language server to use the latest version of Volar. This changes should have no negative impacts on the experience.

    Patch Changes

    • Updated dependencies [c8af6db]
      • @​astrojs/language-server@​2.10.0
    Changelog

    Sourced from @​astrojs/check's changelog.

    0.7.0

    Minor Changes

    • c8af6db: Upgrades the language server to use the latest version of Volar. This changes should have no negative impacts on the experience.

    Patch Changes

    • Updated dependencies [c8af6db]
      • @​astrojs/language-server@​2.10.0
    Commits


    Updates @playwright/test from 1.44.0 to 1.44.1

    Release notes

    Sourced from @​playwright/test's releases.

    v1.44.1

    Highlights

    microsoft/playwright#30779 - [REGRESSION]: When using video: 'on' with VSCode extension the browser got closed microsoft/playwright#30755 - [REGRESSION]: Electron launch with spaces inside executablePath didn't work microsoft/playwright#30770 - [REGRESSION]: Mask elements outside of viewport when creating fullscreen screenshots didn't work microsoft/playwright#30858 - [REGRESSION]: ipv6 got shown instead of localhost in show-trace/show-report

    Browser Versions

    • Chromium 125.0.6422.14
    • Mozilla Firefox 125.0.1
    • WebKit 17.4

    This version was also tested against the following stable channels:

    • Google Chrome 124
    • Microsoft Edge 124
    Commits


    Updates @types/node from 20.12.11 to 20.12.12

    Commits


    Updates prettier-plugin-astro from 0.13.0 to 0.14.0

    Release notes

    Sourced from prettier-plugin-astro's releases.

    v0.14.0

    Minor Changes

    • bb756df: Adds a new option called astroSkipFrontmatter to disable formatting the frontmatter. This can be useful when using other tools to format the frontmatter, such as Biome or dprint.
    Changelog

    Sourced from prettier-plugin-astro's changelog.

    0.14.0

    Minor Changes

    • bb756df: Adds a new option called astroSkipFrontmatter to disable formatting the frontmatter. This can be useful when using other tools to format the frontmatter, such as Biome or dprint.
    Commits


    Most Recent Ignore Conditions Applied to This Pull Request | Dependency Name | Ignore Conditions | | --- | --- | | @astrojs/starlight | [>= 0.21.a, < 0.22] |

    Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

    Dependabot commands and options
    You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot show ignore conditions` will show all of the ignore conditions of the specified dependency - `@dependabot ignore major version` will close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself) - `@dependabot ignore minor version` will close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself) - `@dependabot ignore ` will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself) - `@dependabot unignore ` will remove all of the ignore conditions of the specified dependency - `@dependabot unignore ` will remove the ignore condition of the specified dependency and ignore conditions