chore(deps): update all non-major dependencies by renovate[bot] · Pull Request #293 · aiktb/furiganamaker

renovate · 2024-11-24T23:03:40Z

This PR contains the following updates:

Package	Change	Type	Update
@biomejs/biome (source)	`2.1.3` -> `2.2.4`	devDependencies	minor
@cloudflare/workers-types	`4.20241218.0` -> `4.20250913.0`	devDependencies	minor
@commitlint/cli (source)	`19.6.1` -> `19.8.1`	devDependencies	minor
@commitlint/config-conventional (source)	`19.6.0` -> `19.8.1`	devDependencies	minor
@commitlint/types (source)	`19.5.0` -> `19.8.1`	devDependencies	minor
@floating-ui/react (source)	`0.27.2` -> `0.27.16`	dependencies	patch
@fontsource/dm-sans (source)	`5.1.0` -> `5.2.6`	devDependencies	minor
@fontsource/lobster (source)	`5.1.0` -> `5.2.6`	devDependencies	minor
@fontsource/noto-sans-jp (source)	`5.1.0` -> `5.2.7`	devDependencies	minor
@headlessui/react (source)	`2.2.3` -> `2.2.8`	pnpm.catalog.default	patch
@iconify-json/fa6-brands	`1.2.5` -> `1.2.6`	pnpm.catalog.default	patch
@iconify-json/mdi	`1.2.2` -> `1.2.3`	devDependencies	patch
@iconify-json/tabler	`1.2.13` -> `1.2.22`	devDependencies	patch
@playwright/test (source)	`1.49.1` -> `1.55.0`	devDependencies	minor
@react-router/cloudflare (source)	`7.7.1` -> `7.9.1`	pnpm.catalog.default	minor
@react-router/dev (source)	`7.7.1` -> `7.9.1`	pnpm.catalog.default	minor
@react-router/fs-routes (source)	`7.7.1` -> `7.9.1`	pnpm.catalog.default	minor
@tailwindcss/forms	`0.5.9` -> `0.5.10`	pnpm.catalog.default	patch
@tailwindcss/vite (source)	`4.1.7` -> `4.1.13`	pnpm.catalog.default	patch
@total-typescript/ts-reset (source)	`^0.4.2` -> `^0.6.0`	pnpm.catalog.default	minor
@types/react (source)	`19.0.1` -> `19.1.13`	pnpm.catalog.default	minor
@types/react-dom (source)	`19.0.2` -> `19.1.9`	pnpm.catalog.default	minor
@vitejs/plugin-react-swc (source)	`4.0.0` -> `4.0.1`	devDependencies	patch
@webext-core/messaging (source)	`2.1.0` -> `2.3.0`	dependencies	minor
@wxt-dev/auto-icons (source)	`1.0.2` -> `1.1.0`	devDependencies	minor
es-toolkit (source)	`1.39.8` -> `1.39.10`	pnpm.catalog.default	patch
i18next (source)	`25.3.2` -> `25.5.2`	dependencies	minor
isbot (source)	`5.1.18` -> `5.1.30`	dependencies	patch
lycheeverse/lychee-action	`v2.1.0` -> `v2.6.1`	action	minor
next-themes	`0.4.4` -> `0.4.6`	dependencies	patch
node (source)	`24.5.0` -> `24.8.0`		minor
pnpm (source)	`10.12.1+sha512.f0dda8580f0ee9481c5c79a1d927b9164f2c478e90992ad268bbb2465a736984391d6333d2c327913578b2804af33474ca554ba29c04a8b13060a717675ae3ac` -> `10.16.0`	packageManager	minor
react (source)	`19.0.0` -> `19.1.1`	pnpm.catalog.default	minor
react-dom (source)	`19.0.0` -> `19.1.1`	pnpm.catalog.default	minor
react-i18next	`15.5.3` -> `15.7.3`	dependencies	minor
react-router (source)	`7.7.1` -> `7.9.1`	pnpm.catalog.default	minor
react-share	`5.1.1` -> `5.2.2`	dependencies	minor
tailwindcss (source)	`4.1.7` -> `4.1.13`	pnpm.catalog.default	patch
vite-plugin-svgr	`4.3.0` -> `4.5.0`	devDependencies	minor
wrangler (source)	`4.29.1` -> `4.36.0`	devDependencies	minor
wxt (source)	`0.20.8` -> `0.20.11`	devDependencies	patch
zod (source)	`4.0.15` -> `4.1.8`	dependencies	minor
zustand	`5.0.7` -> `5.0.8`	pnpm.catalog.default	patch

Release Notes

biomejs/biome (@biomejs/biome)

`v2.2.4`

Compare Source

Patch Changes

#7453 aa8cea3 Thanks @arendjr! - Fixed #7242: Aliases specified in package.json's imports section now support having multiple targets as part of an array.
#7454 ac17183 Thanks @arendjr! - Greatly improved performance of noImportCycles by eliminating allocations.

In one repository, the total runtime of Biome with only noImportCycles enabled went from ~23s down to ~4s.
#7447 7139aad Thanks @rriski! - Fixes #7446. The GritQL $... spread metavariable now correctly matches members in object literals, aligning its behavior with arrays and function calls.
#6710 98cf9af Thanks @arendjr! - Fixed #4723: Type inference now recognises index signatures and their accesses when they are being indexed as a string.

Example

type BagOfPromises = {
  // This is an index signature definition. It declares that instances of type
  // `BagOfPromises` can be indexed using arbitrary strings.
  [property: string]: Promise<void>;
};

let bag: BagOfPromises = {};
// Because `bag.iAmAPromise` is equivalent to `bag["iAmAPromise"]`, this is
// considered an access to the string index, and a Promise is expected.
bag.iAmAPromise;

351bccd Thanks @ematipico! - Fixed #7212, now the useOptionalChain rule recognizes optional chaining using typeof (e.g., typeof foo !== 'undefined' && foo.bar).
351bccd Thanks @ematipico! - Fixed #7323. noUnusedPrivateClassMembers no longer reports as unused TypeScript private members if the rule encounters a computed access on this.

In the following example, member as previously reported as unused.
It is no longer reported.
```
class TsBioo {
  private member: number;

  set_with_name(name: string, value: number) {
    this[name] = value;
  }
}
```
351bccd Thanks @ematipico! - Added the new nursery lint rule noJsxLiterals, which disallows the use of string literals inside JSX.

The rule catches these cases:
```
<>
  <div>test</div> {/* test is invalid */}
  <>test</>
  <div>
    {/* this string is invalid */}
    asdjfl test foo
  </div>
</>
```
351bccd Thanks @ematipico! - Fixed an issue (#6393) where the useHookAtTopLevel rule reported excessive diagnostics for nested hook calls.

The rule now reports only the offending top-level call site, not sub-hooks of composite hooks.
```
// Before: reported twice (useFoo and useBar).
function useFoo() {
  return useBar();
}
function Component() {
  if (cond) useFoo();
}
// After: reported once at the call to useFoo().
```
#7461 ea585a9 Thanks @arendjr! - Improved performance of noPrivateImports by eliminating allocations.

In one repository, the total runtime of Biome with only noPrivateImports enabled went from ~3.2s down to ~1.4s.
351bccd Thanks @ematipico! - Fixed #7411. The Biome Language Server had a regression where opening an editor with a file already open wouldn't load the project settings correctly.
351bccd Thanks @ematipico! - Added the new nursery rule noDuplicateDependencies, which verifies that no dependencies are duplicated between the bundledDependencies, bundleDependencies, dependencies, devDependencies, overrides, optionalDependencies, and peerDependencies sections.

For example, the following snippets will trigger the rule:
```
{
  "dependencies": {
    "foo": ""
  },
  "devDependencies": {
    "foo": ""
  }
}
```
```
{
  "dependencies": {
    "foo": ""
  },
  "optionalDependencies": {
    "foo": ""
  }
}
```
```
{
  "dependencies": {
    "foo": ""
  },
  "peerDependencies": {
    "foo": ""
  }
}
```
351bccd Thanks @ematipico! - Fixed #3824. Now the option CLI --color is correctly applied to logging too.

`v2.2.3`

Compare Source

Patch Changes

#7353 4d2b719 Thanks @JeetuSuthar! - Fixed #7340: The linter now allows the navigation property for view-transition in CSS.

Previously, the linter incorrectly flagged navigation: auto as an unknown property. This fix adds navigation to the list of known CSS properties, following the CSS View Transitions spec.
#7275 560de1b Thanks @arendjr! - Fixed #7268: Files that are explicitly passed as CLI arguments are now correctly ignored if they reside in an ignored folder.
#7358 963a246 Thanks @ematipico! - Fixed #7085, now the rule noDescendingSpecificity correctly calculates the specificity of selectors when they are included inside a media query.
#7387 923674d Thanks @qraqras! - Fixed #7381, now the useOptionalChain rule recognizes optional chaining using Yoda expressions (e.g., undefined !== foo && foo.bar).
#7316 f9636d5 Thanks @Conaclos! - Fixed #7289. The rule useImportType now inlines import type into import { type } when the style option is set to inlineType.

Example:
```
import type { T } from "mod";
// becomes
import { type T } from "mod";
```
#7350 bb4d407 Thanks @siketyan! - Fixed #7261: two characters ・ (KATAKANA MIDDLE DOT, U+30FB) and ･ (HALFWIDTH KATAKANA MIDDLE DOT, U+FF65) are no longer considered as valid characters in identifiers. Property keys containing these character(s) are now preserved as string literals.
#7377 811f47b Thanks @ematipico! - Fixed a bug where the Biome Language Server didn't correctly compute the diagnostics of a monorepo setting, caused by an incorrect handling of the project status.
#7245 fad34b9 Thanks @kedevked! - Added the new lint rule useConsistentArrowReturn.

This rule enforces a consistent return style for arrow functions.

Invalid

const f = () => {
  return 1;
};

This rule is a port of ESLint's arrow-body-style rule.

#7370 e8032dd Thanks @fireairforce! - Support dynamic import defer and import source. The syntax looks like:

import.source("foo");
import.source("x", { with: { attr: "val" } });
import.defer("foo");
import.defer("x", { with: { attr: "val" } });

#7369 b1f8cbd Thanks @siketyan! - Range suppressions are now supported for Grit plugins.

For JavaScript, you can suppress a plugin as follows:

// biome-ignore-start lint/plugin/preferObjectSpread: reason
Object.assign({ foo: "bar" }, baz);
// biome-ignore-end lint/plugin/preferObjectSpread: reason

For CSS, you can suppress a plugin as follows:

body {
  /* biome-ignore-start lint/plugin/useLowercaseColors: reason */
  color: #fff;
  /* biome-ignore-end lint/plugin/useLowercaseColors: reason */
}

#7384 099507e Thanks @ematipico! - Reduced the severity of certain diagnostics emitted when Biome deserializes the configuration files.
Now these diagnostics are emitted as Information severity, which means that they won't interfere when running commands with --error-on-warnings
#7302 2af2380 Thanks @unvalley! - Fixed #7301: useReadonlyClassProperties now correctly skips JavaScript files.
#7288 94d85f8 Thanks @ThiefMaster! - Fixed #7286. Files are now formatted with JSX behavior when javascript.parser.jsxEverywhere is explicitly set.

Previously, this flag was only used for parsing, but not for formatting, which resulted in incorrect formatting of conditional expressions when JSX syntax is used in .js files.
#7311 62154b9 Thanks @qraqras! - Added the new nursery rule noUselessCatchBinding. This rule disallows unnecessary catch bindings.
```
try {
    // Do something
- } catch (unused) {}
+ } catch {}
```

#7349 45c1dfe Thanks @ematipico! - Fixed #4298. Biome now correctly formats CSS declarations when it contains one single value:

.bar {
-  --123456789012345678901234567890: var(--1234567890123456789012345678901234567);
+  --123456789012345678901234567890: var(
+    --1234567890123456789012345678901234567
+  );
}

#7295 7638e84 Thanks @ematipico! - Fixed #7130. Removed the emission of a false-positive diagnostic. Biome no longer emits the following diagnostic:

lib/main.ts:1:5 suppressions/unused ━━━━━━━━━━━━━━━━━━━━━━━━━

  ⚠ Suppression comment has no effect because the tool is not enabled.

  > 1 │ /** biome-ignore-all assist/source/organizeImports: For the lib root file, we don't want to organize exports */
      │     ^^^^^^^^^^^^^^^^

#7377 811f47b Thanks @ematipico! - Fixed #7371 where the Biome Language Server didn't correctly recompute the diagnostics when updating a nested configuration file.
#7348 ac27fc5 Thanks @ematipico! - Fixed #7079. Now the rule useSemanticElements doesn't trigger components and custom elements.
#7389 ab06a7e Thanks @Conaclos! - Fixed #7344. useNamingConvention no longer reports interfaces defined in global declarations.

Interfaces declared in global declarations augment existing interfaces.
Thus, they must be ignored.

In the following example, useNamingConvention reported HTMLElement.
It is now ignored.
```
export {};
declare global {
  interface HTMLElement {
    foo(): void;
  }
}
```
#7315 4a2bd2f Thanks @vladimir-ivanov! - Fixed #7310: useReadonlyClassProperties correctly handles nested assignments, avoiding false positives when a class property is assigned within another assignment expression.

Example of code that previously triggered a false positive but is now correctly ignored:
```
class test {
  private thing: number = 0; // incorrectly flagged

  public incrementThing(): void {
    const temp = { x: 0 };
    temp.x = this.thing++;
  }
}
```

`v2.2.2`

Compare Source

Patch Changes

#7266 b270bb5 Thanks @ematipico! - Fixed an issue where Biome got stuck when analyzing some files. This is usually caused by a bug in the inference engine. Now Biome has some guards in place in case the number of types grows too much, and if that happens, a diagnostic is emitted and the inference is halted.
#7281 6436180 Thanks @ematipico! - Fixed an issue where the function scanProject wouldn't work as expected.
#7285 1511d0c Thanks @rriski! - Partially fixed #6782: JSX node kinds are now supported in GritQL AST nodes.
#7249 dff85c0 Thanks @ematipico! - Fixed #748, where Biome Language Server didn't show the unsafe fixes when requesting the quick fixes. Now all LSP editors will show also opt-in, unsafe fixes.
#7266 b270bb5 Thanks @ematipico! - Fixed #7020: Resolved an issue with analysing types of static member expressions involving unions. If the object type was a union that referenced nested unions, it would trigger an infinite loop as it tried to keep expanding nested unions, and the set of types would grow indefinitely.
#7209 679b70e Thanks @patrickshipe! - Resolved an overcorrection in useImportExtensions when importing explicit index files.

Imports that explicitly reference an index file are now preserved and no longer rewritten to nested index paths.

Example

// Before
-      import "./sub/index";
+      import "./sub/index/index.js";

// After
-      import "./sub/index";
+      import "./sub/index.js";

#7270 953f9c6 Thanks @arendjr! - Fixed #6172: Resolved an issue with inferring types for rest parameters. This issue caused rest-parameter types to be incorrect, and in some cases caused extreme performance regressions in files that contained many methods with rest-parameter definitions.
#7234 b7aa111 Thanks @JeetuSuthar! - Fixed #7233: The useIndexOf rule now correctly suggests using indexOf() instead of findIndex().

The diagnostic message was incorrectly recommending Array#findIndex() over Array#indexOf(), when it should recommend the opposite for simple equality checks.
#7283 0b07f45 Thanks @ematipico! - Fixed #7236. Now Biome correctly migrates JSONC configuration files when they are passed using --config-path.
#7239 1d643d8 Thanks @minht11! - Fixed an issue where Svelte globals ($state and so on) were not properly recognized inside .svelte.test.ts/js and .svelte.spec.ts/js files.
#7264 62fdbc8 Thanks @ematipico! - Fixed a regression where when using --log-kind-pretty wasn't working anymore as expected.
#7244 660031b Thanks @JeetuSuthar! - Fixed #7225: The noExtraBooleanCast rule now preserves parentheses when removing Boolean calls inside negations.
```
// Before
!Boolean(b0 && b1);
// After
!(b0 && b1); // instead of !b0 && b1
```
#7298 46a8e93 Thanks @unvalley! - Fixed #6695: useNamingConvention now correctly reports TypeScript parameter properties with modifiers.

Previously, constructor parameter properties with modifiers like private or readonly were not checked against naming conventions. These properties are now treated consistently with regular class properties.

`v2.2.0`

Compare Source

Minor Changes

#5506 1f8755b Thanks @sakai-ast! - The noRestrictedImports rule has been enhanced with a new patterns option. This option allows for more flexible and powerful import restrictions using gitignore-style patterns.

You can now define patterns to restrict entire groups of modules. For example, you can disallow imports from any path under import-foo/ except for import-foo/baz.
```
{
  "options": {
    "patterns": [
      {
        "group": ["import-foo/*", "!import-foo/baz"],
        "message": "import-foo is deprecated, except for modules in import-foo/baz."
      }
    ]
  }
}
```
Invalid examples
```
import foo from "import-foo/foo";
import bar from "import-foo/bar";
```
Valid examples
```
import baz from "import-foo/baz";
```
Additionally, the patterns option introduces importNamePattern to restrict specific import names using regular expressions.
The following example restricts the import names that match x , y or z letters from modules under import-foo/.
```
{
  "options": {
    "patterns": [
      {
        "group": ["import-foo/*"],
        "importNamePattern": "[xyz]"
      }
    ]
  }
}
```
Invalid examples
```
import { x } from "import-foo/foo";
```
Valid examples
```
import { foo } from "import-foo/foo";
```
Furthermore, you can use the invertImportNamePattern boolean option to reverse this logic. When set to true, only the import names that match the importNamePattern will be allowed. The following configuration only allows the import names that match x , y or z letters from modules under import-foo/.
```
{
  "options": {
    "patterns": [
      {
        "group": ["import-foo/*"],
        "importNamePattern": "[xyz]",
        "invertImportNamePattern": true
      }
    ]
  }
}
```
Invalid examples
```
import { foo } from "import-foo/foo";
```
Valid examples
```
import { x } from "import-foo/foo";
```
#6506 90c5d6b Thanks @nazarhussain! - Allow customization of the sort order for different sorting actions. These actions now support a sort option:
- assist/source/useSortedKeys now has a sortOrder option
- assist/source/useSortedAttributes now has a sortOrder option
- assist/source/organizeImports now has an identifierOrder option
For each of these options, the supported values are the same:
1. natural. Compares two strings using a natural ASCII order. Uppercase letters come first (e.g. A < a < B < b) and number are compared in a human way (e.g. 9 < 10). This is the default value.
2. lexicographic. Strings are ordered lexicographically by their byte values. This orders Unicode code points based on their positions in the code charts. This is not necessarily the same as “alphabetical” order, which varies by language and locale.
#7159 df3afdf Thanks @ematipico! - Added the new rule useBiomeIgnoreFolder. Since v2.2, Biome correctly prevents the indexing and crawling of folders.

However, the correct pattern has changed. This rule attempts to detect incorrect usage, and promote the new pattern:
```
// biome.json
{
  "files": {
    "includes": [
-      "!dist/**",
-      "!**/fixtures/**",
+      "!dist",
+      "!**/fixtures",
    ]
  }
}
```
#6989 85b1128 Thanks @arendjr! - Fixed minor inconsistencies in how files.includes was being handled.

Previously, Biome sometimes failed to properly ignore the contents of a folder if you didn't specify the /** at the end of a glob pattern. This was unfortunate, because it meant we still had to traverse the folder and then apply the glob to every entry inside it.

This is no longer an issue and we now recommend to ignore folders without using the /** suffix.
#7118 a78e878 Thanks @avshalomt2! - Added support for .graphqls files. Biome can now format and lint GraphQL files that have the extension .graphqls

#6159 f02a296 Thanks @bavalpey! - Added a new option to Biome's JavaScript formatter, javascript.formatter.operatorLinebreak, to configure whether long lines should be broken before or after binary operators.

For example, the following configuration:

{
  formatter: {
    javascript: {
      operatorLinebreak: "before", // defaults to "after"
    },
  },
}

Will cause this JavaScript file:

const VERY_LONG_CONDITION_1234123412341234123412341234 = false;

if (
  VERY_LONG_CONDITION_1234123412341234123412341234 &&
  VERY_LONG_CONDITION_1234123412341234123412341234 &&
  VERY_LONG_CONDITION_1234123412341234123412341234 &&
  VERY_LONG_CONDITION_1234123412341234123412341234
) {
  console.log("DONE");
}

to be formatted like this:

const VERY_LONG_CONDITION_1234123412341234123412341234 = false;

if (
  VERY_LONG_CONDITION_1234123412341234123412341234 &&
  VERY_LONG_CONDITION_1234123412341234123412341234 &&
  VERY_LONG_CONDITION_1234123412341234123412341234 &&
  VERY_LONG_CONDITION_1234123412341234123412341234
) {
  console.log("DONE");
}

#7137 a653a0f Thanks @ematipico! - Promoted multiple lint rules from nursery to stable groups and renamed several rules for consistency.

Promoted rules

The following rules have been promoted from nursery to stable groups:

CSS

Promoted noImportantStyles to the complexity group.
Promoted noUnknownAtRules to the suspicious group.

GraphQL

Promoted useGraphqlNamedOperations to the correctness group.
Promoted useGraphqlNamingConvention to the style group.

JavaScript/TypeScript

Promoted noExcessiveLinesPerFunction to the complexity group.
Promoted noImplicitCoercions to the complexity group.
Promoted useIndexOf to the complexity group.
Promoted [`noGlo

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 is behind base branch, 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.

cloudflare-workers-and-pages · 2024-11-24T23:03:41Z

Deploying furiganamaker with Cloudflare Pages

Latest commit:	`856211e`
Status:	✅ Deploy successful!
Preview URL:	https://251612da.furiganamaker.pages.dev
Branch Preview URL:	https://renovate-all-minor-patch.furiganamaker.pages.dev

View logs

cloudflare-workers-and-pages · 2025-02-21T11:30:26Z

Deploying furigana-maker with Cloudflare Pages

Latest commit:	`e2a3790`
Status:	✅ Deploy successful!
Preview URL:	https://3d6d9b7d.furiganamaker.pages.dev
Branch Preview URL:	https://renovate-all-minor-patch.furiganamaker.pages.dev

View logs

cloudflare-workers-and-pages · 2025-02-21T15:48:54Z

Deploying furigana-maker with Cloudflare Pages

Latest commit:	`4af7f29`
Status:	⚡️ Build in progress...

View logs

cloudflare-workers-and-pages · 2025-02-21T15:50:28Z

Deploying furigana-maker with Cloudflare Pages

Latest commit:	`4af7f29`
Status:	✅ Deploy successful!
Preview URL:	https://7874b3e6.furiganamaker.pages.dev
Branch Preview URL:	https://renovate-all-minor-patch.furiganamaker.pages.dev

View logs

cloudflare-workers-and-pages · 2025-02-21T18:51:23Z

Deploying furigana-maker with Cloudflare Pages

Latest commit:	`043dcd1`
Status:	⚡️ Build in progress...

View logs

cloudflare-workers-and-pages · 2025-02-21T18:52:29Z

Deploying furigana-maker with Cloudflare Pages

Latest commit:	`043dcd1`
Status:	✅ Deploy successful!
Preview URL:	https://8c19266a.furiganamaker.pages.dev
Branch Preview URL:	https://renovate-all-minor-patch.furiganamaker.pages.dev

View logs

renovate · 2025-07-30T14:12:49Z

⚠️ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

any of the package files in this branch needs updating, or
the branch becomes conflicted, or
you click the rebase/retry checkbox if found above, or
you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: undefined

Command failed: corepack use pnpm@10.16.0

renovate Bot changed the title ~~chore(deps): update dependency @types/chrome to ^0.0.284~~ chore(deps): update all non-major dependencies Nov 25, 2024

renovate Bot force-pushed the renovate/all-minor-patch branch 10 times, most recently from a2478bb to 2da4d0b Compare November 29, 2024 12:33

renovate Bot force-pushed the renovate/all-minor-patch branch 15 times, most recently from 2185209 to c689e0d Compare December 7, 2024 09:40

renovate Bot force-pushed the renovate/all-minor-patch branch 3 times, most recently from b3a041a to 7d5116a Compare December 10, 2024 02:29

aiktb force-pushed the main branch 7 times, most recently from d2eee56 to 605eb53 Compare December 22, 2024 02:28

renovate Bot force-pushed the renovate/all-minor-patch branch 9 times, most recently from 82a0a9c to 262cada Compare December 31, 2024 11:23

renovate Bot force-pushed the renovate/all-minor-patch branch 5 times, most recently from a571a18 to 91e7437 Compare January 6, 2025 00:57

renovate Bot and others added 3 commits September 13, 2025 09:04

chore(deps): update all non-major dependencies

f202f35

Merge branch 'main' into renovate/all-minor-patch

7f03a7b

chore: update deps

20ada20

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Uh oh!

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

chore(deps): update all non-major dependencies#293
aiktb merged 3 commits into
mainfrom
renovate/all-minor-patch

renovate Bot commented Nov 24, 2024 •

edited

Loading

Uh oh!

cloudflare-workers-and-pages Bot commented Nov 24, 2024 •

edited

Loading

Uh oh!

cloudflare-workers-and-pages Bot commented Feb 21, 2025

Uh oh!

cloudflare-workers-and-pages Bot commented Feb 21, 2025

Uh oh!

cloudflare-workers-and-pages Bot commented Feb 21, 2025

Uh oh!

cloudflare-workers-and-pages Bot commented Feb 21, 2025

Uh oh!

cloudflare-workers-and-pages Bot commented Feb 21, 2025

Uh oh!

renovate Bot commented Jul 30, 2025 •

edited

Loading

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

1 participant

Uh oh!

Conversation

renovate Bot commented Nov 24, 2024 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Release Notes

v2.2.4

Patch Changes

Example

v2.2.3

Patch Changes

Invalid

v2.2.2

Patch Changes

Example

v2.2.0

Minor Changes

Promoted rules

CSS

GraphQL

JavaScript/TypeScript

Configuration

Uh oh!

cloudflare-workers-and-pages Bot commented Nov 24, 2024 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Deploying furiganamaker with Cloudflare Pages

Uh oh!

cloudflare-workers-and-pages Bot commented Feb 21, 2025

Deploying furigana-maker with Cloudflare Pages

Uh oh!

cloudflare-workers-and-pages Bot commented Feb 21, 2025

Deploying furigana-maker with Cloudflare Pages

Uh oh!

cloudflare-workers-and-pages Bot commented Feb 21, 2025

Deploying furigana-maker with Cloudflare Pages

Uh oh!

cloudflare-workers-and-pages Bot commented Feb 21, 2025

Deploying furigana-maker with Cloudflare Pages

Uh oh!

cloudflare-workers-and-pages Bot commented Feb 21, 2025

Deploying furigana-maker with Cloudflare Pages

Uh oh!

renovate Bot commented Jul 30, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

⚠️ Artifact update problem

File name: undefined

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

1 participant

renovate Bot commented Nov 24, 2024 •

edited

Loading

`v2.2.4`

`v2.2.3`

`v2.2.2`

`v2.2.0`

cloudflare-workers-and-pages Bot commented Nov 24, 2024 •

edited

Loading

renovate Bot commented Jul 30, 2025 •

edited

Loading