search

MatthiesenXYZ / astro-ghostcms

Easily migrate your Ghost Site to Astro, an Astro Integration that turns your Ghost server into a Headless CMS
https://astro-ghostcms.xyz/
MIT License
18 stars 3 forks source link

Bump the prod-dependencies group with 3 updates #107

Closed dependabot[bot] closed 4 months ago

dependabot[bot] commented 4 months ago

Bumps the prod-dependencies group with 3 updates: vite, astro and @matthiesenxyz/astro-gists.

Updates vite from 5.1.5 to 5.1.6

Changelog

Sourced from vite's changelog.

5.1.6 (2024-03-11)

  • chore(deps): update all non-major dependencies (#16131) (a862ecb), closes #16131
  • fix: check for publicDir before checking if it is a parent directory (#16046) (b6fb323), closes #16046
  • fix: escape single quote when relative base is used (#16060) (8f74ce4), closes #16060
  • fix: handle function property extension in namespace import (#16113) (f699194), closes #16113
  • fix: server middleware mode resolve (#16122) (8403546), closes #16122
  • fix(esbuild): update tsconfck to fix bug that could cause a deadlock (#16124) (fd9de04), closes #16124
  • fix(worker): hide "The emitted file overwrites" warning if the content is same (#16094) (60dfa9e), closes #16094
  • fix(worker): throw error when circular worker import is detected and support self referencing worker (eef9da1), closes #16103
  • style(utils): remove null check (#16112) (0d2df52), closes #16112
  • refactor(runtime): share more code between runtime and main bundle (#16063) (93be84e), closes #16063
Commits
  • 6f7466e release: v5.1.6
  • a862ecb chore(deps): update all non-major dependencies (#16131)
  • 8403546 fix: server middleware mode resolve (#16122)
  • b6fb323 fix: check for publicDir before checking if it is a parent directory (#16046)
  • fd9de04 fix(esbuild): update tsconfck to fix bug that could cause a deadlock (#16124)
  • f699194 fix: handle function property extension in namespace import (#16113)
  • 0d2df52 style(utils): remove null check (#16112)
  • eef9da1 fix(worker): throw error when circular worker import is detected and support ...
  • 60dfa9e fix(worker): hide "The emitted file overwrites" warning if the content is sam...
  • 93be84e refactor(runtime): share more code between runtime and main bundle (#16063)
  • Additional commits viewable in compare view


Updates astro from 4.4.13 to 4.5.0

Release notes

Sourced from astro's releases.

astro@4.5.0

Minor Changes

  • #10206 dc87214141e7f8406c0fdf6a7f425dad6dea6d3e Thanks @​lilnasy! - Allows middleware to run when a matching page or endpoint is not found. Previously, a pages/404.astro or pages/[...catch-all].astro route had to match to allow middleware. This is now not necessary.

    When a route does not match in SSR deployments, your adapter may show a platform-specific 404 page instead of running Astro's SSR code. In these cases, you may still need to add a 404.astro or fallback route with spread params, or use a routing configuration option if your adapter provides one.

  • #9960 c081adf998d30419fed97d8fccc11340cdc512e0 Thanks @​StandardGage! - Allows passing any props to the <Code /> component

  • #10102 e3f02f5fb1cf0dae3c54beb3a4af3dbf3b06abb7 Thanks @​bluwy! - Adds a new experimental.directRenderScript configuration option which provides a more reliable strategy to prevent scripts from being executed in pages where they are not used.

    This replaces the experimental.optimizeHoistedScript flag introduced in v2.10.4 to prevent unused components' scripts from being included in a page unexpectedly. That experimental option no longer exists and must be removed from your configuration, whether or not you enable directRenderScript:

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

    export default defineConfig({
experimental: {
    

      

    • 

        optimizeHoistedScript: true,

      

      • 

    

      

    • 

        directRenderScript: true

      
}
});

With experimental.directRenderScript configured, scripts are now directly rendered as declared in Astro files (including existing features like TypeScript, importing node_modules, and deduplicating scripts). You can also now conditionally render scripts in your Astro file.

However, this means scripts are no longer hoisted to the <head> and multiple scripts on a page are no longer bundled together. If you enable this option, you should check that all your <script> tags behave as expected.

This option will be enabled by default in Astro 5.0.

  • #10130 5a9528741fa98d017b269c7e4f013058028bdc5d Thanks @​bluwy! - Stabilizes markdown.shikiConfig.experimentalThemes as markdown.shikiConfig.themes. No behaviour changes are made to this option.

  • #10189 1ea0a25b94125e4f6f2ac82b42f638e22d7bdffd Thanks @​peng! - Adds the option to pass an object to build.assetsPrefix. This allows for the use of multiple CDN prefixes based on the target file type.

    When passing an object to build.assetsPrefix, you must also specify a fallback domain to be used for all other file types not specified.

    Specify a file extension as the key (e.g. 'js', 'png') and the URL serving your assets of that file type as the value:

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

    export default defineConfig({
build: {
assetsPrefix: {
js: 'https://js.cdn.example.com',
mjs: 'https://js.cdn.example.com', // if you have .mjs files, you must add a new entry like this
png: 'https://images.cdn.example.com',
fallback: 'https://generic.cdn.example.com',

    • ... (truncated)

    Changelog

    Sourced from astro's changelog.

    4.5.0

    Minor Changes

    • #10206 dc87214141e7f8406c0fdf6a7f425dad6dea6d3e Thanks @​lilnasy! - Allows middleware to run when a matching page or endpoint is not found. Previously, a pages/404.astro or pages/[...catch-all].astro route had to match to allow middleware. This is now not necessary.

      When a route does not match in SSR deployments, your adapter may show a platform-specific 404 page instead of running Astro's SSR code. In these cases, you may still need to add a 404.astro or fallback route with spread params, or use a routing configuration option if your adapter provides one.

    • #9960 c081adf998d30419fed97d8fccc11340cdc512e0 Thanks @​StandardGage! - Allows passing any props to the <Code /> component

    • #10102 e3f02f5fb1cf0dae3c54beb3a4af3dbf3b06abb7 Thanks @​bluwy! - Adds a new experimental.directRenderScript configuration option which provides a more reliable strategy to prevent scripts from being executed in pages where they are not used.

      This replaces the experimental.optimizeHoistedScript flag introduced in v2.10.4 to prevent unused components' scripts from being included in a page unexpectedly. That experimental option no longer exists and must be removed from your configuration, whether or not you enable directRenderScript:

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

      export default defineConfig({
experimental: {
      

        

      • 

          optimizeHoistedScript: true,

        

        • 

      

        

      • 

          directRenderScript: true

        
}
});

    With experimental.directRenderScript configured, scripts are now directly rendered as declared in Astro files (including existing features like TypeScript, importing node_modules, and deduplicating scripts). You can also now conditionally render scripts in your Astro file.

    However, this means scripts are no longer hoisted to the <head> and multiple scripts on a page are no longer bundled together. If you enable this option, you should check that all your <script> tags behave as expected.

    This option will be enabled by default in Astro 5.0.

  • #10130 5a9528741fa98d017b269c7e4f013058028bdc5d Thanks @​bluwy! - Stabilizes markdown.shikiConfig.experimentalThemes as markdown.shikiConfig.themes. No behaviour changes are made to this option.

  • #10189 1ea0a25b94125e4f6f2ac82b42f638e22d7bdffd Thanks @​peng! - Adds the option to pass an object to build.assetsPrefix. This allows for the use of multiple CDN prefixes based on the target file type.

    When passing an object to build.assetsPrefix, you must also specify a fallback domain to be used for all other file types not specified.

    Specify a file extension as the key (e.g. 'js', 'png') and the URL serving your assets of that file type as the value:

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

    export default defineConfig({
build: {
assetsPrefix: {
js: 'https://js.cdn.example.com',
mjs: 'https://js.cdn.example.com', // if you have .mjs files, you must add a new entry like this
png: 'https://images.cdn.example.com',

    • ... (truncated)

    Commits


    Updates @matthiesenxyz/astro-gists from 0.2.3 to 0.2.7

    Release notes

    Sourced from @​matthiesenxyz/astro-gists's releases.

    @​matthiesenxyz/astro-gists@​0.2.7

    Patch Changes

    • 4ce42d9: Bump dependencies:

      • vite from to
      • astro from to

    @​matthiesenxyz/astro-gists@​0.2.6

    Patch Changes

    • 18e132f: patch for css

    @​matthiesenxyz/astro-gists@​0.2.5

    Patch Changes

    • e500aeb: fix CSS issue with View Raw Button

    @​matthiesenxyz/astro-gists@​0.2.4

    Patch Changes

    • a6696ed: Readds a basic version of the theme system for now
    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
    changeset-bot[bot] commented 4 months ago

    🦋 Changeset detected

    Latest commit: 14c35eb4b715a71a960792d9c3e7fbcb3b1c850d

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

    This PR includes changesets to release 3 packages | Name | Type | | ------------------------------------------- | ----- | | @matthiesenxyz/starlight-ghostcms | Patch | | @matthiesenxyz/astro-ghostcms | Patch | | @matthiesenxyz/astro-ghostcms-rendercontent | 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

    Adammatthiesen commented 4 months ago

    @dependabot recreate

    dependabot[bot] commented 4 months ago

    Looks like these dependencies are up-to-date now, so this is no longer needed.