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

[ci] release #3972

Merged
merged 1 commit into from
Jul 26, 2022
Merged

[ci] release #3972

merged 1 commit into from
Jul 26, 2022

Conversation

astrobot-houston
Copy link
Contributor

@astrobot-houston astrobot-houston commented Jul 19, 2022 •
edited

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

astro@1.0.0-rc.1

Minor Changes

  • #4015 6fd161d76 Thanks @matthewp! - New output configuration option

    This change introduces a new "output target" configuration option (output). Setting the output target lets you decide the format of your final build, either:

    • "static" (default): A static site. Your final build will be a collection of static assets (HTML, CSS, JS) that you can deploy to any static site host.
    • "server": A dynamic server application. Your final build will be an application that will run in a hosted server environment, generating HTML dynamically for different requests.

    If output is omitted from your config, the default value "static" will be used.

    When using the "server" output target, you must also include a runtime adapter via the adapter configuration. An adapter will adapt your final build to run on the deployed platform of your choice (Netlify, Vercel, Node.js, Deno, etc).

    To migrate: No action is required for most users. If you currently define an adapter, you will need to also add output: 'server' to your config file to make it explicit that you are building a server. Here is an example of what that change would look like for someone deploying to Netlify:

    import { defineConfig } from 'astro/config';
import netlify from '@astrojs/netlify/functions';

export default defineConfig({
  adapter: netlify(),
+ output: 'server',
});

  • #4018 0cc6ede36 Thanks @okikio! - Support for 404 and 500 pages in SSR

  • #3992 ccae43142 Thanks @matthewp! - Removes warnings for integrations/ssr

  • #3973 5a23483ef Thanks @matthewp! - Adds support for Astro.clientAddress

    The new Astro.clientAddress property allows you to get the IP address of the requested user.

    <div>Your address { Astro.clientAddress }</div>

    This property is only available when building for SSR, and only if the adapter you are using supports providing the IP address. If you attempt to access the property in a SSG app it will throw an error.

  • #3570 04070c0c1 Thanks @matthewp! - Bump to Vite 3!

  • #4016 00fab4ce1 Thanks @bholmesdev! - The use of components and JSX expressions in Markdown are no longer supported by default.

    For long term support, migrate to the @astrojs/mdx integration for MDX support (including .mdx pages!).

    Not ready to migrate to MDX? Add the legacy flag to your Astro config to re-enable the previous Markdown support.

    // https://astro.build/config
export default defineConfig({
  legacy: {
    astroFlavoredMarkdown: true,
  },
});

  • #3986 bccd88f0e Thanks @matthewp! - Move the Markdown component to its own package

    This change moves the Markdown component into its own package where it will be maintained separately. All that needs to change from a user's perspective is the import statement:

    ---
import { Markdown } from 'astro/components';
---

    Becomes:

    ---
import Markdown from '@astrojs/markdown-component';
---

Patch Changes

@astrojs/cloudflare@0.3.0

Minor Changes

  • #4015 6fd161d76 Thanks @matthewp! - New output configuration option

    This change introduces a new "output target" configuration option (output). Setting the output target lets you decide the format of your final build, either:

    • "static" (default): A static site. Your final build will be a collection of static assets (HTML, CSS, JS) that you can deploy to any static site host.
    • "server": A dynamic server application. Your final build will be an application that will run in a hosted server environment, generating HTML dynamically for different requests.

    If output is omitted from your config, the default value "static" will be used.

    When using the "server" output target, you must also include a runtime adapter via the adapter configuration. An adapter will adapt your final build to run on the deployed platform of your choice (Netlify, Vercel, Node.js, Deno, etc).

    To migrate: No action is required for most users. If you currently define an adapter, you will need to also add output: 'server' to your config file to make it explicit that you are building a server. Here is an example of what that change would look like for someone deploying to Netlify:

    import { defineConfig } from 'astro/config';
import netlify from '@astrojs/netlify/functions';

export default defineConfig({
  adapter: netlify(),
+ output: 'server',
});

  • #4018 0cc6ede36 Thanks @okikio! - Support for 404 and 500 pages in SSR

  • #3973 5a23483ef Thanks @matthewp! - Adds support for Astro.clientAddress

    The new Astro.clientAddress property allows you to get the IP address of the requested user.

    <div>Your address { Astro.clientAddress }</div>

    This property is only available when building for SSR, and only if the adapter you are using supports providing the IP address. If you attempt to access the property in a SSG app it will throw an error.

@astrojs/deno@0.2.0

Minor Changes

  • #4015 6fd161d76 Thanks @matthewp! - New output configuration option

    This change introduces a new "output target" configuration option (output). Setting the output target lets you decide the format of your final build, either:

    • "static" (default): A static site. Your final build will be a collection of static assets (HTML, CSS, JS) that you can deploy to any static site host.
    • "server": A dynamic server application. Your final build will be an application that will run in a hosted server environment, generating HTML dynamically for different requests.

    If output is omitted from your config, the default value "static" will be used.

    When using the "server" output target, you must also include a runtime adapter via the adapter configuration. An adapter will adapt your final build to run on the deployed platform of your choice (Netlify, Vercel, Node.js, Deno, etc).

    To migrate: No action is required for most users. If you currently define an adapter, you will need to also add output: 'server' to your config file to make it explicit that you are building a server. Here is an example of what that change would look like for someone deploying to Netlify:

    import { defineConfig } from 'astro/config';
import netlify from '@astrojs/netlify/functions';

export default defineConfig({
  adapter: netlify(),
+ output: 'server',
});

  • #3973 5a23483ef Thanks @matthewp! - Adds support for Astro.clientAddress

    The new Astro.clientAddress property allows you to get the IP address of the requested user.

    <div>Your address { Astro.clientAddress }</div>

    This property is only available when building for SSR, and only if the adapter you are using supports providing the IP address. If you attempt to access the property in a SSG app it will throw an error.

@astrojs/image@0.2.0

Minor Changes

  • #4015 6fd161d76 Thanks @matthewp! - New output configuration option

    This change introduces a new "output target" configuration option (output). Setting the output target lets you decide the format of your final build, either:

    • "static" (default): A static site. Your final build will be a collection of static assets (HTML, CSS, JS) that you can deploy to any static site host.
    • "server": A dynamic server application. Your final build will be an application that will run in a hosted server environment, generating HTML dynamically for different requests.

    If output is omitted from your config, the default value "static" will be used.

    When using the "server" output target, you must also include a runtime adapter via the adapter configuration. An adapter will adapt your final build to run on the deployed platform of your choice (Netlify, Vercel, Node.js, Deno, etc).

    To migrate: No action is required for most users. If you currently define an adapter, you will need to also add output: 'server' to your config file to make it explicit that you are building a server. Here is an example of what that change would look like for someone deploying to Netlify:

    import { defineConfig } from 'astro/config';
import netlify from '@astrojs/netlify/functions';

export default defineConfig({
  adapter: netlify(),
+ output: 'server',
});

  • #3570 04070c0c1 Thanks @matthewp! - Bump to Vite 3!

  • #4013 ef9345767 Thanks @tony-sull! - - Fixes two bugs that were blocking SSR support when deployed to a hosting service

    • The built-in sharp service now automatically rotates images based on EXIF data

Patch Changes

@astrojs/mdx@0.3.0

Minor Changes

Patch Changes

@astrojs/netlify@0.5.0

Minor Changes

  • #4015 6fd161d76 Thanks @matthewp! - New output configuration option

    This change introduces a new "output target" configuration option (output). Setting the output target lets you decide the format of your final build, either:

    • "static" (default): A static site. Your final build will be a collection of static assets (HTML, CSS, JS) that you can deploy to any static site host.
    • "server": A dynamic server application. Your final build will be an application that will run in a hosted server environment, generating HTML dynamically for different requests.

    If output is omitted from your config, the default value "static" will be used.

    When using the "server" output target, you must also include a runtime adapter via the adapter configuration. An adapter will adapt your final build to run on the deployed platform of your choice (Netlify, Vercel, Node.js, Deno, etc).

    To migrate: No action is required for most users. If you currently define an adapter, you will need to also add output: 'server' to your config file to make it explicit that you are building a server. Here is an example of what that change would look like for someone deploying to Netlify:

    import { defineConfig } from 'astro/config';
import netlify from '@astrojs/netlify/functions';

export default defineConfig({
  adapter: netlify(),
+ output: 'server',
});

  • #4018 0cc6ede36 Thanks @okikio! - Support for 404 and 500 pages in SSR

  • #3973 5a23483ef Thanks @matthewp! - Adds support for Astro.clientAddress

    The new Astro.clientAddress property allows you to get the IP address of the requested user.

    <div>Your address { Astro.clientAddress }</div>

    This property is only available when building for SSR, and only if the adapter you are using supports providing the IP address. If you attempt to access the property in a SSG app it will throw an error.

@astrojs/node@0.2.0

Minor Changes

  • #4015 6fd161d76 Thanks @matthewp! - New output configuration option

    This change introduces a new "output target" configuration option (output). Setting the output target lets you decide the format of your final build, either:

    • "static" (default): A static site. Your final build will be a collection of static assets (HTML, CSS, JS) that you can deploy to any static site host.
    • "server": A dynamic server application. Your final build will be an application that will run in a hosted server environment, generating HTML dynamically for different requests.

    If output is omitted from your config, the default value "static" will be used.

    When using the "server" output target, you must also include a runtime adapter via the adapter configuration. An adapter will adapt your final build to run on the deployed platform of your choice (Netlify, Vercel, Node.js, Deno, etc).

    To migrate: No action is required for most users. If you currently define an adapter, you will need to also add output: 'server' to your config file to make it explicit that you are building a server. Here is an example of what that change would look like for someone deploying to Netlify:

    import { defineConfig } from 'astro/config';
import netlify from '@astrojs/netlify/functions';

export default defineConfig({
  adapter: netlify(),
+ output: 'server',
});

  • #3973 5a23483ef Thanks @matthewp! - Adds support for Astro.clientAddress

    The new Astro.clientAddress property allows you to get the IP address of the requested user.

    <div>Your address { Astro.clientAddress }</div>

    This property is only available when building for SSR, and only if the adapter you are using supports providing the IP address. If you attempt to access the property in a SSG app it will throw an error.

Patch Changes

@astrojs/sitemap@0.3.0

Minor Changes

  • #4015 6fd161d76 Thanks @matthewp! - New output configuration option

    This change introduces a new "output target" configuration option (output). Setting the output target lets you decide the format of your final build, either:

    • "static" (default): A static site. Your final build will be a collection of static assets (HTML, CSS, JS) that you can deploy to any static site host.
    • "server": A dynamic server application. Your final build will be an application that will run in a hosted server environment, generating HTML dynamically for different requests.

    If output is omitted from your config, the default value "static" will be used.

    When using the "server" output target, you must also include a runtime adapter via the adapter configuration. An adapter will adapt your final build to run on the deployed platform of your choice (Netlify, Vercel, Node.js, Deno, etc).

    To migrate: No action is required for most users. If you currently define an adapter, you will need to also add output: 'server' to your config file to make it explicit that you are building a server. Here is an example of what that change would look like for someone deploying to Netlify:

    import { defineConfig } from 'astro/config';
import netlify from '@astrojs/netlify/functions';

export default defineConfig({
  adapter: netlify(),
+ output: 'server',
});

Patch Changes

@astrojs/svelte@0.5.0

Minor Changes

Patch Changes

@astrojs/vercel@0.3.0

Minor Changes

  • #4015 6fd161d76 Thanks @matthewp! - New output configuration option

    This change introduces a new "output target" configuration option (output). Setting the output target lets you decide the format of your final build, either:

    • "static" (default): A static site. Your final build will be a collection of static assets (HTML, CSS, JS) that you can deploy to any static site host.
    • "server": A dynamic server application. Your final build will be an application that will run in a hosted server environment, generating HTML dynamically for different requests.

    If output is omitted from your config, the default value "static" will be used.

    When using the "server" output target, you must also include a runtime adapter via the adapter configuration. An adapter will adapt your final build to run on the deployed platform of your choice (Netlify, Vercel, Node.js, Deno, etc).

    To migrate: No action is required for most users. If you currently define an adapter, you will need to also add output: 'server' to your config file to make it explicit that you are building a server. Here is an example of what that change would look like for someone deploying to Netlify:

    import { defineConfig } from 'astro/config';
import netlify from '@astrojs/netlify/functions';

export default defineConfig({
  adapter: netlify(),
+ output: 'server',
});

  • #4018 0cc6ede36 Thanks @okikio! - Support for 404 and 500 pages in SSR

  • #3973 5a23483ef Thanks @matthewp! - Adds support for Astro.clientAddress

    The new Astro.clientAddress property allows you to get the IP address of the requested user.

    <div>Your address { Astro.clientAddress }</div>

    This property is only available when building for SSR, and only if the adapter you are using supports providing the IP address. If you attempt to access the property in a SSG app it will throw an error.

  • #4020 1666fdb4c Thanks @JuanM04! - Removed requirement for ENABLE_VC_BUILD=1, since Build Output v3 is now stable. Learn more.

@astrojs/vue@0.5.0

Minor Changes

@astrojs/markdown-component@0.2.0

Minor Changes

  • #4016 00fab4ce1 Thanks @bholmesdev! - The use of components and JSX expressions in Markdown are no longer supported by default.

    For long term support, migrate to the @astrojs/mdx integration for MDX support (including .mdx pages!).

    Not ready to migrate to MDX? Add the legacy flag to your Astro config to re-enable the previous Markdown support.

    // https://astro.build/config
export default defineConfig({
  legacy: {
    astroFlavoredMarkdown: true,
  },
});

  • #3986 bccd88f0e Thanks @matthewp! - Move the Markdown component to its own package

    This change moves the Markdown component into its own package where it will be maintained separately. All that needs to change from a user's perspective is the import statement:

    ---
import { Markdown } from 'astro/components';
---

    Becomes:

    ---
import Markdown from '@astrojs/markdown-component';
---

@astrojs/markdown-remark@0.13.0

Minor Changes

  • ba11b3399 Thanks @RafidMuhymin! - fixed generated slugs in markdown that ends with a dash

  • #4016 00fab4ce1 Thanks @bholmesdev! - The use of components and JSX expressions in Markdown are no longer supported by default.

    For long term support, migrate to the @astrojs/mdx integration for MDX support (including .mdx pages!).

    Not ready to migrate to MDX? Add the legacy flag to your Astro config to re-enable the previous Markdown support.

    // https://astro.build/config
export default defineConfig({
  legacy: {
    astroFlavoredMarkdown: true,
  },
});

  • #4031 6e27a5fdc Thanks @natemoo-re! - BREAKING Renamed Markdown utility function getHeaders() to getHeadings().

Patch Changes

  • #4008 399d7e269 Thanks @bholmesdev! - Avoid parsing JSX, components, and Astro islands when using "plain" md mode. This brings markdown.mode: 'md' in-line with our docs description.

create-astro@0.14.2

Patch Changes

@astrojs/lit@0.3.2

Patch Changes

@astrojs/partytown@0.1.9

Patch Changes

@astrojs/prefetch@0.0.6

Patch Changes

@astrojs/tailwind@0.2.5

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) feat: markdown Related to Markdown (scope) labels Jul 19, 2022
FredKSchott
FredKSchott requested changes Jul 19, 2022
View reviewed changes
Copy link
Member

@FredKSchott FredKSchott left a comment •
edited

Choose a reason for hiding this comment

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

DO NOT MERGE: BLOCKING RELEASE WHILE VITE 3 BAKES

@github-actions github-actions bot force-pushed the changeset-release/main branch 21 times, most recently from 0f318c6 to 33541d0 Compare July 21, 2022 16:33
@natemoo-re natemoo-re mentioned this pull request Jul 21, 2022
Closed
20 tasks
@github-actions github-actions bot force-pushed the changeset-release/main branch 6 times, most recently from 1821ce5 to 86eee68 Compare July 22, 2022 23:06
@natemoo-re natemoo-re mentioned this pull request Jul 23, 2022
Merged
@github-actions github-actions bot force-pushed the changeset-release/main branch 12 times, most recently from f5f38f6 to 3a9f616 Compare July 25, 2022 21:19
@github-actions github-actions bot added pkg: create-astro Related to the `create-astro` package (scope) pkg: lit Related to Lit (scope) labels Jul 26, 2022
@github-actions github-actions bot force-pushed the changeset-release/main branch 4 times, most recently from 3c19ade to c71fc9d Compare July 26, 2022 13:01
@FredKSchott FredKSchott merged commit d790eab into main Jul 26, 2022
@FredKSchott FredKSchott deleted the changeset-release/main branch July 26, 2022 13:58
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@FredKSchott FredKSchott FredKSchott approved these changes

Assignees
No one assigned
Labels
feat: markdown Related to Markdown (scope) 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: lit Related to Lit (scope) pkg: svelte Related to Svelte (scope) pkg: vue Related to Vue (scope)
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.

None yet
2 participants
@astrobot-houston @FredKSchott