chore(deps): update all non-major dependencies #761

renovate · 2024-07-03T17:01:16Z

This PR contains the following updates:

Package	Change	Type	Update
@biomejs/biome (source)	`1.8.3` -> `1.9.0`	devDependencies	minor
astro (source)	`4.11.3` -> `4.15.6`	dependencies	minor
shipyard	`0.6.2` -> `0.7.0`	workspace.dependencies	minor
skia-safe	`0.75.0` -> `0.78.0`	workspace.dependencies	minor
tailwindcss (source)	`3.4.4` -> `3.4.11`	dependencies	patch

Release Notes

biomejs/biome (@biomejs/biome)

`v1.9.0`

Compare Source

Analyzer

Implement the semantic model for CSS. Contributed by @togami2864

CLI

New features

Add --graphql-linter-enabled option, to control whether the linter should be enabled or not for GraphQL files. Contributed by @ematipico
New EXPERIMENTAL search command. The search command allows you to search a Biome project using GritQL syntax.

GritQL is a powerful language that lets you do structural searches on your codebase. This means that trivia such as whitespace or even the type of strings quotes used will be ignored in your search query. It also has many features for querying the structure of your code, making it much more elegant for searching code than regular expressions.

While we believe this command may already be useful to users in some situations (especially when integrated in the IDE extensions!), we also had an ulterior motive for adding this command: We intend to utilize GritQL for our plugin efforts, and by allowing our users to try it out in a first iteration, we hope to gain insight in the type of queries you want to do, as well as the bugs we need to focus on.

For now, the search command is explicitly marked as EXPERIMENTAL, since many bugs remain. Keep this in mind when you try it out, and please let us know your issues!

Note: GritQL escapes code snippets using backticks, but most shells interpret backticks as command invocations. To avoid this, it's best to put single quotes around your Grit queries.
```
biome search '`console.log($message)`' # find all `console.log` invocations
```
Contributed by @arendjr and @BackupMiles

The option --max-diagnostics now accept a none value, which lifts the limit of diagnostics shown. Contributed by @ematipico

Add a new reporter --reporter=gitlab, that emits diagnostics for using the GitLab Code Quality report.

[
  {
    "description": "Use === instead of ==. == is only allowed when comparing against `null`",
    "check_name": "lint/suspicious/noDoubleEquals",
    "fingerprint": "6143155163249580709",
    "severity": "critical",
    "location": {
      "path": "main.ts",
      "lines": {
        "begin": 4
      }
    }
  }
]

Contributed by @NiclasvanEyk

Add new options to the lsp-proxy and start commands:
- --log-path: a directory where to store the daemon logs. The commands also accepts the environment variable BIOME_LOG_PATH.
- --log-prefix-name: a prefix that's added to the file name of the logs. It defaults to server.log. The commands also accepts the environment variable BIOME_LOG_PREFIX_NAME.
@Contributed by @ematipico

Enhancements

When a --reporter is provided, and it's different from the default one, the value provided by via --max-diagnostics is ignored and the limit is lifted. Contributed by @ematipico
biome init now generates a new config file with more options set.
This change intends to improve discoverability of the options and to set the more commonly used options to their default values.
Contributed by @Conaclos

The --verbose flag now reports the list of files that were evaluated, and the list of files that were fixed.
The evaluated files are the those files that can be handled by Biome, files that are ignored, don't have an extension or have an extension that Biome can't evaluate are excluded by this list.
The fixed files are those files that were handled by Biome and changed. Files that stays the same after the process are excluded from this list.

 VERBOSE  ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━

  ℹ Files processed:

  - biome/biome.json
  - biome/packages/@&#8203;biomejs/cli-win32-arm64/package.json
  - biome/packages/tailwindcss-config-analyzer/package.json

 VERBOSE  ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━

  ℹ Files fixed:

  - biome/biome/packages/tailwindcss-config-analyzer/src/generate-tailwind-preset.ts

Contributed by @ematipico

Allow passing nursery to the --only and --skip filters.

The --only option allows you to run a given rule or rule group.
The --skip option allows you to skip the execution of a given group or a given rule.

Previously, it was not possible to pass nursery.
This restriction is now removed, as it may make sense to skip the nursery rules that a project has enabled.

Contributed by @Conaclos
The CLI now returns an error code when calling a command in stdin mode, and the contents of the files aren't fixed. For example, the following example will result in an error code of 1 because the lint command triggers some lint rules:
```
echo "let x = 1" | biome lint --stdin-file-path=stdin.js
```
Contributed by @ematipico

Bug fixes

biome lint --write now takes --only and --skip into account (#3470). Contributed by @Conaclos
Fix #3368, now the reporter github tracks the diagnostics that belong to formatting and organize imports. Contributed by @ematipico
Fix #3545, display a warning, 'Avoid using unnecessary Fragment,' when a Fragment contains only one child element that is placed on a new line. Contributed by @satojin219
Migrating from Prettier or ESLint no longer overwrite the overrides field from the configuration (#3544). Contributed by @Conaclos
Fix JSX expressions for noAriaHiddenOnFocusable (#3708). Contributed by @anthonyshew
Fix edge case for <canvas> elements that use role="img" (#3728). Contributed by @anthonyshew
Fix #3633, where diagnostics where incorrectly printed if the code has errors. Contributed by @ematipico
Allow aria-label on heading to prevent useHeadingContent diagnostic (#3767). Contributed by @anthonyshew
Fix edge case #3791 for rule noFocusedTests being used with non-string-like expressions (#3793). Contributed by @h-a-n-a
Fix optional ARIA properties for role="separator" in useAriaPropsForRole (#3856). Contributed by @anthonyshew

Configuration

Add support for loading configuration from .editorconfig files (#1724).

Configuration supplied in .editorconfig will be overridden by the configuration in biome.json. Support is disabled by default and can be enabled by adding the following to your formatter configuration in biome.json:
```
{
  "formatter": {
    "useEditorconfig": true
  }
}
```
Contributed by @dyc3

overrides from an extended configuration is now merged with the overrides of the extension.

Given the following shared configuration biome.shared.json:

{
  "overrides": [
    {
      "include": ["**/*.json"],
      // ...
    }
  ]
}

and the following configuration:

{
  "extends": ["./biome.shared.json"],
  "overrides": [
    {
      "include": ["**/*.ts"],
      // ...
    }
  ]
}

Previously, the overrides from biome.shared.json was overwritten.
It is now merged and results in the following configuration:

{
  "extends": ["./biome.shared.json"],
  "overrides": [
    {
      "include": ["**/*.json"],
      // ...
    },
    {
      "include": ["**/*.ts"],
      // ...
    }
  ]
}

Contributed by @Conaclos

Editors

Fix #3577, where the update of the configuration file was resulting in the creation of a new internal project. Contributed by @ematipico
Fix #3696, where biome.jsonc was incorrectly parsed with incorrect options. Contributed by @ematipico

Formatter

The CSS formatter is enabled by default. Which means that you don't need to opt-in anymore using the configuration file biome.json:
```
{
-  "css": {
-    "formatter": {
-      "enabled": true
-    }
-  }
}
```
Contributed by @ematipico
Add parentheses for nullcoalescing in ternaries.

This change aligns on Prettier 3.3.3.
This adds clarity to operator precedence.
```
- foo ? bar ?? foo : baz;
+ foo ? (bar ?? foo) : baz;
```
Contributed by @Conaclos
Keep the parentheses around infer ... extends declarations in type unions and type intersections (#3419). Contributed by @Conaclos
Keep parentheses around a yield expression inside a type assertion.

Previously, Biome removed parentheses around some expressions that require them inside a type assertion.
For example, in the following code, Biome now preserves the parentheses.
```
function* f() {
  return <T>(yield 0);
}
```
Contributed by @Conaclos

Remove parentheses around expressions that don't need them inside a decorator.

Biome now matches Prettier in the following cases:

  class {
-   @&#8203;(decorator)
+   @&#8203;decorator
    method() {}
  },
  class {
-   @&#8203;(decorator())
+   @&#8203;decorator()
    method() {}
  },
  class {
    @&#8203;(decorator?.())
    method() {}
  },

Contributed by @Conaclos

Keep parentheses around objects preceded with a @satisfies comment.

In the following example, parentheses are no longer removed.
```
export const PROPS = /** @&#8203;satisfies {Record<string, string>} */ ({
  prop: 0,
});
```
Contributed by @Conaclos

Linter

Promoted rules

New rules are incubated in the nursery group.
Once stable, we promote them to a stable group.

The following CSS rules are promoted:

The following JavaScript rules are promoted:

Deprecated rules

correctness/noInvalidNewBuiltin is deprecated. Use correctness/noInvalidBuiltinInstantiation instead.
style/useSingleCaseStatement is deprecated. Use correctness/noSwitchDeclarations instead.
suspicious/noConsoleLog is deprecated. Use suspicious/noConsole instead.

New features

Implement css suppression action. Contributed by @togami2864
Add support for GraphQL linting. Contributed by @ematipico
Add nursery/noCommonJs. Contributed by @minht11
Add nursery/noDuplicateCustomProperties. Contributed by @chansuke
Add nursery/noEnum. Contributed by @nickfla1
Add nursery/noDynamicNamespaceImportAccess. Contributed by @minht11
Add nursery/noIrregularWhitespace. Contributed by @michellocana
Add nursery/noRestrictedTypes. Contributed by @minht11
Add nursery/noSecrets. Contributed by @SaadBazaz
Add nursery/noUselessEscapeInRegex. Contributed by @Conaclos
Add nursery/noValueAtRule. Contributed by @rishabh3112
Add nursery/useAriaPropsSupportedByRole. Contributed by @ryo-ebata
Add nursery/useConsistentMemberAccessibility. Contributed by @seitarof
Add nursery/useStrictMode. Contributed by @ematipico
Add nursery/useTrimStartEnd. Contributed by @chansuke
Add nursery/noIrreguluarWhitespace. Contributed by @DerTimonius

Enhancements

Rename nursery/noUnknownSelectorPseudoElement to nursery/noUnknownPseudoElement. Contributed by @togami2864
The CSS linter is now enabled by default. Which means that you don't need to opt-in anymore using the configuration file biome.json:
```
{
-  "css": {
-    "linter": {
-      "enabled": true
-    }
-  }
}
```
Contributed by @ematipico
The JavaScript linter recognizes TypeScript 5.5 and 5.6 globals. Contributed by @Conaclos

noBlankTarget now supports an array of allowed domains.

The following configuration allows example.com and example.org as blank targets.

"linter": {
  "rules": {
    "a11y": {
      "noBlankTarget": {
      "level": "error",
        "options": {
           "allowDomains": ["example.com", "example.org"]
          }
        }
      }
    }
  }

Contributed by @Jayllyz

noConsole now accepts an option that specifies some allowed calls on console. Contributed by @Conaclos
Add an ignoreNull option for noDoubleEquals.

By default the rule allows loose comparisons against null.
The option ignoreNull can be set to false for reporting loose comparison against null.

Contributed by @peaBerberian.
noDuplicateObjectKeys now works for JSON and JSONC files. Contributed by @ematipico
noInvalidUseBeforeDeclaration now reports direct use of an enum member before its declaration.

In the following code, A is reported as use before its declaration.
```
enum E {
  B = A << 1,
  A = 1,
}
```
Contributed by @Conaclos
noNodejsModules now ignores imports of a package which has the same name as a Node.js module. Contributed by @Conaclos
noNodejsModules now ignores type-only imports (#1674).

The rule no longer reports type-only imports such as:
```
import type assert from "assert";
import type * as assert2 from "assert";
```
Contributed by @Conaclos
noRedundantUseStrict no longer reports "use strict" directives when the package.json marks explicitly the file as a script using the field "type": "commonjs". Contributed by @ematipico
noStaticOnlyClass no longer reports a class that extends another class (#3612). Contributed by @errmayank
noUndeclaredVariables no longer reports a direct reference to an enum member (#2974).

In the following code, the A reference is no longer reported as an undeclared variable.
```
enum E {
  A = 1,
  B = A << 1,
}
```
Contributed by @Conaclos
noUndeclaredVariables recognized Svelte 5 runes in Svelte components and svelte files.

Svelte 5 introduced runes.
The rule now recognizes Svelte 5 runes in files ending with the .svelte, .svelte.js or .svelte.ts extensions.

Contributed by @Conaclos
noUnusedVariables now checks TypeScript declaration files.

This allows to report a type that is unused because it isn't exported.
Global declarations files (declarations files without exports and imports) are still ignored.

Contributed by @Conaclos
useFilenamingConvention now supports unicase letters.

unicase letters have a single case: they are neither uppercase nor lowercase.
Biome now accepts filenames in unicase.
For example, the filename 안녕하세요 is now accepted.

We still reject a name that mixes unicase characters with lowercase or uppercase characters.
For example, the filename A안녕하세요 is rejected.

This change also fixes #3353.
Filenames consisting only of numbers are now accepted.

Contributed by @Conaclos
useFilenamingConvention now supports Next.js/Nuxt/Astro dynamic routes (#3465).

Next.js, SolidStart, Nuxt, and Astro support dynamic routes such as [...slug].js and [[...slug]].js.

Biome now recognizes this syntax. slug must contain only alphanumeric characters.

Contributed by @Conaclos
useExportType no longer reports empty export (#3535).

An empty export {} allows you to force TypeScript to consider a file with no imports and exports as an EcmaScript module.
While export type {} is valid, it is more common to use export {}.
Users may find it confusing that the linter asks them to convert it to export type {}.
Also, a bundler should be able to remove export {} as well as export type {}.
So it is not so useful to report export {}.

Contributed by @Conaclos

Bug fixes

noControlCharactersInRegex now corretcly handle \u escapes in unicode-aware regexes.

Previously, the rule didn't consider regex with the v flags as unicode-aware regexes.
Moreover, \uhhhh was not handled in unicode-aware regexes.

Contributed by @Conaclos
noControlCharactersInRegex now reports control characters and escape sequence of control characters in string regexes. Contributed by @Conaclos
noExcessiveNestedTestSuites: fix an edge case where the rule would alert on heavily nested zod schemas. Contributed by @dyc3
noExtraNonNullAssertion no longer reports a single non-null assertion enclosed in parentheses (#3352). Contributed by @Conaclos
noMultipleSpacesInRegularExpressionLiterals now correctly provides a code fix when Unicode characters are used. Contributed by @Conaclos
noRedeclare no longer report redeclartions for lexically scoped function declarations #3664.

In JavaScript strict mode, function declarations are lexically scoped:
they cannot be accessed outside the block where they are declared.

In non-strict mode, function declarations are hoisted to the top of the enclosing function or global scope.

Previously Biome always hoisted function declarations.
It now takes into account whether the code is in strict or non strict mode.

Contributed by @Conaclos
noUndeclaredDependencies now ignores self package imports.

Given teh following package.json:
```
{
  "name": "my-package",
  "main": "index.js"
}
```
The following import is no longer reported by the rule:
```
import * as mod from "my-package";
```
Contributed by @Conaclos
Fix [#3149] crashes that occurred when applying the noUselessFragments unsafe fixes in certain scenarios. Contributed by @unvalley
noRedeclare no longer reports a variable named as the function expression where it is declared. Contributed by @Conaclos
useAdjacentOverloadSignatures no longer reports a #private class member and a public class member that share the same name (#3309).

The following code is no longer reported:
```
class C {
  #f() {}
  g() {}
  f() {}
}
```
Contributed by @Conaclos
useAltText n olonger requests alt text for elements hidden from assistive technologies (#3316). Contributed by @robintown
useNamingConvention now accepts applying custom convention on abstract classes. Contributed by @Conaclos
useNamingConvention no longer suggests an empty fix when a name doesn't match strict Pascal case (#3561).

Previously the following code led useNamingConvention to suggest an empty fix.
The rule no longer provides a fix for this case.
```
type AAb = any
```
Contributed by @Conaclos
useNamingConvention no longer provides fixes for global TypeScript declaration files.

Global TypeScript declaration files have no epxorts and no imports.
All the declared types are available in all files of the project.
Thus, it is not safe to propose renaming only in the declaration file.

Contributed by @Conaclos
useSortedClasses lint error with Template literals (#3394). Contributed by @hangaoke1
useValidAriaValues now correctly check property types (3748).

Properties that expect a string now accept arbitrary text.
An identifiers can now be made up of any characters except ASCII whitespace.
An identifier list can now be separated by any ASCII whitespace.

Contributed by @Conaclos

Parser

Enhancements

The JSON parser now allows comments in turbo.json and jest.config.json. Contributed by @Netail and @Conaclos
The JSON parser now allows comments in files with the .json extension under the .vscode and .zed directories.

Biome recognizes are well known JSON files that allows comments and/or trailing commas.
Previously, Biome did not recognize JSON files under the .vscode and the .zed directories as JSON files that allow comments.
You had to configure Biome to recognize them:
```
{
  "overrides": [
    {
      "include": ["**/.vscode/*.json", "**/.zed/*.json"],
      "json": { "parser": { "allowComments": true } }
    }
  ]
}
```
This override is no longer needed!
Note that JSON files under the .vscode and the .zed directories don't accept trailing commas.

Contributed by @Conaclos

Bug fixes

The CSS parser now accepts emoji in identifiers (3627).

The following code is now correctly parsed:
```
p {
  --🥔-color: red;
  color: var(--🥔-color);
}
```
Contributed by @Conaclos
Fix #3287 nested selectors with pseudo-classes. Contributed by @denbezrukov
Fix #3349 allow CSS multiple ampersand support. Contributed by @denbezrukov
```
.class {
  && {
    color: red;
  }
}
```
Fix #3410 by correctly parsing break statements containing keywords.
```
out: while (true) {
  break out;
}
```
Contributed by @ah-yu
Fix #3464 by enabling JSX in .vue files that use the lang='jsx' or lang='tsx' attribute. Contributed by @ematipico

withastro/astro (astro)

`v4.15.6`

Compare Source

Patch Changes

#11993 ffba5d7 Thanks @matthewp! - Fix getStaticPaths regression

This reverts a previous change meant to remove a dependency, to fix a regression with multiple nested spread routes.
#11964 06eff60 Thanks @TheOtterlord! - Add wayland (wl-copy) support to astro info

`v4.15.5`

Compare Source

Patch Changes

#11939 7b09c62 Thanks @bholmesdev! - Adds support for Zod discriminated unions on Action form inputs. This allows forms with different inputs to be submitted to the same action, using a given input to decide which object should be used for validation.

This example accepts either a create or update form submission, and uses the type field to determine which object to validate against.

import { defineAction } from 'astro:actions';
import { z } from 'astro:schema';

export const server = {
  changeUser: defineAction({
    accept: 'form',
    input: z.discriminatedUnion('type', [
      z.object({
        type: z.literal('create'),
        name: z.string(),
        email: z.string().email(),
      }),
      z.object({
        type: z.literal('update'),
        id: z.number(),
        name: z.string(),
        email: z.string().email(),
      }),
    ]),
    async handler(input) {
      if (input.type === 'create') {
        // input is { type: 'create', name: string, email: string }
      } else {
        // input is { type: 'update', id: number, name: string, email: string }
      }
    },
  }),
};

The corresponding create and update forms may look like this:

`v4.15.4`

Compare Source

Patch Changes

#11879 bd1d4aa Thanks @matthewp! - Allow passing a cryptography key via ASTRO_KEY

For Server islands Astro creates a cryptography key in order to hash props for the islands, preventing accidental leakage of secrets.

If you deploy to an environment with rolling updates then there could be multiple instances of your app with different keys, causing potential key mismatches.

To fix this you can now pass the ASTRO_KEY environment variable to your build in order to reuse the same key.

To generate a key use:
```
astro create-key
```
This will print out an environment variable to set like:
```
ASTRO_KEY=PIAuyPNn2aKU/bviapEuc/nVzdzZPizKNo3OqF/5PmQ=
```
#11935 c58193a Thanks @Princesseuh! - Fixes astro add not using the proper export point when adding certain adapters

`v4.15.3`

Compare Source

Patch Changes

#11902 d63bc50 Thanks @ascorbic! - Fixes case where content layer did not update during clean dev builds on Linux and Windows
#11886 7ff7134 Thanks @matthewp! - Fixes a missing error message when actions throws during astro sync
#11904 ca54e3f Thanks @wtchnm! - perf(assets): avoid downloading original image when using cache

`v4.15.2`

Compare Source

Patch Changes

#11870 8e5257a Thanks @ArmandPhilippot! - Fixes typo in documenting the fallbackType property in i18n routing
#11884 e450704 Thanks @ascorbic! - Correctly handles content layer data where the transformed value does not match the input schema
#11900 80b4a18 Thanks @delucis! - Fixes the user-facing type of the new i18n.routing.fallbackType option to be optional

`v4.15.1`

Compare Source

Patch Changes

#11872 9327d56 Thanks @bluwy! - Fixes astro add importing adapters and integrations
#11767 d1bd1a1 Thanks @ascorbic! - Refactors content layer sync to use a queue

`v4.15.0`

Compare Source

Minor Changes

#11729 1c54e63 Thanks @ematipico! - Adds a new variant sync for the astro:config:setup hook's command property. This value is set when calling the command astro sync.

If your integration previously relied on knowing how many variants existed for the command property, you must update your logic to account for this new option.
#11743 cce0894 Thanks @ph1p! - Adds a new, optional property timeout for the client:idle directive.

This value allows you to specify a maximum time to wait, in milliseconds, before hydrating a UI framework component, even if the page is not yet done with its initial load. This means you can delay hydration for lower-priority UI elements with more control to ensure your element is interactive within a specified time frame.
```
<ShowHideButton client:idle={{ timeout: 500 }} />
```
#11677 cb356a5 Thanks @ematipico! - Adds a new option fallbackType to i18n.routing configuration that allows you to control how fallback pages are handled.

When i18n.fallback is configured, this new routing option controls whether to redirect to the fallback page, or to rewrite the fallback page's content in place.

The "redirect" option is the default value and matches the current behavior of the existing fallback system.

The option "rewrite" uses the new rewriting system to create fallback pages that render content on the original, requested URL without a browser refresh.

For example, the following configuration will generate a page /fr/index.html that will contain the same HTML rendered by the page /en/index.html when src/pages/fr/index.astro does not exist.
```
// astro.config.mjs
export default defineConfig({
  i18n: {
    locals: ['en', 'fr'],
    defaultLocale: 'en',
    routing: {
      prefixDefaultLocale: true,
      fallbackType: 'rewrite',
    },
    fallback: {
      fr: 'en',
    },
  },
});
```

#11708 62b0d20 Thanks @martrapp! - Adds a new object swapFunctions to expose the necessary utility functions on astro:transitions/client that allow you to build custom swap functions to be used with view transitions.

The example below uses these functions to replace Astro's built-in default swap function with one that only swaps the <main> part of the page:

<script>
  import { swapFunctions } from 'astro:transitions/client';

  document.addEventListener('astro:before-swap', (e) => { e.swap = () => swapMainOnly(e.newDocument) });

  function swapMainOnly(doc: Document) {
    swapFunctions.deselectScripts(doc);
    swapFunctions.swapRootAttributes(doc);
    swapFunctions.swapHeadElements(doc);
    const restoreFocusFunction = swapFunctions.saveFocus();
    const newMain = doc.querySelector('main');
    const oldMain = document.querySelector('main');
    if (newMain && oldMain) {
      swapFunctions.swapBodyElement(newMain, oldMain);
    } else {
      swapFunctions.swapBodyElement(doc.body, document.body);
    }
    restoreFocusFunction();
  };
</script>

See the view transitions guide for more information about hooking into the astro:before-swap lifecycle event and adding a custom swap implementation.

#11843 5b4070e Thanks @bholmesdev! - Exposes z from the new astro:schema module. This is the new recommended import source for all Zod utilities when using Astro Actions.

`v4.14.6`

Compare Source

Patch Changes

#11847 45b599c Thanks @ascorbic! - Fixes a case where Vite would be imported by the SSR runtime, causing bundling errors and bloat.
#11822 6fcaab8 Thanks @bluwy! - Marks internal vite-plugin-fileurl plugin with enforce: 'pre'
#11713 497324c Thanks @voidfill! - Prevents prefetching of the same urls with different hashes.
#11814 2bb72c6 Thanks @eduardocereto! - Updates the documentation for experimental Content Layer API with a corrected code example
#11842 1ffaae0 Thanks @stephan281094! - Fixes a typo in the MissingImageDimension error message
#11828 20d47aa Thanks @bholmesdev! - Improves error message when invalid data is returned by an Action.

`v4.14.5`

Compare Source

Patch Changes

#11809 62e97a2 Thanks @bholmesdev! - Fixes usage of .transform(), .refine(), .passthrough(), and other effects on Action form inputs.
#11812 260c4be Thanks @bholmesdev! - Exposes ActionAPIContext type from the astro:actions module.
#11813 3f7630a Thanks @bholmesdev! - Fixes unexpected undefined value when calling an action from the client without a return value.

`v4.14.4`

Compare Source

Patch Changes

#11794 3691a62 Thanks @bholmesdev! - Fixes unexpected warning log when using Actions on "hybrid" rendered projects.
#11801 9f943c1 Thanks @delucis! - Fixes a bug where the filePath property was not available on content collection entries when using the content layer file() loader with a JSON file that contained an object instead of an array. This was breaking use of the image() schema utility among other things.

`v4.14.3`

Compare Source

Patch Changes

#11780 c6622ad Thanks @Princesseuh! - Deprecates the Squoosh image service, to be removed in Astro 5.0. We recommend migrating to the default Sharp service.
#11790 41c3fcb Thanks @sarah11918! - Updates the documentation for experimental astro:env with a corrected link to the RFC proposal
#11773 86a3391 Thanks @ematipico! - Changes messages logged when using unsupported, deprecated, or experimental adapter features for clarity
#11745 89bab1e Thanks @bluwy! - Prints prerender dynamic value usage warning only if it's used
#11774 c6400ab Thanks @florian-lefebvre! - Fixes the path returned by injectTypes
#11730 2df49a6 Thanks @florian-lefebvre! - Simplifies path operations of astro sync
#11771 49650a4 Thanks @florian-lefebvre! - Fixes an error thrown by astro sync when an astro:env virtual module is imported inside the Content Collections config
#11744 b677429 Thanks @bluwy! - Disables the WebSocket

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 was generated by Mend Renovate. View the repository job log.

codecov · 2024-07-03T17:15:30Z

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 75.82%. Comparing base (24f764c) to head (fe314e5).
Report is 2 commits behind head on main.

Additional details and impacted files

@@           Coverage Diff           @@
##             main     #761   +/-   ##
=======================================
  Coverage   75.82%   75.82%           
=======================================
  Files         205      205           
  Lines       22946    22946           
=======================================
  Hits        17398    17398           
  Misses       5548     5548

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

deno-deploy bot deployed to Preview July 3, 2024 17:01 View deployment

renovate bot force-pushed the renovate/all-minor-patch branch from 28ba368 to 21e1674 Compare July 3, 2024 22:10

renovate bot changed the title ~~fix(deps): update dependency astro to v4.11.4~~ fix(deps): update dependency astro to v4.11.5 Jul 3, 2024

deno-deploy bot deployed to Preview July 3, 2024 22:10 View deployment

renovate bot force-pushed the renovate/all-minor-patch branch from 21e1674 to 7240f8c Compare July 12, 2024 10:33

renovate bot changed the title ~~fix(deps): update dependency astro to v4.11.5~~ fix(deps): update all non-major dependencies Jul 12, 2024

deno-deploy bot deployed to Preview July 12, 2024 10:33 View deployment

renovate bot force-pushed the renovate/all-minor-patch branch from 7240f8c to f5f6810 Compare July 15, 2024 17:33

renovate bot requested a review from marc2332 as a code owner July 15, 2024 17:33

deno-deploy bot deployed to Preview July 15, 2024 17:34 View deployment

deno-deploy bot deployed to Preview July 15, 2024 17:35 View deployment

renovate bot force-pushed the renovate/all-minor-patch branch from f5f6810 to 0f75f7c Compare July 16, 2024 16:06

deno-deploy bot deployed to Preview July 16, 2024 16:07 View deployment

renovate bot force-pushed the renovate/all-minor-patch branch from 0f75f7c to 67bd53e Compare July 17, 2024 15:25

deno-deploy bot deployed to Preview July 17, 2024 15:25 View deployment

deno-deploy bot deployed to Preview July 17, 2024 15:26 View deployment

renovate bot force-pushed the renovate/all-minor-patch branch from 67bd53e to 1ba7069 Compare July 18, 2024 16:46

deno-deploy bot deployed to Preview July 18, 2024 16:47 View deployment

renovate bot force-pushed the renovate/all-minor-patch branch from 1ba7069 to 4c539fa Compare July 18, 2024 23:48

deno-deploy bot deployed to Preview July 18, 2024 23:48 View deployment

renovate bot force-pushed the renovate/all-minor-patch branch from 4c539fa to ce50564 Compare July 19, 2024 14:37

deno-deploy bot deployed to Preview July 19, 2024 14:38 View deployment

renovate bot force-pushed the renovate/all-minor-patch branch from ce50564 to 8a7617e Compare July 20, 2024 02:18

deno-deploy bot deployed to Preview July 20, 2024 02:19 View deployment

renovate bot force-pushed the renovate/all-minor-patch branch from 8a7617e to 38715fe Compare July 21, 2024 11:29

deno-deploy bot deployed to Preview July 21, 2024 11:29 View deployment

renovate bot force-pushed the renovate/all-minor-patch branch from 38715fe to 7217768 Compare July 25, 2024 16:04

deno-deploy bot deployed to Preview July 25, 2024 16:04 View deployment

renovate bot force-pushed the renovate/all-minor-patch branch from 7217768 to 266337a Compare July 30, 2024 16:37

renovate bot force-pushed the renovate/all-minor-patch branch from 0dad699 to 6a0e904 Compare August 23, 2024 01:11

deno-deploy bot deployed to Preview August 23, 2024 01:11 View deployment

renovate bot force-pushed the renovate/all-minor-patch branch from 6a0e904 to 7e806dd Compare August 28, 2024 09:45

deno-deploy bot deployed to Preview August 28, 2024 09:45 View deployment

deno-deploy bot deployed to Preview August 28, 2024 09:50 View deployment

renovate bot force-pushed the renovate/all-minor-patch branch from 7e806dd to aea957d Compare August 28, 2024 13:41

deno-deploy bot deployed to Preview August 28, 2024 13:42 View deployment

renovate bot force-pushed the renovate/all-minor-patch branch from aea957d to dab622e Compare August 29, 2024 13:46

deno-deploy bot deployed to Preview August 29, 2024 13:47 View deployment

renovate bot force-pushed the renovate/all-minor-patch branch from dab622e to 97b2142 Compare August 29, 2024 18:48

deno-deploy bot deployed to Preview August 29, 2024 18:49 View deployment

renovate bot force-pushed the renovate/all-minor-patch branch from 97b2142 to 96c418f Compare September 2, 2024 11:36

deno-deploy bot deployed to Preview September 2, 2024 11:37 View deployment

renovate bot force-pushed the renovate/all-minor-patch branch from 96c418f to 5c7a0c1 Compare September 5, 2024 03:05

deno-deploy bot deployed to Preview September 5, 2024 03:06 View deployment

renovate bot force-pushed the renovate/all-minor-patch branch from 5c7a0c1 to b2a8ab2 Compare September 6, 2024 18:08

deno-deploy bot deployed to Preview September 6, 2024 18:08 View deployment

renovate bot force-pushed the renovate/all-minor-patch branch from b2a8ab2 to ba45263 Compare September 9, 2024 17:28

deno-deploy bot deployed to Preview September 9, 2024 17:29 View deployment

renovate bot force-pushed the renovate/all-minor-patch branch from ba45263 to fe314e5 Compare September 11, 2024 17:42

deno-deploy bot deployed to Preview September 11, 2024 17:43 View deployment

renovate bot force-pushed the renovate/all-minor-patch branch from fe314e5 to d718b07 Compare September 12, 2024 16:20

renovate bot changed the title ~~fix(deps): update all non-major dependencies~~ chore(deps): update all non-major dependencies Sep 12, 2024

deno-deploy bot deployed to Preview September 12, 2024 16:20 View deployment

renovate bot force-pushed the renovate/all-minor-patch branch from d718b07 to 3a66e76 Compare September 13, 2024 13:40

deno-deploy bot deployed to Preview September 13, 2024 13:40 View deployment

chore(deps): update all non-major dependencies

f593f88

renovate bot force-pushed the renovate/all-minor-patch branch from 3a66e76 to f593f88 Compare September 13, 2024 20:14

deno-deploy bot deployed to Preview September 13, 2024 20:14 View deployment

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

chore(deps): update all non-major dependencies #761

chore(deps): update all non-major dependencies #761

renovate bot commented Jul 3, 2024 •

edited

Loading

codecov bot commented Jul 3, 2024 •

edited

Loading

chore(deps): update all non-major dependencies #761

Are you sure you want to change the base?

chore(deps): update all non-major dependencies #761

Conversation

renovate bot commented Jul 3, 2024 • edited Loading

Release Notes

Analyzer

CLI

New features

Enhancements

Bug fixes

Configuration

Editors

Formatter

Linter

Promoted rules

Deprecated rules

New features

Enhancements

Bug fixes

Parser

Enhancements

Bug fixes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Minor Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Configuration

codecov bot commented Jul 3, 2024 • edited Loading

Codecov Report

renovate bot commented Jul 3, 2024 •

edited

Loading

codecov bot commented Jul 3, 2024 •

edited

Loading