Skip to content

chore(deps): update all dependencies - #1219

Open
renovate[bot] wants to merge 1 commit into
masterfrom
renovate/all
Open

chore(deps): update all dependencies#1219
renovate[bot] wants to merge 1 commit into
masterfrom
renovate/all

Conversation

@renovate

@renovate renovate Bot commented Aug 1, 2026 •
edited
Loading

Copy link
Copy Markdown
Contributor

Note

This PR body was truncated due to platform limits.

This PR contains the following updates:

Package Change Age Confidence Type Update
@1stg/eslint-config (source) ^10.3.1 → ^12.0.0 age confidence devDependencies major
@1stg/prettier-config (source) ^5.4.0 → ^7.0.0 age confidence devDependencies major
@1stg/tsconfig (source) ^4.0.0 → ^5.0.0 age confidence devDependencies major
@changesets/changelog-github (source) ^0.7.0 → ^1.0.0 age confidence devDependencies major
@changesets/cli (source) ^2.31.0 → ^3.0.0 age confidence devDependencies major
@types/node (source) ^25.9.3 → ^26.0.0 age confidence devDependencies major
@vitest/coverage-v8 (source) ^4.1.9 → ^5.0.0 age confidence devDependencies major
actions/checkout v7.0.0 → v7.0.1 age confidence action patch
actions/setup-node v6.4.0 → v7.1.0 age confidence action major
actions/stale v10.3.0 → v11.0.0 age confidence action major
all-contributors-cli (source) ^6.26.1 → ^7.0.0 age confidence devDependencies major
changesets/action v1.9.0 → v2.1.2 age confidence action major
codecov/codecov-action v7.0.0 → v7.1.1 age confidence action minor
node (source) 24 → 26 age confidence major
typescript (source) ^6.0.3 → ^7.0.0 age confidence devDependencies major
vitest (source) ^4.1.9 → ^5.0.0 age confidence devDependencies major
yarn (source) 4.17.0 → 4.18.1 age confidence packageManager minor
yarn-berry-deduplicate (source) ^6.1.3 → ^7.0.0 age confidence devDependencies major

Release Notes

1stG/configs (@​1stg/eslint-config)

v12.0.1

Compare Source

Patch Changes
  • #​436 ac965ca Thanks @​JounQin! - Import eslint-plugin-oxlint statically and always apply its disable list.
    The oxlint: false option is removed because omitting Oxlint would silently
    skip those checks; Oxlint itself remains required through the plugin peer.

v12.0.0

Compare Source

Major Changes

  • #​415 a0276d4 Thanks @​JounQin! - feat!: defineConfig-based configs, Oxlint/Oxfmt and a thin ESLint

    Every remaining config package now exports a defineConfig(options) factory
    alongside the zero-config default. Options are explicit: the configs no longer
    rely on ambient CI, NODE_ENV, cwd or git state; defaults may detect the
    project structure or installed optional peers when defineConfig() is called.
    Options extend the native config types (OxfmtConfig, OxlintConfig,
    prettier.Config, stylelint.Config, postcss.ProcessOptions, ...), so
    tool-specific fields pass through without being re-declared.

    • @1stg/eslint-config now only covers the file types Oxlint cannot parse
      (Markdown/JSON/YAML/TOML) and uses eslint-plugin-oxlint to avoid duplicate
      reports; Markdown/JSON(C) and eslint-plugin-oxlint are installed by default,
      YAML/TOML are optional peers, and eslint-plugin-markup can lint HTML on
      Node >= 24 when installed.
      @1stg/babel-preset is removed and JS/TS/Vue parsing moves to
      @1stg/oxlint-config.
    • New @1stg/oxlint-config (Oxlint) and
      @1stg/oxfmt-config (Oxfmt). Framework plugins are
      enabled when the framework is installed; formatting is no longer an ESLint
      rule by default.
    • @1stg/prettier-config is kept for the languages Oxfmt cannot format (Pug,
      Ruby, shell, INI, properties, Stylus, Sass). Its plugins are optional peer
      dependencies (discovered from this package's dependencies + optional
      peerDependencies), with prettier-plugin-pkg installed by default; the
      /next (babel-ts) variant is gone with Babel.
    • @1stg/nano-staged takes formatter ('oxfmt' | 'prettier' | 'both'),
      linter ('oxlint' | 'eslint') and typecheck options instead of
      per-framework entry points (/tsc, /ngc, /vue-tsc). Linter, stylelint,
      type-coverage and imagemin are auto-detected from installed packages.
    • @1stg/stylelint-config takes scss, scssLoose, modules and prettier
      options; stylelint-prettier is an optional peer enabled when installed, and
      vue is enabled when vue is installed.
    • @1stg/markuplint-config takes vue instead of the /angular and /vue
      subpaths. Angular support is dropped, including the @1stg/tsconfig/angular
      and ng-lib presets.
    • @1stg/commitlint-config takes monorepo (defaulting to isMonorepo());
      @1stg/simple-git-hooks takes runner and only emits hooks for installed
      nano-staged/@commitlint/cli.
    • @1stg/postcss-config is ESM only (use postcss.config.js), minifies based
      on its env option rather than a module-level NODE_ENV snapshot, and extends
      postcss.ProcessOptions; accepts minify, map, cssnano, presetOptions
      and extra plugins.
    • All packages are authored in TypeScript and built with tsc -b into lib/;
      declarations are generated, the hand-written .d.ts files are gone, and
      yarn build runs on install and release.
    • All packages publish explicit exports.types, a files allow-list, and
      consistent Node.js engines.
    • @1stg/browserslist-config is ESM only (browserslist >= 4.24.5) and drops
      the alauda and alauda-legacy presets.
Minor Changes
  • #​421 e3b113d Thanks @​JounQin! - Add a code mode that lints JS/TS/JSX with typescript-eslint and
    optional eslint-plugin-regexp / eslint-plugin-sonarjs, while eslint-plugin-oxlint keeps rules
    already covered by Oxlint disabled. It is enabled automatically when typescript-eslint is installed; pass
    code: false to disable it.

v11.1.0

Compare Source

Minor Changes

  • #​408 f84e555 Thanks @​renovate! - chore(deps): bump eslint-plugin-markup to v2 and require Node.js >=24.11.0

    eslint-plugin-markup@2 needs Node.js >=24, so @1stg/eslint-config now
    declares the intersection of its dependencies' engines. The plugin also moves to
    markuplint@^5, which removes the duplicate markuplint 4 tree that the previous
    release carried alongside markuplint 5.

v11.0.0

Compare Source

Major Changes

  • #​399 15ea175 Thanks @​renovate! - chore(deps): bump all dependencies, require Node.js ^22.18.0 || >=24.11.0

    • Every configuration package now requires Node.js ^22.18.0 || >=24.11.0,
      following Babel 8's own engines.
    • @1stg/babel-preset now requires @babel/core@^8 and is ESM only, the
      removed preset-env bugfixes/useBuiltIns/corejs options are replaced by
      babel-plugin-polyfill-corejs3, and the decorators legacy /
      decoratorsBeforeExport options are replaced by Babel 8's version.
    • babel-preset-proposal-typescript v5 brings native Babel 8 support, so
      @1stg/babel-preset no longer needs the local patch-package patch nor the
      resolutions that forced its Babel 7 plugins onto Babel 8.
    • The async option was removed together with
      babel-plugin-transform-async-to-promises and fast-async, which are no
      longer maintained and do not work with Babel 8. async/await is now left to
      @babel/preset-env, so the configured targets keep native async/await
      instead of being rewritten to promise chains.
    • typescript@7 (the native compiler) is installed as @typescript/native,
      while typescript aliases @typescript/typescript6 for the JS API that the
      lint tool chain still requires.
Minor Changes

  • #​407 ad663dd Thanks @​renovate! - chore(deps): bump all dependencies

    • @1stg/markuplint-config now requires markuplint@^5 and ships
      @markuplint/vue-parser/@markuplint/vue-spec v5.
    • @1stg/eslint-config, @1stg/postcss-config, @1stg/prettier-config and
      @1stg/stylelint-config bump their parser/plugin majors:
      eslint-plugin-simple-import-sort@14, cssnano@9 with postcss-import@17,
      prettier-plugin-toml@3 with prettier-plugin-sh@0.20, and postcss-html@2
      with postcss-markdown@2.
    • @1stg/nano-staged now requires prettier@^3.9.10, which the workspace
      resolves through a single resolutions-free prettier entry.
    • Releases are published with npm provenance: changeset publish shells out
      to yarn npm publish, which now runs with npmPublishProvenance: true and
      the id-token: write permission the release workflow already grants.

v10.3.2

Compare Source

Patch Changes
changesets/changesets (@​changesets/changelog-github)

v1.0.1

Compare Source

Patch Changes

v1.0.0

Compare Source

Major Changes
Minor Changes

  • #​2059 070f531 Thanks @​jycouet! - Add an opt-in, experimental template option to render changelog lines from tokens ({summary}, {ref}, {pull}, {commit}, {authors}). Default output is unchanged. The token syntax may change in a patch release; pin the version if you rely on it.

  • #​1871 dfefc4e Thanks @​mihkeleidast! - Use GITHUB_REPOSITORY as the default repo when no repo option is configured

  • #​1969 2c7c043 Thanks @​marcalexiei! - Add a named export that mirrors the current default export

    The default export is slated for removal in the next major release, so this ensures a smoother transition path.

Patch Changes
changesets/changesets (@​changesets/cli)

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

  • #​2128 7113c01 Thanks @​Andarist! - Renamed the changeset tag command to changeset git-tag.

  • #​2074 3599e47 Thanks @​bluwy! - Set supported package manager versions in "engines" field, including npm >=10.9.0, pnpm >=10.0.0, and yarn >=4.5.2.

  • #​1860 92b1c1b Thanks @​mixelburg! - changeset version now exits with code 1 when there are no unreleased changesets, instead of silently exiting with code 0.

    This makes it easier to detect when a version step is a no-op — for example, to prevent accidentally publishing packages with incorrect version tags when using --snapshot mode.

  • #​1482 df424a4 Thanks @​Andarist! - Bumped supported Node versions to ^22.11 || ^24 || >=26

  • #​1994 062530b Thanks @​bluwy! - The prettier option in .changeset/config.json has been removed in favor of format. format supports "auto", "prettier", "oxfmt", "deno", and "dprint", and false disables formatting. If you previously used prettier: false, migrate to format: false or remove the option to use automatic formatter detection.

  • #​2190 96b65ee Thanks @​bluwy! - Move versioned prerelease changesets to .changeset/pre/ folder instead of accumulating in the root and tracking the versioned changeset ids in the .changeset/pre.json file. Existing pre.json will auto-migrate to this new structure on the next run of changeset version or when calling changeset status.

    This change allows easier management of versioned prerelease changesets (for the final stable release) and current queued changesets (for the next prerelease). Changesets in .changeset/pre/ can be edited or deleted depending if it's still relevant for the final stable release of a package. There's no need to synchronize the changeset ids in pre.json if certain changesets are deleted.

  • #​2145 f5887ff Thanks @​Andarist! - Removed Yarn Classic support

  • #​2097 8c88f6a Thanks @​Andarist! - Packages with only prerelease versions published will now be published with the prerelease tag in the prerelease mode if the target registry doesn't auto-assign latest tag. npm registry itself does that and such packages will continue to be released with latest tag (and not with the configured prerelease tag).

  • #​1879 c76b232 Thanks @​beeequeue! - Removed warning messages about using v1 configs. They will now be silently ignored.

  • #​1655 db46911 Thanks @​bluwy! - Update @manypkg/get-packages which drops support for detecting packages in Bolt monorepos and adds support for npm monorepos

  • #​1651 e1df862 Thanks @​bluwy! - Remove support for the --sinceMaster flag for changeset status. Use --since=master or --since=main instead.

  • #​2117 813bbf3 Thanks @​bluwy! - Remove the pre.json initialVersions property and handling as it's unused internally

  • #​1961 07278a7 Thanks @​beeequeue! - CommitFunctions can now be both sync and async, and the defaultCommitFunctions are now sync.

  • #​1482 df424a4 Thanks @​Andarist! - From now on this package is going to be published as ES module.

  • #​1652 a0b5326 Thanks @​bluwy! - Remove support for the deprecated ___experimentalUnsafeOptions_WILL_CHANGE_IN_PATCH.useCalculatedVersionForSnapshots config. The snapshot.useCalculatedVersion config should be used instead.

  • #​2186 3910adf Thanks @​Andarist! - Private packages are no longer versioned by default. Set privatePackages to true to opt into versioning and tagging them, or set privatePackages.version to true to version them without tagging.

  • #​1879 c76b232 Thanks @​beeequeue! - Migrated from enquirer + @inquirer/launch-editor to @clack/prompts + launch-editor.

    This means the CLI flows will have minor changes, but they are largely the same.

    This change also fixes various issues related to enquirer like cancelling prompts crashing the CLI.

  • #​2090 3aae903 Thanks @​beeequeue! - Peer dependencies now bump packages that depend on them by patch instead of major.

    This means a peer dependency update is no longer assumed (forced) to be a breaking change.

    If the dependent package is not compatible with the peer's new release you should manually add a major changeset describing why and how to migrate.

Minor Changes

  • #​1121 ce2095d Thanks @​Sh031224! - Added new --major, --minor, --patch flags to the add command.

  • #​2135 fd7724a Thanks @​youdie006! - Allow comma-separated values in array-valued CLI flags: the --major, --minor, and --patch flags of the add command, and the --ignore flag of the version command. For example, --minor pkg-a,pkg-b is now equivalent to --minor pkg-a --minor pkg-b. Surrounding whitespace is trimmed and empty entries are ignored.

  • #​2068 d03ffc1 Thanks @​bluwy! - Support {commit-short} placeholder for the snapshot.prereleaseTemplate config, which is a 7 character variant of {commit}

  • #​2061 c2db1dd Thanks @​Andarist! - Added a changeset publish-plan command to inspect which packages would be published or tagged, with optional JSON output.

  • #​2087 edc30c8 Thanks @​trueberryless! - Made the init command interactive. Running changeset init will now guide you through a set of intuitive prompts to configure your changelog generator, commit preferences, publish access, and base branch, rather than silently writing the default configuration file.

  • #​1969 2c7c043 Thanks @​marcalexiei! - Add a named export that mirrors the current default export

    The default export is slated for removal in the next major release, so this ensures a smoother transition path.

  • #​1879 c76b232 Thanks @​beeequeue! - Packages are now listed in alphabetical order when possible.

  • #​2129 369eb0b Thanks @​Andarist! - Commands supporting --output (such as status and publish-plan) can now be invoked with CHANGESETS_OUTPUT=path/to/file environment variable. This has the same effect as calling them with --output=path/to/file

  • #​2100 90b4ad0 Thanks @​Andarist! - Order releases into dependency-aware chunks so packages are grouped in publish order.

  • #​2136 2f9ca42 Thanks @​bluwy! - Remove confirmation prompt when adding a changeset. It will always add a changeset instead, and if the changeset is not desired, the user can edit or delete the file directly.

  • #​2155 5a8119b Thanks @​beeequeue! - Improved changeset publish failure handling. Errors are reported per package, successful publishes are still tagged when another package fails, and authentication retries avoid republishing completed packages.

  • #​2063 ed77176 Thanks @​Andarist! - Added changeset publish --from-pack-dir <dir> to publish packages from a previously created pack output directory.

  • #​2062 830443c Thanks @​Andarist! - Added a changeset pack command that requires --out-dir and writes publishable package tarballs plus an enriched publish-plan.json into that directory, either from the current workspace or from a saved publish plan via --from-plan.

  • #​1879 c76b232 Thanks @​beeequeue! - Choosing a change type now shows a preview of which part of the version it affects.

    Which packages should have a major (X.X.X) bump?

  • #​2129 369eb0b Thanks @​Andarist! - changeset publish and changeset tag can now be invoked with CHANGESETS_OUTPUT=path/to/file environment variable. They produce output in the NDJSON format.

  • #​2130 18bc470 Thanks @​beeequeue! - Allow unmatched glob patterns in the ignore config option.

  • #​2073 b9cbd80 Thanks @​bluwy! - Show if a package is private when selecting packages in changeset add

Patch Changes

v2.31.1

Compare Source

Patch Changes
  • #​2159 15cf592 Thanks @​ingvaldlorentzen! - Fixed already-published version detection with npm 12, which always wraps successful npm info --json output in an array. The unwrapped output made changeset publish treat every package as unpublished and fail attempting to republish existing versions.
vitest-dev/vitest (@&

[!IMPORTANT]
✂ PR body was truncated to here.

Configuration

📅 Schedule: (UTC)

  • Branch creation
    • Between 12:00 AM and 03:59 AM, on day 1 of the month (* 0-3 1 * *)
  • 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.

@changeset-bot

changeset-bot Bot commented Aug 1, 2026 •
edited
Loading

Copy link
Copy Markdown

⚠️ No Changeset found

Latest commit: 77718cb

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

@codesandbox-ci

codesandbox-ci Bot commented Aug 1, 2026 •
edited
Loading

Copy link
Copy Markdown

This pull request is automatically built and testable in CodeSandbox.

To see build info of the built libraries, click here or the icon next to each commit SHA.

@pkg-pr-new

pkg-pr-new Bot commented Aug 1, 2026 •
edited
Loading

Copy link
Copy Markdown

Open in StackBlitz

npm i https://pkg.pr.new/prettier-eslint@1219

commit: c32e160

@renovate
renovate Bot force-pushed the renovate/all branch 3 times, most recently from fcdb365 to a35c2f3 Compare August 14, 2026 21:50
@renovate
renovate Bot force-pushed the renovate/all branch 3 times, most recently from 160b4a0 to 85ff8e9 Compare August 20, 2026 06:25
@renovate
renovate Bot force-pushed the renovate/all branch 3 times, most recently from 1f9d1d9 to a83b479 Compare September 9, 2026 18:01
@coderabbitai

coderabbitai Bot commented Sep 10, 2026 •
edited
Loading

Copy link
Copy Markdown

Important

Review skipped

Bot user detected.

To trigger a single review, invoke the @coderabbitai review command.

Run configuration
  • Source mode: Auto
  • Repository: Unavailable
  • Branch: Unavailable
  • File: No configuration file from this repository applied
  • Commit: Unavailable
  • Layers: defaults
  • Review profile: CHILL
  • Plan: Advanced
  • Run ID: 6e514b3d-b75d-4329-b67d-7b795616331a

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

  • 🔍 Trigger review
  • Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands.

hamzahamidi
hamzahamidi requested changes Sep 12, 2026
View reviewed changes

@hamzahamidi hamzahamidi left a comment

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

CI fails on Node 20, 22, 24 and 26 and on autofix, two causes in this batch.

typescript ^7.0.0 (resolves 7.0.2): @typescript-eslint/typescript-estree 8.61.1 declares peer typescript: ">=4.8.4 <6.1.0" and crashes at load with TypeError: Cannot read properties of undefined (reading 'Cjs') in create-program/shared.js:59. That kills yarn lint and yarn format (tsc -b itself passes, and the test run is stopped by --kill-others-on-fail before it finishes).

@vitest/coverage-v8 ^5.0.0 with vitest still ^4.1.9: vitest warns "Running mixed versions is not supported and may lead into bugs". They have to move together.

@changesets/cli 3.0.2, @changesets/changelog-github 1.0.1 and changesets/action v2.1.2 are majors only exercised by the release workflow, so CI says nothing about them.

Fix on our side is a packageRules entry in renovate.json: hold typescript on ^6 until typescript-eslint supports 7, group vitest with @vitest/coverage-v8, and give changesets 3 its own PR. Yarn 4.18.0 and the actions bumps are fine.

@renovate
renovate Bot force-pushed the renovate/all branch 6 times, most recently from 194a099 to 6cca9f5 Compare September 17, 2026 01:28
@renovate
renovate Bot force-pushed the renovate/all branch 2 times, most recently from 56dea65 to 0451076 Compare September 30, 2026 23:45
@renovate
renovate Bot force-pushed the renovate/all branch 3 times, most recently from dd1082b to 86bf3ac Compare October 11, 2026 00:21
@renovate
renovate Bot force-pushed the renovate/all branch 2 times, most recently from c1db9cb to ea79a29 Compare October 15, 2026 12:55
@renovate
renovate Bot force-pushed the renovate/all branch 6 times, most recently from f46a1f0 to 2ffe73e Compare October 27, 2026 20:38
@renovate
renovate Bot force-pushed the renovate/all branch 2 times, most recently from 90b38c6 to 46582f8 Compare October 28, 2026 21:35
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@hamzahamidi hamzahamidi hamzahamidi requested changes

Requested changes must be addressed to merge this pull request.

Assignees

No one assigned

Labels

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

1 participant

@hamzahamidi