chore(deps): update all non-major dependencies - #55
Open
tagoro9-renovatebot[bot] wants to merge 1 commit into
Open
chore(deps): update all non-major dependencies#55tagoro9-renovatebot[bot] wants to merge 1 commit into
tagoro9-renovatebot[bot] wants to merge 1 commit into
Conversation
Contributor
Author
|
tagoro9-renovatebot
Bot
force-pushed
the
c/renovate_all-minor-patch
branch
4 times, most recently
from
August 20, 2026 00:29
9e1059d to
9ebc091
Compare
tagoro9-renovatebot
Bot
force-pushed
the
c/renovate_all-minor-patch
branch
from
August 21, 2026 00:32
9ebc091 to
6c6d76a
Compare
tagoro9-renovatebot
Bot
force-pushed
the
c/renovate_all-minor-patch
branch
from
August 27, 2026 05:19
6c6d76a to
8fbddf6
Compare
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.
This PR contains the following updates:
2.1.0→2.3.00.45.0→0.45.118.18.1→18.19.01.3.14→1.4.02.70.5→2.72.03.76.1→3.76.50.74.2→0.74.316.1.0→16.2.02.97.0→2.98.01.26.5→1.27.03.5.5→3.7.22.12.2→2.13.13.5.2→3.5.34.2.3→4.2.40.36.0→0.38.40.63.1→0.64.12026.7.17→2026.8.68.4.10→8.4.11v1.21.1→v1.21.21.18.11→1.18.211.7.0→1.10.00.83.0→0.84.218.4→18.61.15.8→1.16.00.38.7→0.39.00.12.1→0.12.526.5.6→26.8.150.44.3→0.45.0Release Notes
atuinsh/atuin (atuin)
v18.19.0Bug Fixes
atuin config set(#3766)Documentation
Features
atuin config setbefore writing them to disk (#3769)atuin lab shareupdatea real subcommand (#3813)Miscellaneous Tasks
packagestep (#3770)OrFilteras a replacement forVecs as filter lists (#3768)atuin-domaincrate for shared domain types (#3790)Refactor
Testing
Daemon
oven-sh/bun (bun)
v1.4.0: Bun v1.4Compare Source
To install Bun v1.4
Windows:
powershell -c "irm bun.com/install.ps1|iex"To upgrade to Bun v1.4.0:
Read the blog post:
Thank you
Bun is free, open source, and MIT-licensed. We receive a lot of contributions from the community, and we'd like to thank everyone who fixed a bug or contributed since Bun v1.3.
junegunn/fzf (fzf)
v0.74.3chafadoes under tmux (#4885)replace-querycorrupting the item text when the query is edited afterwardsgolang/go (go)
v1.27.0Compare Source
v1.26.7Compare Source
v1.26.6Compare Source
vektra/mockery (go-mockery)
v3.7.2What's Changed
New Contributors
Full Changelog: vektra/mockery@v3.7.1...v3.7.2
helm/helm (kubernetes-helm)
v4.2.4: Helm v4.2.4Helm v4.2.4 is a patch release. Users are encouraged to upgrade for the best experience.
The community keeps growing, and we'd love to see you there!
Notable Changes
Installation and Upgrading
Download Helm v4.2.4. The common platform binaries are here:
This release was signed with
208D D36E D5BB 3745 A167 43A4 C7C6 FBB5 B91C 1155and can be found at @scottrigby keybase account. Please use the attached signatures for verifying this release usinggpg.The Quickstart Guide will get you going from there. For upgrade instructions or detailed installation notes, check the install guide. You can also use a script to install on any system with
bash.What's Next
Changelog
3900f43(Scott Rigby)f7c6e8f(Terry Howe)035a2c3(dependabot[bot])f76a5f4(Gates Wang)5a7c6c7(Will Noble)2281848(Will Noble)2c979a1(Jakub Jaruszewski)2bd2c66(kimsungmin1)183a540(kimsm28)08d8da1(kimsm28)9655b5a(kimsm28)430dfac(Terry Howe)9569605(kimsm28)63f2b68(kimsm28)f7488c0(kimsm28)8fe78fb(kimsm28)d0670d2(kimsm28)804256e(kimsungmin1)d79bceb(kimsungmin1)d34fcd9(kimsungmin1)9fbd190(kimsungmin1)9275661(kimsungmin1)fef91f3(kimsungmin1)e89ce68(Mohammad Abdolirad)ff1ac83(Sebastien Tardif)4b4dedb(Sebastien Tardif)7c80103(Sebastien Tardif)ecc9cd2(Jeaeun Kim)f6211ba(Jeaeun Kim)3507ea5(Jeaeun Kim)helm template --debugwith--show-only211ffae(Jeaeun Kim)51a9837(Matheus Pimenta)83a8b70(Matheus Pimenta)Full Changelog: helm/helm@v4.2.3...v4.2.4
bitnami/sealed-secrets (kubeseal)
v0.38.4jesseduffield/lazygit (lazygit)
v0.64.1What's Changed
This fixes a few regressions that were introduced in the last release, and some long-standing bugs that I didn't see any reason to hold back until the next big one.
Fixes 🔧
Maintenance ⚙️
Full Changelog: jesseduffield/lazygit@v0.64.0...v0.64.1
v0.64.0What's Changed
This release has massive changes, but most of them should hopefully not be visible: I completely overhauled lazygit's concurrency model, which was, let's say, less than robust; there were lots of data races, and we were just lucky that this didn't result in crashes or misbehavior more often. We now have a robust concurrency model with no known data races, and in fact we run our integration test suite on CI with the
-raceflag to prove that. The user visible part of this is that some operations run a little more smoothly now; for example, there used to be an ugly spinner freeze at the end of checking out a branch, which is now gone.However, since the changes were so massive there's a higher-than-usual chance of regressions, so please report any that you find.
Apart from that, we also have a few useful enhancements; the most notable one is probably that we now show the Github checks status of pull requests in the branches panel.
Enhancements 🔥
{{diffContext}}template variable in external diff command by @stefanhaller in #5841Fixes 🔧
Maintenance ⚙️
Docs 📖
I18n 🌎
Performance Improvements 📊
New Contributors
Full Changelog: jesseduffield/lazygit@v0.63.1...v0.64.0
open-turo/renovate-config (open-turo/renovate-config)
v1.21.2Compare Source
Bug Fixes
anomalyco/opencode (opencode)
v1.18.21Core
Bugfixes
euandusmulti-region Gemini requests through REP endpointsDesktop
Bugfixes
Thank you to 1 community contributor:
v1.18.18Core
Bugfixes
v1.18.16Core
Bugfixes
Desktop
Improvements
Bugfixes
Thank you to 1 community contributor:
v1.18.13TUI
Bugfixes
Desktop
Bugfixes
Improvements
Thank you to 1 community contributor:
Fission-AI/OpenSpec (openspec)
v1.10.0Minor Changes
c747ed1Thanks @clay-good! - Addopenspec init --language <language>to configure the language used for artifacts in new projects.Patch Changes
#1704
7276c6cThanks @clay-good! - Drop the npmpostinstallscript. Its only job was printing a one-line tip about opt-in shell completions, but shipping any install script madenpm install -g @fission-ai/openspecemit anallow-scriptswarning that reads as a packaging fault (andnpm approve-scriptsthen fails withENOMATCHon a global install, since it looks in the local project). The tip now prints from the CLI on its first run — to stderr, in an interactive terminal, once, and not at all if you already have completions installed — and the published package declares nopreinstall/install/postinstallscript, so a registry install runs no OpenSpec code. Suppress the tip withOPENSPEC_NO_COMPLETIONS=1.#1656
a72a74dThanks @clay-good! - ### Bug Fixesopenspec updatenow suggests restarting an IDE only when it updates an IDE-resident tool. CLI tools such as Claude Code, Codex, and Gemini CLI no longer show an unnecessary restart hint.#1703
9643888Thanks @clay-good! - Point the spec-drivenspecsinstruction's main-spec read and edit at the store-aware root. It namedopenspec/specs/<capability-path>/spec.md, a path relative to the current directory, for both step 1 of the MODIFIED workflow ("locate the existing requirement") and the edit that fixes a leftoverTBDPurpose. When the change lives in a store — whether selected with--store, a projectstore:pointer, or a global default store — the main spec is under the store root, so that read missed it, or silently returned a different capability when a local one happened to share the name, and the MODIFIED block was then copied from the wrong requirement. Both operations now use<planningHome.root>/openspec/specs/..., the root already returned byopenspec instructions ... --jsonand the same convention the sync and archive workflows use. Fixes #1702.#1699
18688c8Thanks @clay-good! - archive: tell the author how to retire a capability when the emptied spec also holds content the merge cannot account for. That combination printed only "Spec must have at least one requirement" and no guidance at all; the abort now names the blocking lines and reports aretire_capabilitiesmarker that is present but cannot be honored. Authored content quoted in those messages - the blocking lines, and the marker's own reason, whichopenspec validateprints too - is stripped of control characters and bounded in length before it reaches the terminal.#1660
7da3f34Thanks @clay-good! - Require generated tasks to state how their completion can be verified.v1.8.0Minor Changes
#1303
1aa0f2aThanks @solanab! - Add the vendor-neutralagentstarget:openspec init --tools agentsinstalls the workflow skills to.agents/skills/openspec-*/SKILL.md, the shared location AGENTS.md-compatible assistants read. It is skills-only, so no slash commands are generated. Becauseagentsis now a real target,--tools allincludes it and creates.agents/skills/where it previously did not.#1274
7a4a745Thanks @NicoAvanzDev! - Generate GitHub Copilot coding agent setup and custom agent files duringopenspec initand keep them synchronized duringopenspec update.#1214
161f945Thanks @showms! - Add MiniMax Code as a global skills-only tool target.#1518
568e56cThanks @clay-good! - ### New Featuresopenspec init --tools rovodevinstalls the OpenSpec workflow skills for Atlassian's Rovo Dev CLI. It is skills-only (no slash commands), written to.rovodev.Bug Fixes
Codex skills now live in the shared
.agentsdirectory —openspec initandopenspec updateinstall Codex skills under.agents/skills/(the canonical location assistants read) and migrate an existing.codexskills directory in place. Files you customized are preserved, not overwritten.openspec statusseparates planning from implementation — status now reportsisPlanningComplete(every non-skipped planning artifact exists; skipped artifacts count as satisfied without being written) distinctly from overall progress, and its messages no longer imply a change is finished before it has been implemented.isCompleteis kept as a compatibility alias, so existing scripts keep working.#1517
73207a6Thanks @clay-good! - Make GitHub Copilot cloud coding-agent files opt-in. Selecting thegithub-copilottool no longer silently writes a GitHub Actions workflow into.github/;openspec initnow asks first (default No) and remembers the choice inopenspec/config.yaml(githubCopilot.cloudAgent). Use--copilot-cloud/--no-copilot-cloudto decide non-interactively.openspec updatenever prompts — it only refreshes cloud files for projects that opted in (or that already have generated cloud files, so existing setups keep working).--no-copilot-cloudorcloudAgent: false) removes OpenSpec-managed cloud files; a user-customized file is always preserved, never overwritten or deleted.initandupdatenow report whether cloud files were written, skipped, or left untouched — and if you already have your owncopilot-setup-steps.yml, they say it was preserved and that you need to add the OpenSpec install step by hand.#1484
521ee33Thanks @clay-good! - Retire a capability when a change removes its last requirement. A change that declaresretire_capabilities: truein its.openspec.yaml(alongside theschema:that file requires) may now be archived even when its REMOVED entries take a capability's last requirement:openspec archivedeletes that capability's main spec instead of aborting with "Spec must have at least one requirement". Without the marker nothing changes — the archive aborts exactly as before, except the message now names the marker as the way out. Retirement happens only when the emptied spec could not have been written at all, every one is named in the archive output, a pasteablegit checkoutis included when the spec lived in the caller's checkout, and--no-validatenever retires. Archive now also rejects a main spec with duplicate canonical requirement names instead of letting delta reconciliation collapse one of the duplicate blocks. One thing to know before retiring: a capability's spec is the base another change's MODIFIED block is checked against, so an in-flight change that modifies the capability you just retired will keep validating clean and then refuse to archive ("target spec does not exist; only ADDED requirements are allowed for new specs") — close or rework that change alongside the retirement.Patch Changes
#1502
ece8660Thanks @clay-good! -openspec validatenow treats the EnglishSHALL/MUSTconvention as guidance in normal mode, so requirements written in other languages can validate. Strict mode continues to enforce the convention.#1483 [
2b3d368]Configuration
📅 Schedule: (UTC)
🚦 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.
This PR has been generated by Mend Renovate CLI.