Repository navigation
build(deps): update all non-major dependencies - #52
Merged
Merged
Conversation
|
Important Review skippedBot user detected. To trigger a single review, invoke the
|
1 similar comment
|
Important Review skippedBot user detected. To trigger a single review, invoke the
|
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:
3.27.3→3.28.02026.10.15→2026.10.17v2026.10.19(+1)v5.2.1→v5.2.2v5.2.30.23.3→0.24.03.27.3→3.28.01.181.0→1.182.10.13.3→0.13.5Release Notes
erlang/rebar3
v3.28.0Compare Source
Few interface changes, but some significant behavioural ones:
Note that both the hex_core update and the certifi update are required for security. The removal of Certifi switches Rebar3 to use your operating system's root store, which may cause issues in some limited devices. However, since distrusted intermediary certificates are currently still in Certifi's hex package, we consider it safer to rely on operating system root stores.
If your device does not comply with the expected root store, you can configure one with
{ssl_cacerts_path, "/path/to/cacerts.pem"}.jdx/mise
v2026.10.17: : Shell names in bootstrap login_shell, templated doctor checks, and a per-plugin vfox cache directoryCompare Source
bootstrap.user.login_shellnow accepts a shell name such asfishinstead of a full path.[doctor.checks]can use templates, and vfox backend plugins get their own cache directory. This release also fixes PATH handling in zsh setups that deduplicate PATH, stale task cache hits, a pipx interpreter mix-up on macOS, and removes trust in the compromised eMudhra CA certificates.It also includes the changes prepared for 2026.10.16, which was tagged but never published: relative and templated
write_targetspaths, version aliases from vfox backend plugins, keyring passwords for private PyPI indexes,vfox-backend:packslip plugin sources, and a change to wherefind_upstarts (see Changed and Upgrading).Added
[bootstrap.user].login_shellaccepts a shell name. A config shared across machines no longer needs to know where each system installs the shell. mise looks up the name when it checks or applies the setting, which happens afterbootstrap.packageshas installed the shell. It searchesPATHfirst (never the mise shims directory), then common package-manager locations:/opt/homebrew/bin,/usr/local/bin,/home/linuxbrew/.linuxbrew/bin,~/.linuxbrew/bin,/usr/binand/bin. If no executable is found,mise bootstrap user applyfails without changing/etc/shellsor the account, andstatusreportsnot installed.mise bootstrap user statusshows the path it found, and--jsonoutput has a newresolvedfield. Absolute paths work as before. #14770 (@jdx)Doctor checks support templates.
run,descriptionandhintin[doctor.checks.*]are rendered with the template context of the config file that declares them, the same way hooks are. A check can now use a value from[vars]instead of hard-coding it.diris not rendered. If a template fails, only that check reportsERRORand the other checks still run. Text that already contains{{or{%in these fields is now parsed as a template. #14771 (@jdx)vfox plugins get
RUNTIME.cacheDirPath. This is a cache directory for each plugin at$MISE_CACHE_DIR/plugins/<plugin-name>. mise creates it before running any hook, and every hook of the plugin sees the same path. UnlikepluginDirPath, it is kept when the plugin is reinstalled.mise cache cleardeletes it, so plugins must handle it being missing. It isnilwhen no cache directory is available. #14776 (@jdx)settings.write_targetsaccepts relative and templated paths. Before, only absolute or~/paths worked, so dotfiles shared between machines with differentMISE_CONFIG_DIRorXDG_CONFIG_HOMEhad to hardcode the config directory. Templates are now rendered, and a relative result is joined to theconfig_rootof the settings file that declares it. For a global file that is$HOME, so the portable spelling uses the file's own directory. The resolved path must still be a global config file that mise loads. If a template fails to render, mise warns, andmise use --globalfails with "must resolve to an absolute path" instead of writing to the default file. #14742 (@jdx)vfox backend plugins can report version aliases.
BackendListVersionscan return analiasestable, so a registry's moving names resolve to real versions. Before,"mise-ghcup:ghc" = "recommended"passed the literal string to the plugin, installed intoinstalls/.../recommended, never followed the tag when it moved, and showedrecommendedinmise lsand the lockfile. Nowghc@recommendedresolves to9.10.3, installs into9.10.3/, and the lockfile records9.10.3. Aliases you define in config still win. They are cached like the version list, and an expired cache still answers offline. Older mise versions ignore thealiasesfield, so plugins can adopt it right away. #14732 (@jdx, @cprecioso)mise lockand version listing work with a PyPI index that uses a keyring. With an index such as Azure Artifacts andartifacts-keyring,mise installworked because uv read the password from its keyring provider, but mise's own requests sent no credentials and failed with401 Unauthorized. Set the newpypi.keyring_provider(disabledby default, orsubprocess; env varMISE_PYPI_KEYRING_PROVIDER) and give the registry URL a username without a password. mise then runskeyring get <url> <username>, as uv does, and sends the result as HTTP Basic credentials when it lists versions and whenmise lockreads a release'srequires-python. The password is never written to the lockfile or the version cache. Thekeyringexecutable must be onPATH. If it is missing or has no entry, mise sends the request without credentials. #14733 (@jdx)vfox-backend:works as a prefix for packslip plugin sources. A vfox backend plugin can be installed from a signed packslip archive, both from the CLI and in[plugins]. Before,mise plugins install vfox-backend:foo 'packslip:owner/repo#1.0.0'failed withpackslip plugin sources require the vfox plugin type. An explicitasdf:orpackage:prefix is still rejected, and the error now says "vfox or vfox-backend". The archive still declaresextensions.mise.plugin = "vfox". #14727 (@jdx)mise plugins install vfox-backend:my-backend 'packslip:your-org/my-backend#1.0.0'mise bootstrap packages listis now an alias forstatus, alongsidels. #14709 (@himkt)Changed
find_upinenv._.filestarts at the config root. Every other relative path in a config resolves against the config root, butfind_upstarted at the current directory. A relativefind_uppath now starts at the config root and walks up through its parents, which suits a monorepo whose root.envapplies to every package. An absolute path starts at its own directory. A global config that wants to search from wherever mise runs can usecwd. Theenv_filesetting still discovers dotenv files up from the current directory and is unchanged. See Upgrading. #14734 (@jdx, @thernstig)allow_buildsapproves only the packages it lists. With the embedded aube installer,allow_builds = ["re2"]also ran the install scripts of every package on aube's bundled trusted-dependencies list, such asdtrace-provider. For a package list, mise now turns that default list off, so only the packages you name build.allow_builds = trueand the default with no option are unchanged. This updates the embedded aube to 2.8.0. #14731 (@jdx)Fixed
exec()in[env]values, and other commands mise runs with the pre-activation environment, can now find commands in a_.pathdirectory that was already onPATHbefore activation, even if the shell deduplicatesPATH(for example zsh withtypeset -U path PATH). #14772 (@jdx)task.source_freshness_hash_contents = true, a task now re-runs when a source file is changed to content of the same size and its old mtime is restored (for example byrsync -a,cp -portouch -r). On Unix, mise now also compares the file's ctime. Cache entries written by older versions are rehashed once. #14778 (@jdx)pipx:installs no longer fail whenaqua:aws/aws-cliis in the toolset. Because macOS filesystems ignore case by default, mise's lookup forpythonmatched aws-cli's executablePythonshared library and passed it to uv as the interpreter. This lookup now requires the exact case. #14769 (@jdx)webpki-root-certs1.0.10,rustls-webpki0.103.16). Builds that use the OS trust store are fixed by OS updates instead. #14781 (@jdx)[bootstrap.compose]project no longer reports drift on every run when a service uses aservice:reference such asnetwork_mode: service:vpn. Compose hashes the reference as written but stamps the container with the hash of the resolvedcontainer:<id>, so the two never matched. mise now pins these references (network_mode,ipc,pid,volumes_from) to the running container before it asks compose for the hash. This needs an explicitfileslist in the project's config. Projects without one hash as before. #14729 (@jdx).ziparchives returned byPreInstall. Before, entries such asbin/npm -> ../lib/node_modules/npm/bin/npm-cli.jsbecame regular files holding the link target, and the tool failed withNo such file or directory. Links that resolve outside the install directory are still rejected. Thehttp:backend and tarballs were not affected. #14730 (@jdx)[daemons.<name>] task = "worker"now finds a file task such as.mise/tasks/worker.sh, asmise run workerdoes. Before, it failed withdaemon srv runs unknown task "worker"unless you wroteworker.sh. #14741 (@jdx)mise self-updateno longer replaces the wingetmise-shim.exelink with a copy. It updates the realmise-shim.exenext to the realmise.exe. Before,mise reshimkept warning that the shim was older than mise. #14737 (@jdx)[dotfiles]entry turned off with onlyenabled = falseno longer printsno recognized operation (block, source, or line), ignoring entryon every command. Other tables with no recognized operation, such as a misspelledline, still warn. #14726 (@jdx, @ponko2)Upgrading
find_upin a global config: a relativefind_upentry inenv._.fileused to search from the current directory. It now searches from the config root, which is~for a global config, so it no longer finds project files. To keep the old behavior, put{{cwd}}/in front of the path.find_upwas added in 2026.10.12.Documentation
permissionsdoes not inherit the group'smode, so it deploys nothing. Removingmodefrom an entry that used to deploy a file leaves that file orphaned, and--prunedeletes it. To deploy a file and set its permissions, use{ mode = "copy", permissions = "0600" }. #14768 (@jdx)New Contributors
Full Changelog: jdx/mise@v2026.10.15...v2026.10.17
💚 Sponsor mise
mise is built and maintained by @jdx, an open source developer at entire.io, the title sponsor of his open source work.
If mise saves you or your team time, please consider becoming an individual or company sponsor. Your support funds ongoing development and helps keep mise fast, free, and independent.
jdx/mise-action
v5.2.2: : Include conf.d config fragments in the cache keyCompare Source
The cache key now includes mise
conf.d/*.tomlconfig fragments, so changing one of them invalidates the cache.Fixed
conf.dfragment now invalidates the cache. mise can load config from single-file fragments inconf.d/directories, but the action didn't hash those files when it built the cache key. As a result, adding or changing tools in a fragment could restore an outdated cache. The cache key now also hashesconf.d/*.tomlfiles under.config/mise/,.mise/andmise/. If your repo already uses these fragments, the cache will miss once after you upgrade. (#698 by @rileymichael)New Contributors
Full Changelog: jdx/mise-action@v5.2.1...v5.2.2
DavidAnson/markdownlint-cli2 (markdownlint-cli2)
v0.24.0Compare Source
markdownlint)semgrep/semgrep (semgrep)
v1.182.0### Added
objc, alpha): tree-sitter based parsing of.mfiles with semgrep pattern syntax (metavariables, ellipsis in argument/statement/message-keyword positions, deep ellipsis), enabling search-mode and taint-mode rules on Objective-C code. Message sends, blocks, control flow, class/method definitions, and Objective-C literals are modeled; remaining constructs parse and degrade gracefully. Objective-C++ (.mm) support will follow separately. (gh-9265)### Changed
c-sharp-pro grammar update (v0.23.1):
@class,cl\u0061ss, andclass(ora\u200Cbandab) are the same name.℘(U+2118) and·(U+00B7), and still accepts formatting characters (e.g. soft hyphen) inside identifiers.(c-sharp-pro-v0.23.1)
hcl grammar update (v1.2.0):
(hcl-v1.2.0)
lua grammar update (v0.5.0):
(lua-v0.5.0)
### Fixed
requirements.txtline declared as a version range or bare name is now reported as a direct dependency even when arequirements.inmanifest is present. Such a line can only have been written by hand, sincepip-compileemits exact pins, so it is a direct declaration regardless of whether the manifest names the package. Exact pins keep using the manifest to decide between direct and transitive. (SC-4242)### Infra/Release Changes
astral-sh/uv (uv)
v0.13.5Compare Source
Released on 2026-10-21.
Following uv 0.13.4, which removed the affected eMudhra/emSign root from uv's own certificate store, this release updates the latest managed CPython builds for 3.11 and newer to python-build-standalone 20261021, including the CPython 3.15.1, 3.14.9, and 3.13.17 security patch releases. These builds include pip 26.2.2 both preinstalled in the managed interpreter and bundled with
ensurepip, which installs pip by default when you runpython -m venv. Both copies use certifi 2026.10.19, which removes the same affected root. After upgrading uv, runuv python upgradeto install the updated builds. Virtual environments pinned to an older Python patch version do not switch to the updated interpreter automatically. Upgrade pip separately in existing virtual environments.Please note upstream CPython 3.9 and 3.10 still bundle pip releases whose certificate bundles trust the affected eMudhra/emSign root. We recommend migrating off of those versions and will no longer be releasing Docker images with uv installed for EOL Python versions.
Enhancements
Python
Preview features
wheel-variants(#22535, #22536, #22687, #22688)Performance
Bug fixes
Security
rustls-webpki0.103.16 (#22777)v0.13.4Compare Source
Released on 2026-10-20.
Preview features
wheel-variants(#22512)Other changes
webpki-root-certs1.0.10 (#22760)Configuration
📅 Schedule: (in timezone Asia/Tokyo)
🚦 Automerge: Enabled.
♻ 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 was generated by Mend Renovate. View the repository job log.