You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: CHANGELOG.md
+20-2Lines changed: 20 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -5,7 +5,25 @@ All notable changes to this project will be documented in this file.
5
5
The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.0.0/),
6
6
and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
7
7
8
-
## [2.4.1] - 2025-10-26
8
+
## [2.4.2] - 2025-09-22
9
+
10
+
This release brings some minor bug fixes and improvements.
11
+
12
+
### Added
13
+
14
+
- elAPI `whoami` that shows information about the eLab user (see [documentation](https://github.com/uhd-urz/elAPI/tree/main?tab=readme-ov-file#elapi-whoami))
15
+
- New configuration field `async_capacity` that lets you the maximum number of in-flight requests (see [documentation](https://github.com/uhd-urz/elAPI/tree/dev?tab=readme-ov-file#configuration))
16
+
- Improved `bill-teams` retry strategy that uses `async_capacity`
17
+
18
+
### Fixed
19
+
20
+
- Fix #162, #155, #19, #8
21
+
22
+
### Changes
23
+
24
+
- Replace HTTPX's back-end with `aiohttp`. This fixes #162.
25
+
26
+
## [2.4.1] - 2025-08-26
9
27
10
28
> [!NOTE]
11
29
> This release deprecates support for Python versions 3.9 and 3.10.
@@ -17,7 +35,7 @@ This is a hotfix release. See the [version 2.4.0 changelog](https://github.com/u
17
35
- Rollback [httpx-limiter](https://midnighter.github.io/httpx-limiter/) to version 0.3.0. The version 0.4.0 would break elAPI support on Pyodide (see GH #160)
18
36
19
37
20
-
## [2.4.0] - 2025-10-25
38
+
## [2.4.0] - 2025-08-25
21
39
22
40
> [!NOTE]
23
41
> This release deprecates support for Python versions 3.9 and 3.10.
Sometimes when a script has finished, you and your team would want to receive an email about its success/failure. elAPI
272
306
offers a no-code solution for this: the `mail` plugin. The `mail` plugin is not enabled by default. To enable it,
273
-
install elAPI with the optional dependency `mail`: `pip install elapi[mail]`or `uv add elapi[mail]`. [__See the wiki__](https://github.com/uhd-urz/elAPI/wiki/mail-plugin) to read more about how to configure the `mail` plugin with your
307
+
install elAPI with the optional dependency `mail`: `pip install elapi[mail]`or `uv add elapi[mail]`. [__See the wiki
308
+
__](https://github.com/uhd-urz/elAPI/wiki/mail-plugin) to read more about how to configure the `mail` plugin with your
274
309
mail server configuration and trigger conditions. In a
275
310
nutshell, the `mail` plugin will scan the logs when a script/plugin is done to look for pre-configured trigger
276
311
conditions, and if found, it will send an email. The trigger conditions can be atomic and scope-based, i.e., an email
0 commit comments