Bump astro from 4.9.3 to 4.10.0

dependabot[bot] commented 1 month ago

Bumps astro from 4.9.3 to 4.10.0.

Release notes

astro@4.10.0

Minor Changes
#10974 2668ef9 Thanks @florian-lefebvre! - Adds experimental support for the astro:env API.

The astro:env API lets you configure a type-safe schema for your environment variables, and indicate whether they should be available on the server or the client. Import and use your defined variables from the appropriate /client or /server module:
---
import { PUBLIC_APP_ID } from 'astro:env/client';
import { PUBLIC_API_URL, getSecret } from 'astro:env/server';
const API_TOKEN = getSecret('API_TOKEN');
const data = await fetch(${PUBLIC_API_URL}/users, {
method: 'POST',
headers: {
'Content-Type': 'application/json',
Authorization: Bearer ${API_TOKEN},
},
body: JSON.stringify({ appId: PUBLIC_APP_ID }),
});
To define the data type and properties of your environment variables, declare a schema in your Astro config in experimental.env.schema. The envField helper allows you define your variable as a string, number, or boolean and pass properties in an object:
// astro.config.mjs
import { defineConfig, envField } from 'astro/config';
export default defineConfig({
experimental: {
env: {
schema: {
PUBLIC_API_URL: envField.string({ context: 'client', access: 'public', optional: true }),
PUBLIC_PORT: envField.number({ context: 'server', access: 'public', default: 4321 }),
API_SECRET: envField.string({ context: 'server', access: 'secret' }),
},
},
},
});
There are three kinds of environment variables, determined by the combination of context (client or server) and access (private or public) settings defined in your env.schema:
Public client variables: These variables end up in both your final client and server bundles, and can be accessed from both client and server through the astro:env/client module:
import { PUBLIC_API_URL } from 'astro:env/client';

... (truncated)

Changelog

Sourced from astro's changelog.

4.10.0

Minor Changes
#10974 2668ef9 Thanks @florian-lefebvre! - Adds experimental support for the astro:env API.

The astro:env API lets you configure a type-safe schema for your environment variables, and indicate whether they should be available on the server or the client. Import and use your defined variables from the appropriate /client or /server module:
---
import { PUBLIC_APP_ID } from 'astro:env/client';
import { PUBLIC_API_URL, getSecret } from 'astro:env/server';
const API_TOKEN = getSecret('API_TOKEN');
const data = await fetch(${PUBLIC_API_URL}/users, {
method: 'POST',
headers: {
'Content-Type': 'application/json',
Authorization: Bearer ${API_TOKEN},
},
body: JSON.stringify({ appId: PUBLIC_APP_ID }),
});
To define the data type and properties of your environment variables, declare a schema in your Astro config in experimental.env.schema. The envField helper allows you define your variable as a string, number, or boolean and pass properties in an object:
// astro.config.mjs
import { defineConfig, envField } from 'astro/config';
export default defineConfig({
experimental: {
env: {
schema: {
PUBLIC_API_URL: envField.string({ context: 'client', access: 'public', optional: true }),
PUBLIC_PORT: envField.number({ context: 'server', access: 'public', default: 4321 }),
API_SECRET: envField.string({ context: 'server', access: 'secret' }),
},
},
},
});
There are three kinds of environment variables, determined by the combination of context (client or server) and access (private or public) settings defined in your env.schema:
Public client variables: These variables end up in both your final client and server bundles, and can be accessed from both client and server through the astro:env/client module:
import { PUBLIC_API_URL } from 'astro:env/client';

... (truncated)

Commits

48d5309 [ci] release (#11186)
97fbe93 fix: merge userConfig inside getViteConfig (#11194)
a64428d [ci] format
6e29a17 Make Astro.url in format: 'preserve' match dev (#11191)
58b10a0 Fix throw AstroUserError in mdx (#11192)
4ad1ce2 [ci] format
1529428 [docs] format error messages (#11188)
db71177 [ci] format
04b6421 [docs] formatting for astro:env (#11187)
d03160a [ci] format
Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot show ignore conditions` will show all of the ignore conditions of the specified dependency - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

netlify[bot] commented 1 month ago

Deploy Preview for poetic-rolypoly-6d1495 failed. Why did it fail? →

Name	Link
Latest commit	2e8a7011906833dbb8c80052094a540ae2e54bf3
Latest deploy log	https://app.netlify.com/sites/poetic-rolypoly-6d1495/deploys/6663bc1bce6f35000840e8ae

netlify[bot] commented 1 month ago

Deploy Preview for food-market-web-app ready!

Name	Link
Latest commit	2e8a7011906833dbb8c80052094a540ae2e54bf3
Latest deploy log	https://app.netlify.com/sites/food-market-web-app/deploys/6663bc1b51e18800088f24da
Deploy Preview	https://deploy-preview-7--food-market-web-app.netlify.app
Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.
Lighthouse	1 paths audited Performance: 85 Accessibility: 100 Best Practices: 92 SEO: 91 PWA: - View the detailed breakdown and full score reports

To edit notification comments on pull requests, go to your Netlify site configuration.

dependabot[bot] commented 1 month ago

OK, I won't notify you again about this release, but will get in touch when a new version is available. If you'd rather skip all updates until the next major or minor version, let me know by commenting @dependabot ignore this major version or @dependabot ignore this minor version. You can also ignore all major, minor, or patch releases for a dependency by adding an ignore condition with the desired update_types to your config file.

If you change your mind, just re-open this PR and I'll resolve any conflicts on it.

github-actions[bot] commented 1 month ago

Your database schema is up-to-date.

github-actions[bot] commented 1 month ago

Your database schema is up-to-date.

vc-summer-2024-captstone-web / food-market-web-app