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.

Sign up for GitHub

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

Jump to bottom

fix(deps): update astro integrations #56

Open
wants to merge 1 commit into
base: main
Choose a base branch
from
Open

fix(deps): update astro integrations #56

wants to merge 1 commit into from

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Jan 24, 2023 •
edited

Mend Renovate

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
@astrojs/image (source) ^0.12.1 -> ^0.18.0 age adoption passing confidence
@astrojs/mdx (source) ^0.14.0 -> ^0.19.0 age adoption passing confidence

Release Notes

withastro/astro (@​astrojs/image)

v0.18.0

Compare Source

Minor Changes

v0.17.3

Compare Source

Patch Changes

v0.17.2

Compare Source

Patch Changes

v0.17.1

Compare Source

Patch Changes

v0.17.0

Compare Source

Minor Changes
  • #​7260 39403c32f Thanks @​natemoo-re! - Unflags support for output: 'hybrid' mode, which enables pre-rendering by default. The additional experimental.hybridOutput flag can be safely removed from your configuration.
Patch Changes

v0.16.9

Compare Source

Patch Changes

v0.16.8

Compare Source

Patch Changes

v0.16.7

Compare Source

Patch Changes

v0.16.6

Compare Source

Patch Changes

v0.16.5

Compare Source

Patch Changes

  • #​6714 ff0430786 Thanks @​bluwy! - Add build.assetsPrefix option for CDN support. If set, all Astro-generated asset links will be prefixed with it. For example, setting it to https://cdn.example.com would generate https://cdn.example.com/_astro/penguin.123456.png links.

    Also adds import.meta.env.ASSETS_PREFIX environment variable that can be used to manually create asset links not handled by Astro.

  • Updated dependencies [489dd8d69, a1a4f45b5, a1108e037, 8b88e4cf1, d54cbe413, 4c347ab51, ff0430786, 2f2e572e9, 7116c021a]:

    • astro@2.2.0

v0.16.4

Compare Source

Patch Changes

v0.16.3

Compare Source

Patch Changes

v0.16.2

Compare Source

Patch Changes

  • #​6548 4685f5554 Thanks @​matthewp! - Use base64 encoded modules for Squoosh integration

    This moves @astrojs/image to use base64 encoded versions of the Squoosh wasm modules. This is in order to prevent breakage in SSR environments where your files are moved around. This will fix usage of the integration in Netlify.

  • Updated dependencies [9caf2a9cc, d338b6f74]:

    • astro@2.1.6

v0.16.1

Compare Source

Patch Changes

v0.16.0

Compare Source

Minor Changes
Patch Changes

v0.15.1

Compare Source

Patch Changes

v0.15.0

Compare Source

Minor Changes
Patch Changes

v0.14.1

Compare Source

Patch Changes

v0.14.0

Compare Source

Minor Changes
Patch Changes

v0.13.1

Compare Source

Patch Changes

v0.13.0

Compare Source

Minor Changes

  • #​5584 9963c6e4d & #​5842 c4b0cb8bf Thanks @​wulinsheng123 and @​natemoo-re! - Breaking Change: client assets are built to an _astro directory in the build output directory. Previously these were built to various locations, including assets/, chunks/ and the root of build output.

    You can control this location with the new build configuration option named assets.

  • #​5707 5eba34fcc Thanks @​bluwy! - Remove astro:build:start backwards compatibility code

  • #​5806 7572f7402 Thanks @​matthewp! - Make astro a peerDependency of integrations

    This marks astro as a peerDependency of several packages that are already getting major version bumps. This is so we can more properly track the dependency between them and what version of Astro they are being used with.

Patch Changes
withastro/astro (@​astrojs/mdx)

v0.19.7

Compare Source

Patch Changes

v0.19.6

Compare Source

Patch Changes
  • #​7185 339529fc8 Thanks @​bholmesdev! - Bring back improved style and script handling across content collection files. This addresses bugs found in a previous release to @astrojs/markdoc.

v0.19.5

Compare Source

Patch Changes

v0.19.4

Compare Source

Patch Changes
  • #​7178 57e65d247 Thanks @​bholmesdev! - Fix: revert Markdoc asset bleed changes. Production build issues were discovered that deserve a different fix.

v0.19.3

Compare Source

Patch Changes
  • #​6758 f558a9e20 Thanks @​bholmesdev! - Improve style and script handling across content collection files. This addresses style bleed present in @astrojs/markdoc v0.1.0

v0.19.2

Compare Source

Patch Changes

v0.19.1

Compare Source

Patch Changes

v0.19.0

Compare Source

Minor Changes
Patch Changes

v0.18.4

Compare Source

Patch Changes

v0.18.3

Compare Source

Patch Changes

v0.18.2

Compare Source

Patch Changes

v0.18.1

Compare Source

Patch Changes

v0.18.0

Compare Source

Minor Changes

  • #​6344 694918a56 Thanks @​Princesseuh! - Add a new experimental flag (experimental.assets) to enable our new core Assets story.

    This unlocks a few features:

    • A new built-in image component and JavaScript API to transform and optimize images.
    • Relative images with automatic optimization in Markdown.
    • Support for validating assets using content collections.
    • and more!

    See Assets (Experimental) on our docs site for more information on how to use this feature!

  • #​6213 afbbc4d5b Thanks @​Princesseuh! - Updated compilation settings to disable downlevelling for Node 14

Patch Changes

v0.17.2

Compare Source

Patch Changes

v0.17.0

Compare Source

Minor Changes
  • #​6253 0049fda62 Thanks @​bluwy! - Support rehype plugins that inject namespaced attributes. This introduces a breaking change if you use custom components for HTML elements, where the prop passed to the component will be normal HTML casing, e.g. class instead of className, and xlink:href instead of xlinkHref.

v0.16.2

Compare Source

Patch Changes

v0.16.1

Compare Source

Patch Changes

v0.16.0

Compare Source

Minor Changes
  • #​6050 2ab32b59e Thanks @​bholmesdev! - Fix: load syntax highlighters after MDX remark plugins. This keeps MDX consistent with Astro's markdown behavior.
Patch Changes

v0.15.2

Compare Source

Patch Changes

v0.15.1

Compare Source

Patch Changes

v0.15.0

Compare Source

Minor Changes

  • #​5684 a9c292026 Thanks @​bholmesdev! - Refine Markdown and MDX configuration options for ease-of-use. & #​5769 93e633922 Thanks @​bholmesdev! - Introduce a smartypants flag to opt-out of Astro's default SmartyPants plugin.

    • Markdown

      • Replace the extendDefaultPlugins option with a gfm boolean and a smartypants boolean. These are enabled by default, and can be disabled to remove GitHub-Flavored Markdown and SmartyPants.

      • Ensure GitHub-Flavored Markdown and SmartyPants are applied whether or not custom remarkPlugins or rehypePlugins are configured. If you want to apply custom plugins and remove Astro's default plugins, manually set gfm: false and smartypants: false in your config.

    • Migrate extendDefaultPlugins to gfm and smartypants

      You may have disabled Astro's built-in plugins (GitHub-Flavored Markdown and Smartypants) with the extendDefaultPlugins option. This has now been split into 2 flags to disable each plugin individually:

      • markdown.gfm to disable GitHub-Flavored Markdown
      • markdown.smartypants to disable SmartyPants
      // astro.config.mjs
import { defineConfig } from 'astro/config';

export default defineConfig({
  markdown: {
-   extendDefaultPlugins: false,
+   smartypants: false,
+   gfm: false,
  }
});

      Additionally, applying remark and rehype plugins no longer disables gfm and smartypants. You will need to opt-out manually by setting gfm and smartypants to false.

    • MDX

      • Support all Markdown configuration options (except drafts) from your MDX integration config. This includes syntaxHighlighting and shikiConfig options to further customize the MDX renderer.

      • Simplify extendPlugins to an extendMarkdownConfig option. MDX options will default to their equivalent in your Markdown config. By setting extendMarkdownConfig to false, you can "eject" to set your own syntax highlighting, plugins, and more.

    • Migrate MDX's extendPlugins to extendMarkdownConfig

      You may have used the extendPlugins option to manage plugin defaults in MDX. This has been replaced by 3 flags:

      • extendMarkdownConfig (true by default) to toggle Markdown config inheritance. This replaces the extendPlugins: 'markdown' option.
      • gfm (true by default) and smartypants (true by default) to toggle GitHub-Flavored Markdown and SmartyPants in MDX. This replaces the extendPlugins: 'defaults' option.

  • #​5687 e2019be6f Thanks @​bholmesdev! - Give remark and rehype plugins access to user frontmatter via frontmatter injection. This means data.astro.frontmatter is now the complete Markdown or MDX document's frontmatter, rather than an empty object.

    This allows plugin authors to modify existing frontmatter, or compute new properties based on other properties. For example, say you want to compute a full image URL based on an imageSrc slug in your document frontmatter:

    export function remarkInjectSocialImagePlugin() {
  return function (tree, file) {
    const { frontmatter } = file.data.astro;
    frontmatter.socialImageSrc = new URL(frontmatter.imageSrc, 'https://my-blog.com/').pathname;
  };
}

    When using Content Collections, you can access this modified frontmatter using the remarkPluginFrontmatter property returned when rendering an entry.

    Migration instructions

    Plugin authors should now check for user frontmatter when applying defaults.

    For example, say a remark plugin wants to apply a default title if none is present. Add a conditional to check if the property

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.

  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

@renovate renovate bot force-pushed the renovate/astro-integrations branch 2 times, most recently from e7cf08f to 75ed3ac Compare February 1, 2023 15:45
@renovate renovate bot force-pushed the renovate/astro-integrations branch 2 times, most recently from 654395b to 17e9e33 Compare February 17, 2023 01:22
@renovate renovate bot force-pushed the renovate/astro-integrations branch from 17e9e33 to 7692663 Compare March 7, 2023 20:38
@renovate renovate bot force-pushed the renovate/astro-integrations branch 4 times, most recently from c809db3 to b646a3c Compare April 23, 2023 06:36
@renovate renovate bot force-pushed the renovate/astro-integrations branch from b646a3c to 9517830 Compare May 10, 2023 05:56
@renovate renovate bot force-pushed the renovate/astro-integrations branch from 9517830 to 2348f11 Compare May 10, 2023 06:14
@renovate renovate bot changed the title chore(deps): update astro integrations fix(deps): update astro integrations May 10, 2023
@renovate renovate bot force-pushed the renovate/astro-integrations branch from 2348f11 to 215be3b Compare May 10, 2023 06:23
@renovate renovate bot force-pushed the renovate/astro-integrations branch from 215be3b to a6f8ca9 Compare June 6, 2023 16:25
@renovate renovate bot force-pushed the renovate/astro-integrations branch from a6f8ca9 to a7183ad Compare August 30, 2023 16:28
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers
No reviews
Assignees
No one assigned
Labels
dependencies
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.

None yet
0 participants