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

[ci] release #6652

Merged
merged 1 commit into from
Mar 28, 2023
Merged

[ci] release #6652

merged 1 commit into from
Mar 28, 2023

Conversation

astrobot-houston
Copy link
Contributor

@astrobot-houston astrobot-houston commented Mar 24, 2023

This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to main, this PR will be updated.

Releases

@astrojs/markdoc@0.1.0

Minor Changes

  • #6653 7c439868a Thanks @bholmesdev! - Simplify Markdoc configuration with a new markdoc.config.mjs file. This lets you import Astro components directly to render as Markdoc tags and nodes, without the need for the previous components property. This new configuration also unlocks passing variables to your Markdoc from the Content component (see the new docs).

    Migration

    Move any existing Markdoc config from your astro.config to a new markdoc.config.mjs file at the root of your project. This should be applied as a default export, with the optional defineMarkdocConfig() helper for autocomplete in your editor.

    This example configures an aside Markdoc tag. Note that components should be imported and applied to the render attribute directly, instead of passing the name as a string:

    // markdoc.config.mjs
    import { defineMarkdocConfig } from '@astrojs/markdoc/config';
    import Aside from './src/components/Aside.astro';
    
    export default defineMarkdocConfig({
      tags: {
        aside: {
          render: Aside,
        },
      },
    });

    You should also remove the components prop from your Content components. Since components are imported into your config directly, this is no longer needed.

    ---
    - import Aside from '../components/Aside.astro';
    import { getEntryBySlug } from 'astro:content';
    
    const entry = await getEntryBySlug('docs', 'why-markdoc');
    const { Content } = await entry.render();
    ---
    
    <Content
    - components={{ Aside }}
    />

Patch Changes

@astrojs/partytown@1.2.0

Minor Changes

astro@2.1.8

Patch Changes

  • #6675 1f783e320 Thanks @matthewp! - Prevent frontmatter errors from crashing the dev server

  • #6688 2e92e9aa9 Thanks @JohannesKlauss! - Add a additional check for null on the req.body check in NodeApp.render.

  • #6578 adecda7d6 Thanks @wulinsheng123! - add new flag with open for dev and preview

  • #6680 386336441 Thanks @koriwi! - Invalidates cache when changing serviceEntryPoint

  • #6653 7c439868a Thanks @bholmesdev! - Simplify Markdoc configuration with a new markdoc.config.mjs file. This lets you import Astro components directly to render as Markdoc tags and nodes, without the need for the previous components property. This new configuration also unlocks passing variables to your Markdoc from the Content component (see the new docs).

    Migration

    Move any existing Markdoc config from your astro.config to a new markdoc.config.mjs file at the root of your project. This should be applied as a default export, with the optional defineMarkdocConfig() helper for autocomplete in your editor.

    This example configures an aside Markdoc tag. Note that components should be imported and applied to the render attribute directly, instead of passing the name as a string:

    // markdoc.config.mjs
    import { defineMarkdocConfig } from '@astrojs/markdoc/config';
    import Aside from './src/components/Aside.astro';
    
    export default defineMarkdocConfig({
      tags: {
        aside: {
          render: Aside,
        },
      },
    });

    You should also remove the components prop from your Content components. Since components are imported into your config directly, this is no longer needed.

    ---
    - import Aside from '../components/Aside.astro';
    import { getEntryBySlug } from 'astro:content';
    
    const entry = await getEntryBySlug('docs', 'why-markdoc');
    const { Content } = await entry.render();
    ---
    
    <Content
    - components={{ Aside }}
    />
  • #6639 25cd3e574 Thanks @tony-sull! - Fixes an attribute naming mismatch in the definition for elements in astro.JSX

  • #6353 4bf87c64f Thanks @wulinsheng123! - Throw better error when a dynamic endpoint without additional extensions is prerendered with undefined params.

  • #6643 fc0ed9c53 Thanks @Princesseuh! - Fix images not having the proper path when using base

create-astro@3.1.2

Patch Changes

@astrojs/image@0.16.3

Patch Changes

@github-actions github-actions bot added pkg: astro Related to the core `astro` package (scope) pkg: example Related to an example package (scope) pkg: svelte Related to Svelte (scope) pkg: vue Related to Vue (scope) pkg: integration Related to any renderer integration (scope) labels Mar 24, 2023
@github-actions github-actions bot force-pushed the changeset-release/main branch 11 times, most recently from 3de0133 to 0c0a585 Compare March 28, 2023 13:01
@bholmesdev
Copy link
Contributor

bholmesdev commented Mar 28, 2023

Really confused how Markdoc was bumped to 1.0 here. The changeset only suggests a minor, and astro core is a dev dependency + peer dependency only. @matthewp any ideas?

Fixed by setting a version in the peer dep! Thanks @bluwy 🙌

@github-actions github-actions bot added the pkg: create-astro Related to the `create-astro` package (scope) label Mar 28, 2023
@github-actions github-actions bot force-pushed the changeset-release/main branch 3 times, most recently from 43fa712 to 8037b65 Compare March 28, 2023 16:21
@bholmesdev bholmesdev merged commit af108e4 into main Mar 28, 2023
@bholmesdev bholmesdev deleted the changeset-release/main branch March 28, 2023 17:17
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
pkg: astro Related to the core `astro` package (scope) pkg: create-astro Related to the `create-astro` package (scope) pkg: example Related to an example package (scope) pkg: integration Related to any renderer integration (scope) pkg: svelte Related to Svelte (scope) pkg: vue Related to Vue (scope)
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants