KeisukeYamashita / commitlint-rs

🔦 Lint commit messages with conventional commit messages
https://keisukeyamashita.github.io/commitlint-rs
Apache License 2.0
32 stars 8 forks source link

bump(deps): bump @astrojs/starlight from 0.12.0 to 0.13.0 in /web #227

Closed dependabot[bot] closed 11 months ago

dependabot[bot] commented 11 months ago

Bumps @astrojs/starlight from 0.12.0 to 0.13.0.

Release notes

Sourced from @​astrojs/starlight's releases.

@​astrojs/starlight@​0.13.0

Minor Changes

  • #1023 a3b80f7 Thanks @​kevinzunigacuellar! - Respect the trailingSlash and build.format Astro options when creating Starlight navigation links.

    ⚠️ Potentially breaking change: This change will cause small changes in link formatting for most sites. These are unlikely to break anything, but if you care about link formatting, you may want to change some Astro settings.

    If you want to preserve Starlight’s previous behavior, set trailingSlash: 'always' in your astro.config.mjs:

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

    export default defineConfig({ trailingSlash: 'always', integrations: [ starlight({ // ... }), ], });

  • #742 c6a4bcb Thanks @​hippotastic! - Adds Expressive Code as Starlight’s default code block renderer

    ⚠️ Potentially breaking change: This addition changes how Markdown code blocks are rendered. By default, Starlight will now use Expressive Code. If you were already customizing how code blocks are rendered and don't want to use the features provided by Expressive Code, you can preserve the previous behavior by setting the new config option expressiveCode to false.

    If you had previously added Expressive Code manually to your Starlight project, you can now remove the manual set-up in astro.config.mjs:

    • Move your configuration to Starlight’s new expressiveCode option.
    • Remove the astro-expressive-code integration.

    For example:

    import starlight from '@astrojs/starlight';
    import { defineConfig } from 'astro/config';
    - import expressiveCode from 'astro-expressive-code';
    

    export default defineConfig({ integrations: [

    • expressiveCode({
    • themes: ['rose-pine'],
      
    • }), starlight({ title: 'My docs',

... (truncated)

Changelog

Sourced from @​astrojs/starlight's changelog.

0.13.0

Minor Changes

  • #1023 a3b80f7 Thanks @​kevinzunigacuellar! - Respect the trailingSlash and build.format Astro options when creating Starlight navigation links.

    ⚠️ Potentially breaking change: This change will cause small changes in link formatting for most sites. These are unlikely to break anything, but if you care about link formatting, you may want to change some Astro settings.

    If you want to preserve Starlight’s previous behavior, set trailingSlash: 'always' in your astro.config.mjs:

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

    export default defineConfig({ trailingSlash: 'always', integrations: [ starlight({ // ... }), ], });

  • #742 c6a4bcb Thanks @​hippotastic! - Adds Expressive Code as Starlight’s default code block renderer

    ⚠️ Potentially breaking change: This addition changes how Markdown code blocks are rendered. By default, Starlight will now use Expressive Code. If you were already customizing how code blocks are rendered and don't want to use the features provided by Expressive Code, you can preserve the previous behavior by setting the new config option expressiveCode to false.

    If you had previously added Expressive Code manually to your Starlight project, you can now remove the manual set-up in astro.config.mjs:

    • Move your configuration to Starlight’s new expressiveCode option.
    • Remove the astro-expressive-code integration.

    For example:

    import starlight from '@astrojs/starlight';
    import { defineConfig } from 'astro/config';
    - import expressiveCode from 'astro-expressive-code';
    

    export default defineConfig({ integrations: [

    • expressiveCode({
    • themes: ['rose-pine'],
      
    • }), starlight({

... (truncated)

Commits


Dependabot compatibility score

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 this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
dependabot[bot] commented 11 months ago

Superseded by #231.