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

Update astro monorepo (major) #30

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

Update astro monorepo (major) #30

wants to merge 1 commit into from

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented May 3, 2024

Mend Renovate

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
@astrojs/sitemap (source) ^0.1.0 -> ^3.0.0 age adoption passing confidence
@astrojs/tailwind (source) ^0.1.0 -> ^5.0.0 age adoption passing confidence
astro (source) ^1.0.0-beta.4 -> ^4.0.0 age adoption passing confidence

Release Notes

withastro/astro (@​astrojs/sitemap)

v3.1.4

Compare Source

Patch Changes

v3.1.3

Compare Source

Patch Changes

v3.1.2

Compare Source

Patch Changes

v3.1.1

Compare Source

Patch Changes

v3.1.0

Compare Source

Minor Changes

  • #​9846 9b78c992750cdb99c40a89a00ea2a0d1c00877d7 Thanks @​ktym4a! - Adds a new configuration option prefix that allows you to change the default sitemap-*.xml file name.

    By default, running astro build creates both sitemap-index.xml and sitemap-0.xml in your output directory.

    To change the names of these files (e.g. to astrosite-index.xml and astrosite-0.xml), set the prefix option in your sitemap integration configuration:

    import { defineConfig } from 'astro/config';
import sitemap from '@​astrojs/sitemap';
export default defineConfig({
  site: 'https://example.com',
  integrations: [
    sitemap({
      prefix: 'astrosite-',
    }),
  ],
});

    This option is useful when Google Search Console is unable to fetch your default sitemap files, but can read renamed files.

v3.0.5

Compare Source

Patch Changes

v3.0.4

Compare Source

Patch Changes

v3.0.3

Compare Source

Patch Changes

v3.0.2

Compare Source

Patch Changes

v3.0.1

Compare Source

Patch Changes

v3.0.0

Compare Source

Major Changes

v2.0.2

Compare Source

Patch Changes

v2.0.1

Compare Source

Patch Changes

v2.0.0

Compare Source

Major Changes
  • #​7656 dd931a780 Thanks @​natemoo-re! - Sitemap only includes page routes (generated by .astro files) rather than all routes (pages, endpoints, or redirects). This behavior matches our existing documentation, but is a breaking change nonetheless.
Patch Changes

v1.4.0

Compare Source

Minor Changes

v1.3.3

Compare Source

Patch Changes

v1.3.2

Compare Source

Patch Changes

v1.3.1

Compare Source

Patch Changes

v1.3.0

Compare Source

Minor Changes

v1.2.2

Compare Source

Patch Changes

v1.2.1

Compare Source

Patch Changes

v1.2.0

Compare Source

Minor Changes

v1.1.0

Compare Source

Minor Changes

v1.0.1

Compare Source

Patch Changes

v1.0.0

Compare Source

Major Changes

v0.3.0

Compare Source

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

v0.2.6

Compare Source

Patch Changes

v0.2.5

Compare Source

Patch Changes

v0.2.4

Compare Source

Patch Changes

v0.2.3

Compare Source

Patch Changes
  • #​3723 52f75369 Thanks @​alextim! - fix: if serialize function returns undefined for the passed entry, such entry will be excluded from sitemap

v0.2.2

Compare Source

Patch Changes

v0.2.1

Compare Source

Patch Changes

v0.2.0

Compare Source

Minor Changes

  • #​3579 1031c06f Thanks @​alextim! - # Key features

    • Split up your large sitemap into multiple sitemaps by custom limit.
    • Ability to add sitemap specific attributes such as lastmod etc.
    • Final output customization via JS function.
    • Localization support.
    • Reliability: all config options are validated.

v0.1.2

Compare Source

Patch Changes

v0.1.1

Compare Source

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

v5.1.0

Compare Source

Minor Changes
Patch Changes

v5.0.4

Compare Source

Patch Changes

v5.0.3

Compare Source

Patch Changes

v5.0.2

Compare Source

Patch Changes

v5.0.1

Compare Source

Patch Changes

v5.0.0

Compare Source

Major Changes
Patch Changes

v4.0.0

Compare Source

Major Changes

  • #​7391 556fd694a Thanks @​bluwy! - Rename options config.path to configFile, and config.applyBaseStyles to applyBaseStyles. If you are using these options, you need to migrate to the new names.

    // astro.config.mjs
import { defineConfig } from 'astro/config';
import tailwind from '@​astrojs/tailwind';

export default defineConfig({
  integrations: [
    tailwind({
-      config: {
-        path: '...',
-        applyBaseStyles: true,
-      },
+      configFile: '...',
+      applyBaseStyles: true,
    }),
  ],
});

  • #​6724 3f1cb6b1a Thanks @​TomPichaud! - Let the tailwindcss PostCSS plugin load its config file itself. This changes the Tailwind config loading behaviour where it is loaded from process.cwd() instead of the project root.

    If your Tailwind config file is not located in the current working directory, you will need to configure the integration's configFile option to load from a specific path:

    // astro.config.mjs
import { defineConfig } from 'astro/config';
import tailwind from '@​astrojs/tailwind';
import { fileURLToPath } from 'url';

export default defineConfig({
  integrations: [
    tailwind({
      configFile: fileURLToPath(new URL('./tailwind.config.cjs', import.meta.url)),
    }),
  ],
});

    This change also requires a Tailwind config file to exist in your project as a fallback config is no longer provided. It is set up automatically during astro add tailwind, but if it does not exist, you can manually create a tailwind.config.cjs file in your project root:

    // tailwind.config.cjs
/** @​type {import('tailwindcss').Config} */
module.exports = {
  content: ['./src/**/*.{astro,html,js,jsx,md,mdx,svelte,ts,tsx,vue}'],
  theme: {
    extend: {},
  },
  plugins: [],
};
Patch Changes

v3.1.3

Compare Source

Patch Changes

v3.1.2

Compare Source

Patch Changes

v3.1.1

Compare Source

Patch Changes

v3.1.0

Compare Source

Minor Changes
Patch Changes

v3.0.1

Compare Source

Patch Changes

v3.0.0

Compare Source

Major Changes

  • #​5717 a3a7fc929 Thanks @​bluwy! - Remove style.postcss Astro config. Refactor Tailwind integration to configure through vite instead. Also disables autoprefixer in dev.

  • #​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

v2.1.3

Compare Source

Patch Changes

v2.1.2

Compare Source

Patch Changes

v2.1.1

Compare Source

Patch Changes

v2.1.0

Compare Source

Minor Changes

  • #​4947 a5e3ecc80 Thanks @​JuanM04! - ## HMR on config file changes

    New in this release is the ability for config changes to automatically reflect via HMR. Now when you edit your tsconfig.json or tailwind.config.js configs, the changes will reload automatically without the need to restart your dev server.

v2.0.2

Compare Source

Patch Changes

v2.0.1

Compare Source

Patch Changes

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 has been generated by Mend Renovate. View repository job log here.

@height Height
Copy link

height bot commented May 3, 2024

Link Height tasks by mentioning a task ID in the pull request title or commit messages, or description and comments with the keyword link (e.g. "Link T-123").

💡Tip: You can also use "Close T-X" to automatically close a task when the pull request is merged.

@stackblitz StackBlitz
Copy link

stackblitz bot commented May 3, 2024

Review PR in StackBlitz Codeflow Run & review this pull request in StackBlitz Codeflow.

@vercel Vercel
Copy link

vercel bot commented May 3, 2024 •
edited

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name Status Preview Comments Updated (UTC)
homeless-hacker ❌ Failed (Inspect) May 3, 2024 2:26am

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
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.

None yet
0 participants