google / scaaml

Apache License 2.0
130 stars 38 forks source link

Bump the npm_and_yarn group in /website with 2 updates #305

Closed dependabot[bot] closed 1 month ago

dependabot[bot] commented 1 month ago

Bumps the npm_and_yarn group in /website with 2 updates: cookie and astro.

Updates cookie from 0.6.0 to 0.7.2

Release notes

Sourced from cookie's releases.

v0.7.2

Fixed

  • Fix object assignment of hasOwnProperty (#177) bc38ffd

https://github.com/jshttp/cookie/compare/v0.7.1...v0.7.2

0.7.1

Fixed

  • Allow leading dot for domain (#174)
    • Although not permitted in the spec, some users expect this to work and user agents ignore the leading dot according to spec
  • Add fast path for serialize without options, use obj.hasOwnProperty when parsing (#172)

https://github.com/jshttp/cookie/compare/v0.7.0...v0.7.1

0.7.0

https://github.com/jshttp/cookie/compare/v0.6.0...v0.7.0

Commits
Maintainer changes

This version was pushed to npm by blakeembrey, a new releaser for cookie since your current version.


Updates astro from 4.15.4 to 4.16.0

Release notes

Sourced from astro's releases.

astro@4.16.0

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>
    <blockquote>
    <p>[!WARNING]
    This feature is stable and is not considered experimental. However, this feature is only intended to address difficult performance issues, and breaking changes may occur in a <a href="https://docs.astro.build/en/upgrade-astro/#semantic-versioning">minor release</a> to keep this option as performant as possible.</p>
    </blockquote>
    <pre lang="js"><code>// astro.config.mjs
    import { defineConfig } from 'astro';
    
    export default defineConfig({
      build: {
    </code></pre>
    </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">astro's changelog</a>.</em></p>
    <blockquote>
    <h2>4.16.0</h2>
    <h3>Minor Changes</h3>
    <ul>
    <li>
    <p><a href="https://redirect.github.com/withastro/astro/pull/12039">#12039</a> <a href="https://github.com/withastro/astro/commit/710a1a11f488ff6ed3da6d3e0723b2322ccfe27b"><code>710a1a1</code></a> Thanks <a href="https://github.com/ematipico"><code>@​ematipico</code></a>! - Adds a <code>markdown.shikiConfig.langAlias</code> option that allows <a href="https://shiki.style/guide/load-lang#custom-language-aliases">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">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.

    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.

    [!WARNING] This feature is stable and is not considered experimental. However, this feature is only intended to address difficult performance issues, and breaking changes may occur in a minor release to keep this option as performant as possible.

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

    export default defineConfig({

... (truncated)

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 You can disable automated security fix PRs for this repo from the [Security Alerts page](https://github.com/google/scaaml/network/alerts).
coveralls commented 1 month ago

Pull Request Test Coverage Report for Build 11273978747

Details


Totals Coverage Status
Change from base Build 11273959442: 0.0%
Covered Lines: 2202
Relevant Lines: 2736

💛 - Coveralls