search

osmbe / road-completion

Compare open-data road datasets to OpenStreetMap data
https://osmbe.github.io/road-completion/
MIT License
16 stars 3 forks source link

Bump cookie, @astrojs/svelte and astro in /report #492

Open dependabot[bot] opened 1 month ago

dependabot[bot] commented 1 month ago

Bumps cookie to 0.7.2 and updates ancestor dependencies cookie, @astrojs/svelte and astro. These dependencies need to be updated together.

Updates cookie from 0.5.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

0.6.0

  • Add partitioned option
Commits
Maintainer changes

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


Updates @astrojs/svelte from 2.2.0 to 5.7.2

Release notes

Sourced from @​astrojs/svelte's releases.

@​astrojs/svelte@​5.7.2

Patch Changes

@​astrojs/svelte@​5.7.1

Patch Changes

Changelog

Sourced from @​astrojs/svelte's changelog.

5.7.2

Patch Changes

5.7.1

Patch Changes

5.7.0

Minor Changes

  • #11490 6ad02b5 Thanks @​bluwy! - Bumps Svelte 5 peer dependency to ^5.0.0-next.190 and support the latest slots/snippets API

5.6.0

Minor Changes

  • #11234 4385bf7 Thanks @​ematipico! - Adds a new function called addServerRenderer to the Container API. Use this function to manually store renderers inside the instance of your container.

    This new function should be preferred when using the Container API in environments like on-demand pages:

    import type { APIRoute } from 'astro';
import { experimental_AstroContainer } from 'astro/container';
import reactRenderer from '@astrojs/react/server.js';
import vueRenderer from '@astrojs/vue/server.js';
import ReactComponent from '../components/button.jsx';
import VueComponent from '../components/button.vue';

    // MDX runtime is contained inside the Astro core
import mdxRenderer from 'astro/jsx/server.js';
    

    // In case you need to import a custom renderer
import customRenderer from '../renderers/customRenderer.js';
    

    export const GET: APIRoute = async (ctx) => {
const container = await experimental_AstroContainer.create();
container.addServerRenderer({ renderer: reactRenderer });
container.addServerRenderer({ renderer: vueRenderer });
container.addServerRenderer({ renderer: customRenderer });
// You can pass a custom name too
container.addServerRenderer({
name: 'customRenderer',
renderer: customRenderer,
});

... (truncated)

Commits


Updates astro from 2.9.6 to 4.16.1

Release notes

Sourced from astro's releases.

astro@4.16.1

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.

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>
</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.1</h2>
<h3>Patch Changes</h3>
<ul>
<li>
<p><a href="https://redirect.github.com/withastro/astro/pull/12177">#12177</a> <a href="https://github.com/withastro/astro/commit/a4ffbfaa5cb460c12bd486fd75e36147f51d3e5e"><code>a4ffbfa</code></a> Thanks <a href="https://github.com/matthewp"><code>@​matthewp</code></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">#12173</a> <a href="https://github.com/withastro/astro/commit/2d10de5f212323e6e19c7ea379826dcc18fe739c"><code>2d10de5</code></a> Thanks <a href="https://github.com/ematipico"><code>@​ematipico</code></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">#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.

... (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 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](https://github.com/osmbe/road-completion/network/alerts).