NixOS / nixos-homepage

Sources for nixos.org
https://nixos.org
285 stars 305 forks source link

chore(deps): bump the all group with 4 updates #1461

Closed dependabot[bot] closed 2 weeks ago

dependabot[bot] commented 3 weeks ago

Bumps the all group with 4 updates: @astrojs/mdx, astro, tailwindcss and @iconify-json/simple-icons.

Updates @astrojs/mdx from 3.0.1 to 3.1.0

Release notes

Sourced from @​astrojs/mdx's releases.

@​astrojs/mdx@​3.1.0

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 '@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'); });

Changelog

Sourced from @​astrojs/mdx's changelog.

3.1.0

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 '@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'); });

Commits


Updates astro from 4.9.2 to 4.10.1

Release notes

Sourced from astro's releases.

astro@4.10.1

Patch Changes

astro@4.10.0

Minor Changes

  • #10974 2668ef9 Thanks @​florian-lefebvre! - Adds experimental support for the astro:env API.

    The astro:env API lets you configure a type-safe schema for your environment variables, and indicate whether they should be available on the server or the client. Import and use your defined variables from the appropriate /client or /server module:

    ---
    import { PUBLIC_APP_ID } from 'astro:env/client';
    import { PUBLIC_API_URL, getSecret } from 'astro:env/server';
    const API_TOKEN = getSecret('API_TOKEN');
    

    const data = await fetch(${PUBLIC_API_URL}/users, { method: 'POST', headers: { 'Content-Type': 'application/json', Authorization: Bearer ${API_TOKEN}, }, body: JSON.stringify({ appId: PUBLIC_APP_ID }), });

    To define the data type and properties of your environment variables, declare a schema in your Astro config in experimental.env.schema. The envField helper allows you define your variable as a string, number, or boolean and pass properties in an object:

    // astro.config.mjs
    import { defineConfig, envField } from 'astro/config';
    

    export default defineConfig({ experimental: { env: { schema: { PUBLIC_API_URL: envField.string({ context: 'client', access: 'public', optional: true }), PUBLIC_PORT: envField.number({ context: 'server', access: 'public', default: 4321 }), API_SECRET: envField.string({ context: 'server', access: 'secret' }), }, },

... (truncated)

Changelog

Sourced from astro's changelog.

4.10.1

Patch Changes

4.10.0

Minor Changes

  • #10974 2668ef9 Thanks @​florian-lefebvre! - Adds experimental support for the astro:env API.

    The astro:env API lets you configure a type-safe schema for your environment variables, and indicate whether they should be available on the server or the client. Import and use your defined variables from the appropriate /client or /server module:

    ---
    import { PUBLIC_APP_ID } from 'astro:env/client';
    import { PUBLIC_API_URL, getSecret } from 'astro:env/server';
    const API_TOKEN = getSecret('API_TOKEN');
    

    const data = await fetch(${PUBLIC_API_URL}/users, { method: 'POST', headers: { 'Content-Type': 'application/json', Authorization: Bearer ${API_TOKEN}, }, body: JSON.stringify({ appId: PUBLIC_APP_ID }), });

    To define the data type and properties of your environment variables, declare a schema in your Astro config in experimental.env.schema. The envField helper allows you define your variable as a string, number, or boolean and pass properties in an object:

    // astro.config.mjs
    import { defineConfig, envField } from 'astro/config';
    

    export default defineConfig({ experimental: { env: { schema: { PUBLIC_API_URL: envField.string({ context: 'client', access: 'public', optional: true }), PUBLIC_PORT: envField.number({ context: 'server', access: 'public', default: 4321 }), API_SECRET: envField.string({ context: 'server', access: 'secret' }),

... (truncated)

Commits


Updates tailwindcss from 3.4.3 to 3.4.4

Release notes

Sourced from tailwindcss's releases.

v3.4.4

Fixed

  • Make it possible to use multiple <alpha-value> placeholders in a single color definition (#13740)
  • Don't prefix classes in arbitrary values of has-*, group-has-*, and peer-has-* variants (#13770)
  • Support negative values for {col,row}-{start,end} utilities (#13781)
  • Update embedded browserslist database (#13792)
Changelog

Sourced from tailwindcss's changelog.

[3.4.4] - 2024-06-05

Fixed

  • Make it possible to use multiple <alpha-value> placeholders in a single color definition (#13740)
  • Don't prefix classes in arbitrary values of has-*, group-has-*, and peer-has-* variants (#13770)
  • Support negative values for {col,row}-{start,end} utilities (#13781)
  • Update embedded browserslist database (#13792)
Commits


Updates @iconify-json/simple-icons from 1.1.103 to 1.1.104

Commits


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