mason/lua/mason-core/installer/context, branch v2.2.0

feat: add support for removal of packages from a registry (#2052)

2026-01-07T14:46:58Z

This adds support for removal of packages from any given registry. Currently mason.nvim doesn't support this at all and throws an error when trying to interact with the registry in any way while having a removed package installed locally. This ensures that removed packages are available both in the `:Mason` UI as well as the public Lua APIs. These "synthesized" packages only supports uninstallation, and metadata such as licenses, categories, homepage, etc is not available.

fix(installer): update cwd after uv_fs_rename() was successful (#2033)

2025-11-14T03:20:19Z

Also moves to fs.sync calls over fs.async to avoid unnecessary async coroutine overhead.

fix(installer): attempt to recover from known fs error while finalizing installation on some file systems (#1933)

2025-11-14T02:50:44Z

Co-authored-by: William Boman

feat(context): add ctx:await()

2025-02-19T11:15:49Z

refactor: turn StdioSink into a proper class

2025-02-19T11:15:49Z

feat(context): add ctx:fetch()

2025-02-19T11:15:49Z

refactor!: change Package API

2025-02-19T11:15:48Z

This changes the following public APIs: **(_breaking_) Events on the `Package` class** The `uninstall:success` event on the `Package` class now receives an `InstallReceipt` as argument, instead of an `InstallHandle`. This receipt is an in-memory representation of what was uninstalled. There's also a new `uninstall:failed` event for situations where uninstallation for some reason fails. Note: this also applies to the registry events (i.e. `package:uninstall:success` and `package:uninstall:failed`). --- **(_breaking_) `Package:uninstall()` is now asynchronous and receives two new arguments, similarly to `Package:install()`** While package uninstallations remain synchronous under the hood, the public API has been changed from synchronous -> asynchronous. Users of this method are recommended to provide a callback in situations where code needs to execute after uninstallation fully completes. --- **(_breaking_) `Package:get_install_path()` has been removed. --- **`Package:install()` now takes an optional callback** This callback allows consumers to be informed whether installation was successful or not without having to go through a different, low-level, API. See below for a comparison between the old and new APIs: ```lua -- before local handle = pkg:install() handle:once("closed", function () -- ... end) -- after pkg:install({}, function (success, result) -- ... end) ```

refactor: standardize constructors and improve inheritance construction

2025-02-19T08:23:19Z

refactor(installer): move initializations to InstallContext constructor

2025-02-19T08:23:19Z

refactor!: refactor installer internals and add new Package class methods (#1523)

2025-02-19T08:22:40Z

This contains the following changes: 1) `Package:install()` now accepts a second, optional, callback argument which is called when installation finishes (successfully or not). 2) Adds a `Package:is_installing()` method. This contains the following breaking changes: 1) `Package:install()` will now error when called while an installation is already ongoing. Use the new `Package:is_installing()` method to check whether an installation is already running. This also refactors large portions of the tests by removing test globals, removing async_test, and adding the `mason-test` Lua module instead. Test helpers via globals are problematic to work with due to not being detected through tools like the Lua language server without additional configuration. This has been replaced with a Lua module `mason-test`. `async_test` has also been removed in favour of explicitly making use of the `mason-core.async` API. These changes stands for a significant portion of the diff.