Skip to content

chore(deps): update all dependencies - #192

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

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

Conversation

@renovate

@renovate renovate Bot commented Apr 1, 2025 •
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/app-config (source) ^10.0.1 → ^15.0.0 age confidence devDependencies major
@changesets/changelog-github (source) ^0.5.0 → ^1.0.0 age confidence devDependencies major
@changesets/cli (source) ^2.27.1 → ^3.0.0 age confidence devDependencies major
@pkgr/rollup (source) ^6.0.0 → ^7.0.0 age confidence devDependencies major
@types/node (source) ^18.19.8 → ^24.0.0 age confidence devDependencies major
@types/web ^0.0.135 → ^0.0.354 age confidence devDependencies patch
@vitejs/plugin-vue-jsx (source) ^3.1.0 → ^5.0.0 age confidence devDependencies major
actions/checkout v4 → v7 age confidence action major
actions/setup-node v4 → v7 age confidence action major
changesets/action v1 → v2.1.0 age confidence action major
codecov/codecov-action v3 → v7 age confidence action major
github/codeql-action v3 → v4 age confidence action major
pkg-size/action → a637fb0 action pinDigest
rimraf ^5.0.5 → ^6.0.0 age confidence devDependencies major
typescript (source) ^5.3.3 → ^7.0.0 age confidence devDependencies major
vue-tsc (source) ^1.8.27 → ^3.0.0 age confidence devDependencies major
yarn 1.22.21 → 1.22.22 age confidence packageManager patch

Release Notes

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

v15.0.0

Compare Source

Major Changes
Patch Changes

v14.3.0

Compare Source

Minor Changes
Patch Changes

v14.2.0

Compare Source

Minor Changes
Patch Changes

v14.1.0

Compare Source

Minor Changes
Patch Changes

v14.0.0

Compare Source

Major Changes
Patch Changes

v13.1.0

Compare Source

Minor Changes
Patch Changes

v13.0.1

Compare Source

Patch Changes

v13.0.0

Compare Source

Major Changes
Patch Changes

v12.0.1

Compare Source

Patch Changes

v12.0.0

Compare Source

Major Changes
Patch Changes

v11.1.2

Compare Source

Patch Changes

v11.1.1

Compare Source

Patch Changes

v11.1.0

Compare Source

Minor Changes
Patch Changes

v11.0.3

Compare Source

Patch Changes

v11.0.2

Compare Source

Patch Changes

v11.0.1

Compare Source

Patch Changes

v11.0.0

Compare Source

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

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

v0.7.0

Compare Source

Minor Changes

v0.6.0

Compare Source

Minor Changes
Patch Changes

v0.5.2

Compare Source

Patch Changes

v0.5.1

Compare Source

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

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

  • #​1476 e0e1748 Thanks @​pralkarz! - Replace fs-extra usage with node:fs

  • #​2060 11bded4 Thanks @​Andarist! - Fixed changeset publish to respect ignored packages for both publishing and private package tagging.

  • #​2041 ce39c72 Thanks @​bluwy! - Enable guide line for add command and use box design for dependent patch bump note

  • #​2064 ffd65fc Thanks @​Andarist! - For pnpm projects, Changesets now match pnpm's native registry behavior more closely during unpublished package checks. Both scope-based publishConfig registry overrides and publishConfig.registry are now ignored.

  • #​2002 6db2c21 Thanks @​Andarist! - Lazy-load CLI commands so changeset only loads the code needed for the command being run.

  • #​2097 8c88f6a Thanks @​Andarist! - Route package manager calls through their respective CLIs during publish (npm, pnpm, yarn). Notably, Yarn Berry publishes now let Yarn update workspace protocol ranges as part of the publish process.

  • #​2132 d35bb77 Thanks @​cyphercodes! - Improve publish error handling for npm and pnpm JSON errors. Changesets now skips npm 11 already-published errors that omit code, correctly skips pnpm 11 already-published errors, and retries pnpm 11 ERR_PNPM_OTP_NON_INTERACTIVE publish failures in delegated interactive mode.

  • #​2160 162419d Thanks @​beeequeue! - Added or modified the files property in the manifest. This should not change any behavior.

  • #​2009 44df27d Thanks @​bluwy! - Use cac for CLI arg parsing and handling

  • #​2113 b8222e6 Thanks @​Andarist! - Fixed publish error printing for pnpm 11.

  • #​2065 0598e83 Thanks @​Andarist! - Improved changeset publish auth handling by removing the preflight OTP requirement check and falling back to interactive auth when the package manager reports that authentication is required.

  • #​2065 0598e83 Thanks @​Andarist! - changeset publish now reads initial OTP values from npm and pnpm environment variables.

  • #​2171 3257f57 Thanks @​beeequeue! - Enabled Node's Compile Cache to improve CLI startup speed.

  • #​1570 d099e43 Thanks @​pralkarz! - Removed extra leftover code related to Changesets v1

  • #​2113 b8222e6 Thanks @​Andarist! - Fixed accidental success logs on failed npm publishes

  • #​1616 609046c Thanks @​bluwy! - Remove term-size dependency

  • #​1476 e0e1748 Thanks @​pralkarz! - Replaced spawndamnit with tinyexec

  • #​584 6c79210 Thanks @​Andarist! - Avoid an infinite loop when git commands fail to execute when Changesets try to retrieve commits that added files.

  • #​2177 b5e1762 Thanks @​Andarist! - Avoid writing an undefined version when updating dependencies in unversioned private packa

✂ Note

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 Apr 1, 2025 •
edited
Loading

Copy link
Copy Markdown

⚠️ No Changeset found

Latest commit: b385a00

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

@vercel

vercel Bot commented Apr 1, 2025 •
edited
Loading

Copy link
Copy Markdown

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Preview Comments Updated (UTC)
vue Error Error Nov 8, 2025 6:03am

@coderabbitai

coderabbitai Bot commented Apr 1, 2025 •
edited
Loading

Copy link
Copy Markdown

Important

Review skipped

Bot user detected.

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

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

  • 🔍 Trigger a full review

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

@socket-security

socket-security Bot commented Apr 1, 2025 •
edited
Loading

Copy link
Copy Markdown

Warning

Review the following alerts detected in dependencies.

According to your organization's Security Policy, it is recommended to resolve "Warn" alerts. Learn more about Socket for GitHub.

Action Severity Alert  (click "▶" to expand/collapse)
Warn High
Obfuscated code: npm chrono-node is 90.0% likely obfuscated

Confidence: 0.90

Location: Package overview

From: yarn.lock → npm/@1stg/app-config@15.0.0 → npm/chrono-node@2.9.0

ℹ Read more on: This package | This alert | What is obfuscated code?

Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev.

Suggestion: Packages should not obfuscate their code. Consider not using packages with obfuscated code.

Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/chrono-node@2.9.0. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.

Warn High
Obfuscated code: npm yargs is 90.0% likely obfuscated

Confidence: 0.90

Location: Package overview

From: yarn.lock → npm/@1stg/app-config@15.0.0 → npm/yargs@17.7.3

ℹ Read more on: This package | This alert | What is obfuscated code?

Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev.

Suggestion: Packages should not obfuscate their code. Consider not using packages with obfuscated code.

Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/yargs@17.7.3. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.

View full report

@renovate
renovate Bot force-pushed the renovate/all branch from b2f20e5 to 45a70bc Compare May 6, 2025 07:45
@renovate
renovate Bot force-pushed the renovate/all branch from 45a70bc to d4148f4 Compare May 9, 2025 07:29
@renovate
renovate Bot force-pushed the renovate/all branch from d4148f4 to 582854e Compare May 15, 2025 06:49
@renovate
renovate Bot force-pushed the renovate/all branch from 582854e to 1d597a6 Compare May 16, 2025 16:51
@renovate
renovate Bot force-pushed the renovate/all branch from 1d597a6 to 0ea588e Compare May 17, 2025 06:10
@renovate
renovate Bot force-pushed the renovate/all branch from 0ea588e to 8a77d2d Compare May 18, 2025 13:23
@renovate
renovate Bot force-pushed the renovate/all branch from 8a77d2d to 2c7acc4 Compare May 29, 2025 05:51
@renovate
renovate Bot force-pushed the renovate/all branch from 2c7acc4 to 811f1aa Compare June 1, 2025 04:27
@renovate
renovate Bot force-pushed the renovate/all branch from 811f1aa to a3b0709 Compare June 1, 2025 09:04
@renovate
renovate Bot force-pushed the renovate/all branch from a3b0709 to d1d8997 Compare June 3, 2025 14:02
@renovate
renovate Bot force-pushed the renovate/all branch from d1d8997 to 0821c1c Compare June 4, 2025 06:54
@renovate
renovate Bot force-pushed the renovate/all branch from 0821c1c to 6677b6b Compare June 5, 2025 06:47
@renovate
renovate Bot force-pushed the renovate/all branch from 6677b6b to 0b8d05f Compare June 9, 2025 06:47
@socket-security

socket-security Bot commented Aug 8, 2025 •
edited
Loading

Copy link
Copy Markdown

Review the following changes in direct dependencies. Learn more about Socket for GitHub.

Diff Package Supply Chain
Security		 Vulnerability Quality Maintenance License
Updated@​1stg/​app-config@​10.0.1 ⏵ 15.0.053 +510053 +588 +4100
Updated@​pkgr/​rollup@​6.0.0 ⏵ 7.1.073 +11006788 +7100
Updated@​changesets/​cli@​2.27.1 ⏵ 3.0.099 +210074 -2597 +2100
Updated@​types/​node@​12.20.47 ⏵ 24.13.310010081 +196100
Updatedpostcss@​8.4.33 ⏵ 8.5.26100 +1100 +248294 -1100
Updatedrimraf@​2.7.1 ⏵ 6.1.3100100100 +183 +33100
Updatedtslib@​2.6.2 ⏵ 2.8.1100100100 +186100
Updated@​vitejs/​plugin-vue-jsx@​3.1.0 ⏵ 5.1.6100100100 +888 -4100
Updatedtypescript@​5.3.3 ⏵ 7.0.29910089 -1100 +5100 +10
Updated@​types/​web@​0.0.135 ⏵ 0.0.35410010090 +296 +1100
Updatedvue-tsc@​1.8.27 ⏵ 3.3.10100 +1210091 +1397 +1100
Updated@​changesets/​changelog-github@​0.5.0 ⏵ 1.0.0100 +110095 +2896 +3100

View full report

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

No reviews

Assignees

No one assigned

Labels

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

0 participants