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 (alpha) #11627

Merged
merged 1 commit into from
Aug 19, 2024
Merged

[ci] release (alpha) #11627

merged 1 commit into from
Aug 19, 2024

Conversation

astrobot-houston
Copy link
Contributor

@astrobot-houston astrobot-houston commented Aug 5, 2024

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 next, this PR will be updated.

⚠️⚠️⚠️⚠️⚠️⚠️

next is currently in pre mode so this branch has prereleases rather than normal releases. If you want to exit prereleases, run changeset pre exit on next.

⚠️⚠️⚠️⚠️⚠️⚠️

Releases

astro@5.0.0-alpha.0

Major Changes

  • #10742 b6fbdaa Thanks @ematipico! - The lowest version of Node supported by Astro is now Node v18.17.1 and higher.

  • #11715 d74617c Thanks @Princesseuh! - Refactor the exported types from the astro module. There should normally be no breaking changes, but if you relied on some previously deprecated types, these might now have been fully removed.

    In most cases, updating your code to move away from previously deprecated APIs in previous versions of Astro should be enough to fix any issues.

  • #11660 e90f559 Thanks @bluwy! - Fixes attribute rendering for non-boolean HTML attributes with boolean values to match proper attribute handling in browsers.

    Previously, non-boolean attributes may not have included their values when rendered to HTML. In Astro v5.0, the values are now explicitly rendered as ="true" or ="false"

    In the following .astro examples, only allowfullscreen is a boolean attribute:

    <!-- src/pages/index.astro --><!-- `allowfullscreen` is a boolean attribute -->
    <p allowfullscreen={true}></p>
    <p allowfullscreen={false}></p>
    
    <!-- `inherit` is *not* a boolean attribute -->
    <p inherit={true}></p>
    <p inherit={false}></p>
    
    <!-- `data-*` attributes are not boolean attributes -->
    <p data-light={true}></p>
    <p data-light={false}></p>

    Astro v5.0 now preserves the full data attribute with its value when rendering the HTML of non-boolean attributes:

      <p allowfullscreen></p>
      <p></p>
    
      <p inherit="true"></p>
    - <p inherit></p>
    + <p inherit="false"></p>
    
    - <p data-light></p>
    + <p data-light="true"></p>
    - <p></p>
    + <p data-light="false"></p>

    If you rely on attribute values, for example to locate elements or to conditionally render, update your code to match the new non-boolean attribute values:

    - el.getAttribute('inherit') === ''
    + el.getAttribute('inherit') === 'false'
    
    - el.hasAttribute('data-light')
    + el.dataset.light === 'true'
  • #11714 8a53517 Thanks @matthewp! - Remove support for functionPerRoute

    This change removes support for the functionPerRoute option both in Astro and @astrojs/vercel.

    This option made it so that each route got built as separate entrypoints so that they could be loaded as separate functions. The hope was that by doing this it would decrease the size of each function. However in practice routes use most of the same code, and increases in function size limitations made the potential upsides less important.

    Additionally there are downsides to functionPerRoute, such as hitting limits on the number of functions per project. The feature also never worked with some Astro features like i18n domains and request rewriting.

    Given this, the feature has been removed from Astro.

Patch Changes

@astrojs/vercel@8.0.0-alpha.0

Major Changes

  • #11714 8a53517 Thanks @matthewp! - Remove support for functionPerRoute

    This change removes support for the functionPerRoute option both in Astro and @astrojs/vercel.

    This option made it so that each route got built as separate entrypoints so that they could be loaded as separate functions. The hope was that by doing this it would decrease the size of each function. However in practice routes use most of the same code, and increases in function size limitations made the potential upsides less important.

    Additionally there are downsides to functionPerRoute, such as hitting limits on the number of functions per project. The feature also never worked with some Astro features like i18n domains and request rewriting.

    Given this, the feature has been removed from Astro.

Minor Changes

  • #11728 5ea02b1 Thanks @matthewp! - Deprecates the functionPerRoute option

    This option is now deprecated, and will be removed entirely in Astro v5.0. We suggest removing this option from your configuration as soon as you are able to:

    import { defineConfig } from 'astro/config';
    import vercel from '@astrojs/vercel/serverless';
    
    export default defineConfig({
      // ...
      output: 'server',
      adapter: vercel({
    -     functionPerRoute: true,
      }),
    });

Patch Changes

@astrojs/markdown-remark@6.0.0-alpha.0

Major Changes

  • #11661 83a2a64 Thanks @bluwy! - Renames the following CSS variables theme color token names to better align with the Shiki v1 defaults:

    • --astro-code-color-text => --astro-code-foreground
    • --astro-code-color-background => --astro-code-background

    You can perform a global find and replace in your project to migrate to the new token names.

create-astro@4.8.4-alpha.0

Patch Changes

@astrojs/markdoc@1.0.0-alpha.0

Patch Changes

@astrojs/mdx@4.0.0-alpha.0

Patch Changes

@astrojs/node@9.0.0-alpha.0

Patch Changes

@astrojs/svelte@6.0.0-alpha.0

Patch Changes

@astrojs/tailwind@6.0.0-alpha.0

Patch Changes

@astrojs/vue@5.0.0-alpha.0

Patch Changes

@github-actions github-actions bot added pkg: example Related to an example package (scope) pkg: astro Related to the core `astro` package (scope) labels Aug 5, 2024
@github-actions github-actions bot force-pushed the changeset-release/next branch from 07f5643 to 03d180a Compare August 6, 2024 09:24
@Princesseuh Princesseuh added the semver: major Change triggers a `major` release label Aug 6, 2024
Copy link
Member

@Princesseuh Princesseuh left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Woaw there partner, we're not quite ready for this just yet.

@Princesseuh Princesseuh changed the title [ci] release [ci] release (next) Aug 6, 2024
@astrobot-houston astrobot-houston changed the title [ci] release (next) [ci] release (beta) Aug 6, 2024
@github-actions github-actions bot force-pushed the changeset-release/next branch from 03d180a to 6ffc311 Compare August 6, 2024 09:34
@Princesseuh Princesseuh marked this pull request as draft August 6, 2024 09:36
@github-actions github-actions bot force-pushed the changeset-release/next branch 4 times, most recently from 7f674f8 to c336a71 Compare August 12, 2024 12:57
@astrobot-houston astrobot-houston changed the title [ci] release (beta) [ci] release (alpha) Aug 13, 2024
@github-actions github-actions bot force-pushed the changeset-release/next branch 11 times, most recently from 763e101 to 8d097b5 Compare August 19, 2024 14:33
@matthewp matthewp marked this pull request as ready for review August 19, 2024 16:36
@github-actions github-actions bot force-pushed the changeset-release/next branch from 8d097b5 to 0ff72df Compare August 19, 2024 18:00
@matthewp matthewp merged commit f239242 into next Aug 19, 2024
@matthewp matthewp deleted the changeset-release/next branch August 19, 2024 18:37
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: example Related to an example package (scope) semver: major Change triggers a `major` release
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants