build(deps): bump @opentui/solid from 0.3.0 to 0.3.1#56
Closed
dependabot[bot] wants to merge 1 commit into
Closed
Conversation
Bumps [@opentui/solid](https://github.com/anomalyco/opentui/tree/HEAD/packages/solid) from 0.3.0 to 0.3.1. - [Release notes](https://github.com/anomalyco/opentui/releases) - [Commits](https://github.com/anomalyco/opentui/commits/v0.3.1/packages/solid) --- updated-dependencies: - dependency-name: "@opentui/solid" dependency-version: 0.3.1 dependency-type: direct:production update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com>
|
Review the following changes in direct dependencies. Learn more about Socket for GitHub.
|
Contributor
|
Closed as superseded by the combined dependency update in f5876fa, which applies these bumps together to avoid bun.lock conflicts. |
Author
|
OK, I won't notify you again about this release, but will get in touch when a new version is available. If you'd rather skip all updates until the next major or minor version, let me know by commenting If you change your mind, just re-open this PR and I'll resolve any conflicts on it. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Bumps @opentui/solid from 0.3.0 to 0.3.1.
Release notes
Sourced from @opentui/solid's releases.
Commits
2d4de31Release v0.3.1Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting
@dependabot rebase.Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
@dependabot rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@dependabot ignore this major versionwill close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this minor versionwill close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this dependencywill close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)Need help on this PR? Tag
/codesmithwith what you need. Autofix is disabled.Summary by cubic
Bump
@opentui/solidto 0.3.1 to pick up the renderer’s split-footer replay reset and align with the latest@opentui/core.@opentui/solid0.3.0 → 0.3.1 and setpackages/opencoderange to>=0.3.1.@opentui/coreand its platform builds to 0.3.1 for compatibility.Written for commit 017e5a7. Summary will update on new commits.
Greptile Summary
This Dependabot PR bumps
@opentui/solidfrom 0.3.0 to 0.3.1 (a patch release adding split-footer replay reset) and tightens the minimum version constraint inpackages/opencode/package.jsonfrom>=0.1.92to>=0.3.1.@opentui/coreand all its platform-specific optional packages are also bumped from 0.3.0 to 0.3.1 inbun.lock, which is expected since@opentui/solid@0.3.1depends on@opentui/core@0.3.1.Confidence Score: 4/5
Safe to merge — the dependency bump is a patch release with a small additive feature, and no functional code is changed.
The only substantive question is whether the unrelated workspace version bump (1.4.1→1.5.0) in the lockfile is intentional; if the manifest files already carried 1.5.0 before this PR, the lockfile was simply catching up and there is no real risk.
bun.lock — confirm the workspace package version advancement from 1.4.1 to 1.5.0 was expected.
Important Files Changed
Flowchart
%%{init: {'theme': 'neutral'}}%% flowchart TD A["Dependabot triggers bun install"] --> B["@opentui/solid 0.3.0 → 0.3.1"] B --> C["@opentui/core 0.3.0 → 0.3.1\n(transitive peer dep)"] A --> D["bun.lock regenerated"] D --> E["Workspace packages synced\n1.4.1 → 1.5.0\n(pre-existing lockfile drift)"] B --> F["package.json constraint updated\n>=0.1.92 → >=0.3.1"]Comments Outside Diff (1)
bun.lock, line 22-56 (link)The lockfile regeneration also advanced all three workspace packages (
@cortexkit/anthropic-auth-core,@cortexkit/opencode-anthropic-auth,@cortexkit/pi-anthropic-auth) from1.4.1to1.5.0. These changes are unrelated to the@opentui/solid0.3.0→0.3.1 bump. This suggests the lockfile was previously out of sync with the workspacepackage.jsonmanifests, and Dependabot'sbun installrun picked up the drift. Worth confirming the1.5.0workspace versions are intentional before merging.Note: If this suggestion doesn't match your team's coding style, reply to this and let me know. I'll remember it for next time!
Reviews (1): Last reviewed commit: "build(deps): bump @opentui/solid from 0...." | Re-trigger Greptile