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.

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

build(deps-dev): bump astro from 4.5.18 to 4.16.1 in /landing #190

Closed

Conversation

dependabot[bot]
Copy link
Contributor

@dependabot dependabot bot commented on behalf of github Oct 14, 2024

Bumps astro from 4.5.18 to 4.16.1.

Release notes

Sourced from astro's releases.

[email protected]

Patch Changes

  • #12177 a4ffbfa Thanks @​matthewp! - Ensure we target scripts for execution in the router

    Using document.scripts is unsafe because if the application has a name="scripts" this will shadow the built-in document.scripts. Fix is to use getElementsByTagName to ensure we're only grabbing real scripts.

  • #12173 2d10de5 Thanks @​ematipico! - Fixes a bug where Astro Actions couldn't redirect to the correct pathname when there was a rewrite involved.

[email protected]

Minor Changes

  • #12039 710a1a1 Thanks @​ematipico! - Adds a markdown.shikiConfig.langAlias option that allows aliasing a non-supported code language to a known language. This is useful when the language of your code samples is not a built-in Shiki language, but you want your Markdown source to contain an accurate language while also displaying syntax highlighting.

    The following example configures Shiki to highlight cjs code blocks using the javascript syntax highlighter:

    import { defineConfig } from 'astro/config';
    export default defineConfig({
    markdown: {
    shikiConfig: {
    langAlias: {
    cjs: 'javascript',
    },
    },
    },
    });

    Then in your Markdown, you can use the alias as the language for a code block for syntax highlighting:

    ```cjs
    'use strict';
    function commonJs() {
    return 'I am a commonjs file';
    }
    </code></pre>
    </li>
    <li>
    <p><a href="https://redirect.github.com/withastro/astro/pull/11984">#11984</a> <a href="https://github.com/withastro/astro/commit/3ac2263ff6070136bec9cffb863c38bcc31ccdfe"><code>3ac2263</code></a> Thanks <a href="https://github.com/chaegumi"><code>@​chaegumi</code></a>! - Adds a new <code>build.concurreny</code> configuration option to specify the number of pages to build in parallel</p>
    <p><strong>In most cases, you should not change the default value of <code>1</code>.</strong></p>
    <p>Use this option only when other attempts to reduce the overall rendering time (e.g. batch or cache long running tasks like fetch calls or data access) are not possible or are insufficient.</p>
    <p>Use this option only if the refactors are not possible. If the number is set too high, the page rendering may slow down due to insufficient memory resources and because JS is single-threaded.</p>
    </li>
    </ul>
    <!-- raw HTML omitted -->
    </blockquote>
    <p>... (truncated)</p>
    </details>
    <details>
    <summary>Changelog</summary>
    <p><em>Sourced from <a href="https://github.com/withastro/astro/blob/main/packages/astro/CHANGELOG.md&quot;&gt;astro's changelog</a>.</em></p>
    <blockquote>
    <h2>4.16.1</h2>
    <h3>Patch Changes</h3>
    <ul>
    <li>
    <p><a href="https://redirect.github.com/withastro/astro/pull/12177&quot;&gt;#12177&lt;/a> <a href="https://github.com/withastro/astro/commit/a4ffbfaa5cb460c12bd486fd75e36147f51d3e5e&quot;&gt;&lt;code&gt;a4ffbfa&lt;/code&gt;&lt;/a> Thanks <a href="https://github.com/matthewp&quot;&gt;&lt;code&gt;@​matthewp&lt;/code&gt;&lt;/a>! - Ensure we target scripts for execution in the router</p>
    <p>Using <code>document.scripts</code> is unsafe because if the application has a <code>name=&quot;scripts&quot;</code> this will shadow the built-in <code>document.scripts</code>. Fix is to use <code>getElementsByTagName</code> to ensure we're only grabbing real scripts.</p>
    </li>
    <li>
    <p><a href="https://redirect.github.com/withastro/astro/pull/12173&quot;&gt;#12173&lt;/a> <a href="https://github.com/withastro/astro/commit/2d10de5f212323e6e19c7ea379826dcc18fe739c&quot;&gt;&lt;code&gt;2d10de5&lt;/code&gt;&lt;/a> Thanks <a href="https://github.com/ematipico&quot;&gt;&lt;code&gt;@​ematipico&lt;/code&gt;&lt;/a>! - Fixes a bug where Astro Actions couldn't redirect to the correct pathname when there was a rewrite involved.</p>
    </li>
    </ul>
    <h2>4.16.0</h2>
    <h3>Minor Changes</h3>
    <ul>
    <li>
    <p><a href="https://redirect.github.com/withastro/astro/pull/12039&quot;&gt;#12039&lt;/a> <a href="https://github.com/withastro/astro/commit/710a1a11f488ff6ed3da6d3e0723b2322ccfe27b&quot;&gt;&lt;code&gt;710a1a1&lt;/code&gt;&lt;/a> Thanks <a href="https://github.com/ematipico&quot;&gt;&lt;code&gt;@​ematipico&lt;/code&gt;&lt;/a>! - Adds a <code>markdown.shikiConfig.langAlias</code> option that allows <a href="https://shiki.style/guide/load-lang#custom-language-aliases&quot;&gt;aliasing a non-supported code language to a known language</a>. This is useful when the language of your code samples is not <a href="https://shiki.style/languages&quot;&gt;a built-in Shiki language</a>, but you want your Markdown source to contain an accurate language while also displaying syntax highlighting.</p>
    <p>The following example configures Shiki to highlight <code>cjs</code> code blocks using the <code>javascript</code> syntax highlighter:</p>
    <pre lang="js"><code>import { defineConfig } from 'astro/config';
    export default defineConfig({
    markdown: {
    shikiConfig: {
    langAlias: {
    cjs: 'javascript',
    },
    },
    },
    });
    </code></pre>
    <p>Then in your Markdown, you can use the alias as the language for a code block for syntax highlighting:</p>
    <pre lang="md"><code>```cjs
    'use strict';
    function commonJs() {
    return 'I am a commonjs file';
    }
    

  • #11984 3ac2263 Thanks @​chaegumi! - Adds a new build.concurreny configuration option to specify the number of pages to build in parallel

    In most cases, you should not change the default value of 1.

    Use this option only when other attempts to reduce the overall rendering time (e.g. batch or cache long running tasks like fetch calls or data access) are not possible or are insufficient.

... (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 <dependency name> 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)
    You can disable automated security fix PRs for this repo from the Security Alerts page.

@dependabot dependabot bot requested a review from elianiva as a code owner October 14, 2024 20:22
@dependabot dependabot bot added dependencies Pull requests that update a dependency file javascript Pull requests that update Javascript code labels Oct 14, 2024
Copy link
Contributor Author

dependabot bot commented on behalf of github Oct 27, 2024

Looks like astro is up-to-date now, so this is no longer needed.

@dependabot dependabot bot closed this Oct 27, 2024
@dependabot dependabot bot deleted the dependabot/npm_and_yarn/landing/astro-4.16.1 branch October 27, 2024 14:34
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
dependencies Pull requests that update a dependency file javascript Pull requests that update Javascript code
Projects
Status: Done
Development

Successfully merging this pull request may close these issues.

0 participants