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

Bump the npm_and_yarn group with 3 updates #195

Closed

Conversation

dependabot[bot]
Copy link
Contributor

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

Bumps the npm_and_yarn group with 3 updates: vite, astro and rollup.

Updates vite from 5.1.6 to 5.1.8

Changelog

Sourced from vite's changelog.

5.1.8 (2024-09-19)

5.1.7 (2024-03-24)

Commits

Updates astro from 4.5.6 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

Updates rollup from 4.12.1 to 4.24.0

Release notes

Sourced from rollup's releases.

v4.24.0

4.24.0

2024-10-02

Features

  • Support preserving and transpiling JSX syntax (#5668)

Pull Requests

v4.23.0

4.23.0

2024-10-01

Features

  • Collect all emitted names and originalFileNames for assets (#5686)

Pull Requests

v4.22.5

4.22.5

2024-09-27

Bug Fixes

  • Allow parsing of certain unicode characters again (#5674)

Pull Requests

v4.22.4

4.22.4

2024-09-21

Bug Fixes

... (truncated)

Changelog

Sourced from rollup's changelog.

4.24.0

2024-10-02

Features

  • Support preserving and transpiling JSX syntax (#5668)

Pull Requests

4.23.0

2024-10-01

Features

  • Collect all emitted names and originalFileNames for assets (#5686)

Pull Requests

4.22.5

2024-09-27

Bug Fixes

  • Allow parsing of certain unicode characters again (#5674)

Pull Requests

4.22.4

2024-09-21

Bug Fixes

  • Fix a vulnerability in generated code that affects IIFE, UMD and CJS bundles when run in a browser context (#5671)

Pull Requests

... (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 <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
  • @dependabot ignore <dependency name> 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 <dependency name> 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 <dependency name> 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 <dependency name> will remove all of the ignore conditions of the specified dependency
  • @dependabot unignore <dependency name> <ignore condition> 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.

Bumps the npm_and_yarn group with 3 updates: [vite](https://github.com/vitejs/vite/tree/HEAD/packages/vite), [astro](https://github.com/withastro/astro/tree/HEAD/packages/astro) and [rollup](https://github.com/rollup/rollup).


Updates `vite` from 5.1.6 to 5.1.8
- [Release notes](https://github.com/vitejs/vite/releases)
- [Changelog](https://github.com/vitejs/vite/blob/v5.1.8/packages/vite/CHANGELOG.md)
- [Commits](https://github.com/vitejs/vite/commits/v5.1.8/packages/vite)

Updates `astro` from 4.5.6 to 4.16.1
- [Release notes](https://github.com/withastro/astro/releases)
- [Changelog](https://github.com/withastro/astro/blob/main/packages/astro/CHANGELOG.md)
- [Commits](https://github.com/withastro/astro/commits/[email protected]/packages/astro)

Updates `rollup` from 4.12.1 to 4.24.0
- [Release notes](https://github.com/rollup/rollup/releases)
- [Changelog](https://github.com/rollup/rollup/blob/master/CHANGELOG.md)
- [Commits](rollup/rollup@v4.12.1...v4.24.0)

---
updated-dependencies:
- dependency-name: vite
  dependency-type: direct:production
  dependency-group: npm_and_yarn
- dependency-name: astro
  dependency-type: direct:production
  dependency-group: npm_and_yarn
- dependency-name: rollup
  dependency-type: indirect
  dependency-group: npm_and_yarn
...

Signed-off-by: dependabot[bot] <[email protected]>
@dependabot dependabot bot added the dependencies Pull requests that update a dependency file label Oct 14, 2024
Copy link

changeset-bot bot commented Oct 14, 2024

🦋 Changeset detected

Latest commit: 7024c2b

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 2 packages
Name Type
@matthiesenxyz/astro-ghostcms Patch
@matthiesenxyz/starlight-ghostcms Patch

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

Signed-off-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
@Adammatthiesen Adammatthiesen deleted the dependabot/npm_and_yarn/npm_and_yarn-00fa39e9cf branch October 14, 2024 23:41
Copy link
Contributor Author

dependabot bot commented on behalf of github Oct 14, 2024

This pull request was built based on a group rule. Closing it will not ignore any of these versions in future pull requests.

To ignore these dependencies, configure ignore rules in dependabot.yml

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
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant