LAPIS icon indicating copy to clipboard operation
LAPIS copied to clipboard

Published 20 hours ago • verified publisher icon GenSpectrum

chore(lapis-docs): bump the minorandpatch group across 1 directory with 7 updates

Open dependabot[bot] opened this issue 6 months ago • 1 comments

Bumps the minorandpatch group with 7 updates in the /lapis-docs directory:

Package From To
@astrojs/react 3.6.0 3.6.2
@astrojs/starlight 0.25.3 0.25.4
astro 4.12.2 4.13.3
tailwindcss 3.4.7 3.4.9
@astrojs/check 0.8.3 0.9.2
@playwright/test 1.45.3 1.46.0
@types/node 22.0.0 22.2.0

Updates @astrojs/react from 3.6.0 to 3.6.2

Release notes

Sourced from @​astrojs/react's releases.

@​astrojs/react@​3.6.2

Patch Changes

  • #11624 7adb350 Thanks @​bluwy! - Prevents throwing errors when checking if a component is a React component in runtime

@​astrojs/react@​3.6.1

Patch Changes

  • #11571 1c3265a Thanks @​bholmesdev! - BREAKING CHANGE to the experimental Actions API only. Install the latest @astrojs/react integration as well if you're using React 19 features.

    Make .safe() the default return value for actions. This means { data, error } will be returned when calling an action directly. If you prefer to get the data while allowing errors to throw, chain the .orThrow() modifier.

    import { actions } from 'astro:actions';

    // Before
const { data, error } = await actions.like.safe();
// After
const { data, error } = await actions.like();
    

    // Before
const newLikes = await actions.like();
// After
const newLikes = await actions.like.orThrow();

    Migration

    To migrate your existing action calls:

    • Remove .safe from existing safe action calls
    • Add .orThrow to existing unsafe action calls

  • #11570 84189b6 Thanks @​bholmesdev! - BREAKING CHANGE to the experimental Actions API only. Install the latest @astrojs/react integration as well if you're using React 19 features.

    Updates the Astro Actions fallback to support action={actions.name} instead of using getActionProps(). This will submit a form to the server in zero-JS scenarios using a search parameter:

    ---
import { actions } from 'astro:actions';
---

    <form action={actions.logOut}>
<!--output: action="?_astroAction=logOut"-->
<button>Log Out</button>
</form>

    You may also construct form action URLs using string concatenation, or by using the URL() constructor, with the an action's .queryString property:

... (truncated)

Changelog

Sourced from @​astrojs/react's changelog.

3.6.2

Patch Changes

  • #11624 7adb350 Thanks @​bluwy! - Prevents throwing errors when checking if a component is a React component in runtime

3.6.1

Patch Changes

  • #11571 1c3265a Thanks @​bholmesdev! - BREAKING CHANGE to the experimental Actions API only. Install the latest @astrojs/react integration as well if you're using React 19 features.

    Make .safe() the default return value for actions. This means { data, error } will be returned when calling an action directly. If you prefer to get the data while allowing errors to throw, chain the .orThrow() modifier.

    import { actions } from 'astro:actions';

    // Before
const { data, error } = await actions.like.safe();
// After
const { data, error } = await actions.like();
    

    // Before
const newLikes = await actions.like();
// After
const newLikes = await actions.like.orThrow();

    Migration

    To migrate your existing action calls:

    • Remove .safe from existing safe action calls
    • Add .orThrow to existing unsafe action calls

  • #11570 84189b6 Thanks @​bholmesdev! - BREAKING CHANGE to the experimental Actions API only. Install the latest @astrojs/react integration as well if you're using React 19 features.

    Updates the Astro Actions fallback to support action={actions.name} instead of using getActionProps(). This will submit a form to the server in zero-JS scenarios using a search parameter:

    ---
import { actions } from 'astro:actions';
---

    <form action={actions.logOut}>
<!--output: action="?_astroAction=logOut"-->
<button>Log Out</button>
</form>

... (truncated)

Commits

Updates @astrojs/starlight from 0.25.3 to 0.25.4

Release notes

Sourced from @​astrojs/starlight's releases.

@​astrojs/starlight@​0.25.4

Patch Changes

  • #2155 8bed886 Thanks @​delucis! - Improves page load performance on slower devices

  • #2167 9ac7725 Thanks @​delucis! - Fixes an issue detecting the built-in locale when running Starlight in a web container environment on Firefox

  • #2166 4f12049 Thanks @​delucis! - Updates @astrojs/mdx, @astrojs/sitemap, astro-expressive-code, unified, and vfile dependencies to the latest version

Changelog

Sourced from @​astrojs/starlight's changelog.

0.25.4

Patch Changes

  • #2155 8bed886 Thanks @​delucis! - Improves page load performance on slower devices

  • #2167 9ac7725 Thanks @​delucis! - Fixes an issue detecting the built-in locale when running Starlight in a web container environment on Firefox

  • #2166 4f12049 Thanks @​delucis! - Updates @astrojs/mdx, @astrojs/sitemap, astro-expressive-code, unified, and vfile dependencies to the latest version

Commits

Updates astro from 4.12.2 to 4.13.3

Release notes

Sourced from astro's releases.

[email protected]

Patch Changes

  • #11653 32be549 Thanks @​florian-lefebvre! - Updates astro:env docs to reflect current developments and usage guidance

  • #11658 13b912a Thanks @​bholmesdev! - Fixes orThrow() type when calling an Action without an input validator.

  • #11603 f31d466 Thanks @​bholmesdev! - Improves user experience when render an Action result from a form POST request:

    • Removes "Confirm post resubmission?" dialog when refreshing a result.
    • Removes the ?_astroAction=NAME flag when a result is rendered.

    Also improves the DX of directing to a new route on success. Actions will now redirect to the route specified in your action string on success, and redirect back to the previous page on error. This follows the routing convention of established backend frameworks like Laravel.

    For example, say you want to redirect to a /success route when actions.signup succeeds. You can add /success to your action string like so:

    <form method="POST" action={'/success' + actions.signup}></form>
    • On success, Astro will redirect to /success.
    • On error, Astro will redirect back to the current page.

    You can retrieve the action result from either page using the Astro.getActionResult() function.

    Note on security

    This uses a temporary cookie to forward the action result to the next page. The cookie will be deleted when that page is rendered.

    ⚠ The action result is not encrypted. In general, we recommend returning minimal data from an action handler to a) avoid leaking sensitive information, and b) avoid unexpected render issues once the temporary cookie is deleted. For example, a login function may return a user's session id to retrieve from your Astro frontmatter, rather than the entire user object.

[email protected]

Patch Changes

  • #11648 589d351 Thanks @​bholmesdev! - Fixes unexpected error when refreshing a POST request from a form using Actions.

  • #11600 09ec2ca Thanks @​ArmandPhilippot! - Deprecates getEntryBySlug and getDataEntryById functions exported by astro:content in favor of getEntry.

  • #11593 81d7150 Thanks @​bholmesdev! - Adds support for Date(), Map(), and Set() from action results. See devalue for a complete list of supported values.

    Also fixes serialization exceptions when deploying Actions with edge middleware on Netlify and Vercel.

  • #11617 196092a Thanks @​abubakriz! - Fix toolbar audit incorrectly flagging images as above the fold.

  • #11634 2716f52 Thanks @​bholmesdev! - Fixes internal server error when calling an Astro Action without arguments on Vercel.

  • #11628 9aaf58c Thanks @​madbook! - Ensures consistent CSS chunk hashes across different environments

[email protected]

Patch Changes

... (truncated)

Changelog

Sourced from astro's changelog.

4.13.3

Patch Changes

  • #11653 32be549 Thanks @​florian-lefebvre! - Updates astro:env docs to reflect current developments and usage guidance

  • #11658 13b912a Thanks @​bholmesdev! - Fixes orThrow() type when calling an Action without an input validator.

  • #11603 f31d466 Thanks @​bholmesdev! - Improves user experience when render an Action result from a form POST request:

    • Removes "Confirm post resubmission?" dialog when refreshing a result.
    • Removes the ?_astroAction=NAME flag when a result is rendered.

    Also improves the DX of directing to a new route on success. Actions will now redirect to the route specified in your action string on success, and redirect back to the previous page on error. This follows the routing convention of established backend frameworks like Laravel.

    For example, say you want to redirect to a /success route when actions.signup succeeds. You can add /success to your action string like so:

    <form method="POST" action={'/success' + actions.signup}></form>
    • On success, Astro will redirect to /success.
    • On error, Astro will redirect back to the current page.

    You can retrieve the action result from either page using the Astro.getActionResult() function.

    Note on security

    This uses a temporary cookie to forward the action result to the next page. The cookie will be deleted when that page is rendered.

    ⚠ The action result is not encrypted. In general, we recommend returning minimal data from an action handler to a) avoid leaking sensitive information, and b) avoid unexpected render issues once the temporary cookie is deleted. For example, a login function may return a user's session id to retrieve from your Astro frontmatter, rather than the entire user object.

4.13.2

Patch Changes

  • #11648 589d351 Thanks @​bholmesdev! - Fixes unexpected error when refreshing a POST request from a form using Actions.

  • #11600 09ec2ca Thanks @​ArmandPhilippot! - Deprecates getEntryBySlug and getDataEntryById functions exported by astro:content in favor of getEntry.

  • #11593 81d7150 Thanks @​bholmesdev! - Adds support for Date(), Map(), and Set() from action results. See devalue for a complete list of supported values.

    Also fixes serialization exceptions when deploying Actions with edge middleware on Netlify and Vercel.

  • #11617 196092a Thanks @​abubakriz! - Fix toolbar audit incorrectly flagging images as above the fold.

  • #11634 2716f52 Thanks @​bholmesdev! - Fixes internal server error when calling an Astro Action without arguments on Vercel.

  • #11628 9aaf58c Thanks @​madbook! - Ensures consistent CSS chunk hashes across different environments

... (truncated)

Commits

Updates tailwindcss from 3.4.7 to 3.4.9

Release notes

Sourced from tailwindcss's releases.

v3.4.9

Fixed

  • No longer warns when broad glob patterns are detecting vendor folders

v3.4.8

Fixed

  • Fix minification when using nested CSS (#14105)
  • Warn when broad glob patterns are used in the content configuration (#14140)
Changelog

Sourced from tailwindcss's changelog.

[3.4.9] - 2024-08-08

Fixed

  • No longer warns when broad glob patterns are detecting vendor folders

[3.4.8] - 2024-08-07

Fixed

  • Fix minification when using nested CSS (#14105)
  • Warn when broad glob patterns are used in the content configuration (#14140)
Commits

Updates @astrojs/check from 0.8.3 to 0.9.2

Release notes

Sourced from @​astrojs/check's releases.

@​astrojs/check@​0.9.2

Patch Changes

  • e8e18a8: Fixes an issue where errors inside script and style tags could be offset by a few characters when multi bytes characters were present in the file
  • Updated dependencies [e8e18a8]
    • @​astrojs/language-server@​2.13.2

@​astrojs/check@​0.9.1

Patch Changes

  • cc94bef: Revert a change to top-level returns that could prevent the return types of functions from being correct in certain cases
  • Updated dependencies [cc94bef]
    • @​astrojs/language-server@​2.13.1

@​astrojs/check@​0.9.0

Minor Changes

  • b65d6b4: Adds support for SCSS and LESS intellisense inside style tags

Patch Changes

  • Updated dependencies [3a60f00]
  • Updated dependencies [b65d6b4]
    • @​astrojs/language-server@​2.13.0
Changelog

Sourced from @​astrojs/check's changelog.

0.9.2

Patch Changes

  • e8e18a8: Fixes an issue where errors inside script and style tags could be offset by a few characters when multi bytes characters were present in the file
  • Updated dependencies [e8e18a8]
    • @​astrojs/language-server@​2.13.2

0.9.1

Patch Changes

  • cc94bef: Revert a change to top-level returns that could prevent the return types of functions from being correct in certain cases
  • Updated dependencies [cc94bef]
    • @​astrojs/language-server@​2.13.1

0.9.0

Minor Changes

  • b65d6b4: Adds support for SCSS and LESS intellisense inside style tags

Patch Changes

  • Updated dependencies [3a60f00]
  • Updated dependencies [b65d6b4]
    • @​astrojs/language-server@​2.13.0
Commits

Updates @playwright/test from 1.45.3 to 1.46.0

Release notes

Sourced from @​playwright/test's releases.

v1.46.0

TLS Client Certificates

Playwright now allows to supply client-side certificates, so that server can verify them, as specified by TLS Client Authentication.

When client certificates are specified, all browser traffic is routed through a proxy that establishes the secure TLS connection, provides client certificates to the server and validates server certificates.

The following snippet sets up a client certificate for https://example.com:

import { defineConfig } from '@playwright/test';

export default defineConfig({

// ...

use: {

clientCertificates: [{

origin: 'https://example.com',

certPath: './cert.pem',

keyPath: './key.pem',

passphrase: 'mysecretpassword',

}],

},

// ...

});

You can also provide client certificates to a particular test project or as a parameter of browser.newContext() and apiRequest.newContext().

--only-changed cli option

New CLI option --only-changed allows to only run test files that have been changed since the last git commit or from a specific git "ref".

# Only run test files with uncommitted changes
npx playwright test --only-changed

Only run test files changed relative to the "main" branch


npx playwright test --only-changed=main

Component Testing: New router fixture

This release introduces an experimental router fixture to intercept and handle network requests in component testing. There are two ways to use the router fixture:

  • Call router.route(url, handler) that behaves similarly to page.route().
  • Call router.use(handlers) and pass MSW library request handlers to it.

Here is an example of reusing your existing MSW handlers in the test.

</tr></table>

... (truncated)

Commits
  • 99a3631 chore: mark v1.46 (#32013)
  • 929fef3 cherry-pick(#32012): chore(lint): bump Microsoft.CodeAnalysis for linting cod...
  • cf31aa8 cherry-pick(#32008): chore(client-certificates): rewrite error for unsupporte...
  • ed9b4d9 cherry-pick(#32007): fix(client-certificates): report error to the browser if...
  • fca1fa0 cherry-pick(#31973): chore: run client-certificate tests in service mode
  • ff11273 cherry-pick(#32010): docs: release notes for 1.46 update
  • 4953ac3 cherry-pick(#31975): chore: remove bright counter from sidebar tab se… (#31976)
  • 4c66f8a cherry-pick(#31970): fix(trace): do not place expect into unfinished … (#31974)
  • deba37b cherry-pick(#31960): feat(ui mode): linkify attachment names and content (#31...
  • 2cfe733 cherry-pick(#31961): fix(trace-viewer): make 'hide route actions' work for .NET
  • Additional commits viewable in compare view

Updates @types/node from 22.0.0 to 22.2.0

Commits

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 <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
  • @dependabot ignore <dependency name> major version will close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself)
  • @dependabot ignore <dependency name> minor version will close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself)
  • @dependabot ignore <dependency name> will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself)
  • @dependabot unignore <dependency name> will remove all of the ignore conditions of the specified dependency
  • @dependabot unignore <dependency name> <ignore condition> will remove the ignore condition of the specified dependency and ignore conditions

dependabot[bot] avatar Aug 12 '24 19:08 dependabot[bot]