Skip to content

fix(deps): update all dependencies - #345

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

fix(deps): update all dependencies#345
renovate[bot] wants to merge 1 commit into
mainfrom
renovate/all

Conversation

@renovate

@renovate renovate Bot commented Jul 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
@​alauda/doc-stream-sdk 0.1.0 → 1.0.0 age confidence dependencies 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
@earendil-works/pi-agent-core (source) 0.84.3 → 0.99.1 age confidence dependencies minor
@earendil-works/pi-ai (source) 0.84.3 → 0.99.1 age confidence dependencies minor
@rsbuild/plugin-sass (source) ^1.5.2 → ^2.0.0 age confidence dependencies major
@rsbuild/plugin-yaml ^1.0.4 → ^2.0.0 age confidence dependencies major
@rspress/core (source) 2.0.12 → 2.0.23 age confidence dependencies patch
@rspress/plugin-algolia (source) 2.0.12 → 2.0.23 age confidence dependencies patch
@rspress/plugin-sitemap (source) 2.0.12 → 2.0.23 age confidence dependencies patch
@rspress/shared (source) 2.0.12 → 2.0.23 age confidence dependencies patch
@rstest/core (source) ^0.10.0 → ^0.12.0 age confidence devDependencies minor
@rstest/coverage-istanbul (source) ^0.10.0 → ^0.12.0 age confidence devDependencies minor
actions/checkout v6.0.2 → v7.0.1 age confidence action major
actions/setup-node v6.4.0 → v7.0.0 age confidence action major
changesets/action v1 → v2.1.2 age confidence action major
codecov/codecov-action v6 → v7 age confidence action major
commander ^14.0.3 → ^15.0.0 age confidence dependencies major
ejs ^5.0.2 → ^6.0.0 age confidence dependencies major
node (source) 24.15.0 → 24.21.0 age confidence minor
openai ^6.38.0 → ^7.0.0 age confidence dependencies major
simple-git (source) ^3.36.0 → ^4.0.0 age confidence dependencies major
typescript (source) ^6.0.3 → ^7.0.0 age confidence dependencies major
typescript (source) ^6.0.3 → ^7.0.0 age confidence devDependencies major
x-fetch ^0.2.6 → ^0.3.0 age confidence dependencies minor
yarn (source) 4.15.0 → 4.18.1 age confidence packageManager minor

Release Notes

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.
earendil-works/pi (@​earendil-works/pi-agent-core)

v0.99.1

Compare Source

v0.99.0

Compare Source

Added
  • Added the onProviderStreamEvent agent option, which is passed to provider streams to observe parsed provider events before normalization (#​9784, #​9901 by @​davidbrai).
  • The agent loop now records the requested thinking level as thinkingLevel on each assistant message.

v0.87.1

Compare Source

v0.87.0

Compare Source

Breaking Changes

  • Removed AgentOptions.shouldStopAfterTurn and AgentLoopConfig.shouldStopAfterTurn. Use finishTurn and return { action: "end" } to stop after the completed turn:

    // Before
shouldStopAfterTurn: async (turn, signal) => await shouldStop(turn, signal),

// After
finishTurn: async (turn, signal) => {
  // shouldStopAfterTurn previously ran only for normal responses.
  if (turn.message.stopReason === "error" || turn.message.stopReason === "aborted") return;
  return (await shouldStop(turn, signal)) ? { action: "end" } : undefined;
},

    finishTurn runs after the assistant and all tool results are finalized but before turn_end; its decision is applied after turn_end. It also runs for error and aborted responses, whose decisions are ignored because those responses remain hard exits. The guard in the migration preserves the old hook's normal-response-only invocation, including avoiding predicate side effects on hard exits. Returning { action: "end" } leaves steering and follow-up queues untouched and skips prepareNextTurn.

Added
  • Added prepareRequest, which runs before every provider request, including the first. For example, return { context: { ...context, messages: persistedMessages } } to install canonical context after already-selected input is emitted without introducing another queue poll.
  • Added finishTurn, which runs after assistant/tool-result finalization and before turn_end for normal, error, and aborted responses. Return { action: "end" } to end a normal run after turn_end, or undefined to preserve normal scheduling. { action: "continue" } ensures one next provider request: existing tool-result, steering, or follow-up scheduling can satisfy that request without adding another one; otherwise the loop makes one context-only request. Error and aborted responses remain hard exits.
  • Added Agent.peekQueuedMessages() to preview the next queue-selected batch without consuming it.
Fixed
  • Fixed harness reads misclassifying text files beginning with GIF as images (#​9755).

v0.86.1

Compare Source

v0.86.0

Compare Source

v0.85.1

Compare Source

v0.85.0

Compare Source

Fixed
  • Fixed proxied assistant responses dropping persisted provider-native thinking levels.
  • Fixed the write tool reporting UTF-16 code-unit counts as byte counts by removing the misleading count (#​8979).

v0.84.4

Compare Source

Breaking Changes
  • Changed prepareNextTurn and prepareNextTurnWithContext to run only after shouldStopAfterTurn and queued-message checks determine that the agent loop will start another assistant turn. They no longer run after final or terminating turns; move end-of-run work to agent_end handling (#​6879).
Fixed
  • Fixed Windows NodeExecutionEnv aborts crashing when taskkill.exe is unavailable on PATH (#​6596).
Removed
  • Removed the withdrawn manual-drive configuration, action inspection methods, action outcomes, and snapshot action field from AgentHarness.
earendil-works/pi (@​earendil-works/pi-ai)

v0.99.1

Compare Source

Added
  • Added GPT-6.1 Sol (gpt-6.1-sol) to the OpenAI, Azure OpenAI Responses, and OpenAI Codex providers.

v0.99.0

[Compare Source](https://redirect.github.com/earendil-works/pi/compare/v0.87.1...

❗ 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 Jul 1, 2026 •
edited
Loading

Copy link
Copy Markdown

⚠️ No Changeset found

Latest commit: b606c21

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

@renovate
renovate Bot force-pushed the renovate/all branch 6 times, most recently from 5ecf124 to 31c35ac Compare July 8, 2026 23:30
@renovate
renovate Bot force-pushed the renovate/all branch 4 times, most recently from 5e43391 to 5161e9a Compare July 15, 2026 12:01
@renovate
renovate Bot force-pushed the renovate/all branch 3 times, most recently from 4f40138 to cb79030 Compare July 21, 2026 00:32
@renovate
renovate Bot force-pushed the renovate/all branch 6 times, most recently from d4302b0 to b289a6c Compare July 30, 2026 10:47
@renovate
renovate Bot force-pushed the renovate/all branch 3 times, most recently from 8286b47 to 3d55e7e Compare August 5, 2026 11:15
@renovate
renovate Bot force-pushed the renovate/all branch 5 times, most recently from 7431c3f to 71dd41a Compare August 17, 2026 09:04
@renovate
renovate Bot force-pushed the renovate/all branch 2 times, most recently from 701f016 to 4a243b1 Compare August 20, 2026 09:12
@renovate
renovate Bot force-pushed the renovate/all branch 10 times, most recently from 28398fd to 4c75fe2 Compare September 10, 2026 22:46
@renovate
renovate Bot force-pushed the renovate/all branch 13 times, most recently from 4d667b3 to 1d8052c Compare September 20, 2026 12:28
@renovate
renovate Bot force-pushed the renovate/all branch 5 times, most recently from 2ce6d23 to 932255f Compare September 26, 2026 15:37
@renovate

renovate Bot commented Sep 29, 2026 •
edited
Loading

Copy link
Copy Markdown
Contributor Author

⚠️ 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: yarn.lock
➤ YN0000: · Yarn 4.18.1
➤ YN0000: ┌ Resolution step
➤ YN0016: │ @earendil-works/pi-agent-core@npm:0.99.1: All versions satisfying "0.99.1" are quarantined
➤ YN0000: └ Completed in 1s 615ms
➤ YN0000: · Failed with errors in 1s 627ms

This branch has not been deployed

No deployments
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