apache-airflow-providers-edge3
Provider package apache-airflow-providers-edge3 for Apache Airflow
Activity
- Latest release
- 3d ago
- Total releases
- 68
- Cadence
- ~5 days
- Last 12 months
- 50
Details
- License
- Apache-2.0
- First release
- Apr 16, 2025
| Version | Released | |
|---|---|---|
4.3.2rc1
pre
|
4.3.2rc1
pre
Dependencies (6)
|
|
4.3.1
patch
|
4.3.1
patch
Dependencies (6)
|
|
4.3.1rc1
pre
|
4.3.1rc1
pre
Dependencies (6)
|
|
4.3.0
minor
|
4.3.0
minor
Dependencies (6)
|
|
4.3.0rc2
pre
|
4.3.0rc2
pre
Dependencies (6)
|
|
4.3.0rc1
pre
|
4.3.0rc1
pre
Dependencies (6)
|
|
4.2.0
minor
|
4.2.0
minor
Dependencies (6)
|
|
4.2.0rc1
pre
|
4.2.0rc1
pre
Dependencies (6)
|
|
4.1.0
minor
|
4.1.0
minor
Dependencies (6)
|
|
4.1.0rc1
pre
|
4.1.0rc1
pre
Dependencies (6)
|
|
4.0.0
major
|
4.0.0
major
Dependencies (6)
|
|
4.0.0rc1
pre
|
4.0.0rc1
pre
Dependencies (6)
|
|
3.8.0
minor
|
3.8.0
minor
Dependencies (6)
|
|
3.8.0rc2
pre
|
3.8.0rc2
pre
Dependencies (6)
|
|
3.8.0rc1
pre
|
3.8.0rc1
pre
Dependencies (6)
|
|
3.7.0
minor
|
3.7.0
minor
Dependencies (6)
|
|
3.7.0rc1
pre
|
3.7.0rc1
pre
Dependencies (6)
|
|
3.6.0
minor
|
3.6.0
minor
Dependencies (6)
|
|
3.6.0rc1
pre
|
3.6.0rc1
pre
Dependencies (6)
|
|
3.5.0
minor
|
3.5.0
minor
Dependencies (6)
|
|
3.5.0rc1
pre
|
3.5.0rc1
pre
Dependencies (6)
|
|
3.4.0
minor
|
3.4.0
minor
Dependencies (6)
|
|
3.4.0rc1
pre
|
3.4.0rc1
pre
Dependencies (6)
|
|
3.3.0
minor
|
3.3.0
minor
Dependencies (6)
|
|
3.3.0rc1
pre
|
3.3.0rc1
pre
Dependencies (6)
|
|
3.2.0
minor
|
3.2.0
minor
Dependencies (6)
|
|
3.2.0rc1
pre
|
3.2.0rc1
pre
Dependencies (6)
|
|
3.1.0
minor
|
3.1.0
minor
Dependencies (6)
|
|
3.1.0rc2
pre
|
3.1.0rc2
pre
Dependencies (6)
|
|
3.1.0rc1
pre
|
3.1.0rc1
pre
Dependencies (6)
|
|
3.0.2
patch
|
3.0.2
patch
Dependencies (6)
|
|
3.0.2rc1
pre
|
3.0.2rc1
pre
Dependencies (6)
|
|
3.0.1
patch
|
3.0.1
patch
Dependencies (6)
|
|
3.0.1rc1
pre
|
3.0.1rc1
pre
Dependencies (6)
|
|
3.0.0
major
|
3.0.0
major
Dependencies (6)
|
|
3.0.0rc1
pre
|
3.0.0rc1
pre
Dependencies (6)
|
|
2.0.1
patch
|
2.0.1
patch
Dependencies (4)
|
|
2.0.1rc1
pre
|
2.0.1rc1
pre
Dependencies (4)
|
|
2.0.0
major
|
2.0.0
major
Dependencies (4)
|
|
2.0.0rc1
pre
1 CVE
CVE-2025-67895
PYSEC-2026-276
GHSA-66h8-3g48-6hx8
PYSEC-2025-87
Jun 29, 2026
Apache Airflow Providers Edge3 exposes internal API allowing RCE in web server context
9.8
/ 10
Critical
Network
Low
None
None
Unchanged
High
High
High
Edge3 Worker RPC RCE on Airflow 2. This issue affects Apache Airflow Providers Edge3: before 2.0.0 - and only if projects installed and configured it on Airflow 2. The Edge3 provider support in Airflow 2 has been always development-only and not officially released, however if projects installed and configured Edge3 provider in Airflow 2, it implicitly enabled non-public (normally) API which was used to test Edge Provider in Airflow 2 during the development. This API allowed Dag author to perform Remote Code Execution in the webserver context, which Dag Author was not supposed to be able to do. If projects installed and configured Edge3 provider for Airflow 2, they should uninstall it and migrate to Airflow 3. The new Edge3 provider versions (>=2.0.0) has a minimum version of Airflow set to 3 and the RCE-prone Airflow 2 code is removed, so it should no longer be possible to use the Edge3 provider 2.0.0+ on Airflow 2. If projects used Edge Provider in Airflow 3, you they are not affected. Affected versions
1.0.0
1.0.0rc1
1.0.0rc2
1.1.0
1.1.0rc1
1.1.1
1.1.1rc1
1.1.2
1.1.2rc1
1.1.2rc2
1.1.3
1.1.3rc1
+ 17 more Show less
1.2.0
1.2.0rc1
1.3.0
1.3.0rc1
1.3.1
1.3.1rc1
1.4.0
1.4.0rc1
1.4.1
1.4.1rc1
1.4.1rc2
1.5.0
1.5.0rc1
1.6.0
1.6.0rc1
1.6.0rc2
2.0.0rc1
Fixed in
2.0.0
References
Updated Jul 01, 2026 · Source: OSV.dev |
2.0.0rc1
pre
Dependencies (4)
|
|
1.6.0
minor
1 CVE
CVE-2025-67895
PYSEC-2026-276
GHSA-66h8-3g48-6hx8
PYSEC-2025-87
Jun 29, 2026
Apache Airflow Providers Edge3 exposes internal API allowing RCE in web server context
9.8
/ 10
Critical
Network
Low
None
None
Unchanged
High
High
High
Edge3 Worker RPC RCE on Airflow 2. This issue affects Apache Airflow Providers Edge3: before 2.0.0 - and only if projects installed and configured it on Airflow 2. The Edge3 provider support in Airflow 2 has been always development-only and not officially released, however if projects installed and configured Edge3 provider in Airflow 2, it implicitly enabled non-public (normally) API which was used to test Edge Provider in Airflow 2 during the development. This API allowed Dag author to perform Remote Code Execution in the webserver context, which Dag Author was not supposed to be able to do. If projects installed and configured Edge3 provider for Airflow 2, they should uninstall it and migrate to Airflow 3. The new Edge3 provider versions (>=2.0.0) has a minimum version of Airflow set to 3 and the RCE-prone Airflow 2 code is removed, so it should no longer be possible to use the Edge3 provider 2.0.0+ on Airflow 2. If projects used Edge Provider in Airflow 3, you they are not affected. Affected versions
1.0.0
1.0.0rc1
1.0.0rc2
1.1.0
1.1.0rc1
1.1.1
1.1.1rc1
1.1.2
1.1.2rc1
1.1.2rc2
1.1.3
1.1.3rc1
+ 17 more Show less
1.2.0
1.2.0rc1
1.3.0
1.3.0rc1
1.3.1
1.3.1rc1
1.4.0
1.4.0rc1
1.4.1
1.4.1rc1
1.4.1rc2
1.5.0
1.5.0rc1
1.6.0
1.6.0rc1
1.6.0rc2
2.0.0rc1
Fixed in
2.0.0
References
Updated Jul 01, 2026 · Source: OSV.dev |
1.6.0
minor
Dependencies (4)
|
|
1.6.0rc2
pre
1 CVE
CVE-2025-67895
PYSEC-2026-276
GHSA-66h8-3g48-6hx8
PYSEC-2025-87
Jun 29, 2026
Apache Airflow Providers Edge3 exposes internal API allowing RCE in web server context
9.8
/ 10
Critical
Network
Low
None
None
Unchanged
High
High
High
Edge3 Worker RPC RCE on Airflow 2. This issue affects Apache Airflow Providers Edge3: before 2.0.0 - and only if projects installed and configured it on Airflow 2. The Edge3 provider support in Airflow 2 has been always development-only and not officially released, however if projects installed and configured Edge3 provider in Airflow 2, it implicitly enabled non-public (normally) API which was used to test Edge Provider in Airflow 2 during the development. This API allowed Dag author to perform Remote Code Execution in the webserver context, which Dag Author was not supposed to be able to do. If projects installed and configured Edge3 provider for Airflow 2, they should uninstall it and migrate to Airflow 3. The new Edge3 provider versions (>=2.0.0) has a minimum version of Airflow set to 3 and the RCE-prone Airflow 2 code is removed, so it should no longer be possible to use the Edge3 provider 2.0.0+ on Airflow 2. If projects used Edge Provider in Airflow 3, you they are not affected. Affected versions
1.0.0
1.0.0rc1
1.0.0rc2
1.1.0
1.1.0rc1
1.1.1
1.1.1rc1
1.1.2
1.1.2rc1
1.1.2rc2
1.1.3
1.1.3rc1
+ 17 more Show less
1.2.0
1.2.0rc1
1.3.0
1.3.0rc1
1.3.1
1.3.1rc1
1.4.0
1.4.0rc1
1.4.1
1.4.1rc1
1.4.1rc2
1.5.0
1.5.0rc1
1.6.0
1.6.0rc1
1.6.0rc2
2.0.0rc1
Fixed in
2.0.0
References
Updated Jul 01, 2026 · Source: OSV.dev |
1.6.0rc2
pre
Dependencies (4)
|
|
1.6.0rc1
pre
1 CVE
CVE-2025-67895
PYSEC-2026-276
GHSA-66h8-3g48-6hx8
PYSEC-2025-87
Jun 29, 2026
Apache Airflow Providers Edge3 exposes internal API allowing RCE in web server context
9.8
/ 10
Critical
Network
Low
None
None
Unchanged
High
High
High
Edge3 Worker RPC RCE on Airflow 2. This issue affects Apache Airflow Providers Edge3: before 2.0.0 - and only if projects installed and configured it on Airflow 2. The Edge3 provider support in Airflow 2 has been always development-only and not officially released, however if projects installed and configured Edge3 provider in Airflow 2, it implicitly enabled non-public (normally) API which was used to test Edge Provider in Airflow 2 during the development. This API allowed Dag author to perform Remote Code Execution in the webserver context, which Dag Author was not supposed to be able to do. If projects installed and configured Edge3 provider for Airflow 2, they should uninstall it and migrate to Airflow 3. The new Edge3 provider versions (>=2.0.0) has a minimum version of Airflow set to 3 and the RCE-prone Airflow 2 code is removed, so it should no longer be possible to use the Edge3 provider 2.0.0+ on Airflow 2. If projects used Edge Provider in Airflow 3, you they are not affected. Affected versions
1.0.0
1.0.0rc1
1.0.0rc2
1.1.0
1.1.0rc1
1.1.1
1.1.1rc1
1.1.2
1.1.2rc1
1.1.2rc2
1.1.3
1.1.3rc1
+ 17 more Show less
1.2.0
1.2.0rc1
1.3.0
1.3.0rc1
1.3.1
1.3.1rc1
1.4.0
1.4.0rc1
1.4.1
1.4.1rc1
1.4.1rc2
1.5.0
1.5.0rc1
1.6.0
1.6.0rc1
1.6.0rc2
2.0.0rc1
Fixed in
2.0.0
References
Updated Jul 01, 2026 · Source: OSV.dev |
1.6.0rc1
pre
Dependencies (4)
|
|
1.5.0
minor
1 CVE
CVE-2025-67895
PYSEC-2026-276
GHSA-66h8-3g48-6hx8
PYSEC-2025-87
Jun 29, 2026
Apache Airflow Providers Edge3 exposes internal API allowing RCE in web server context
9.8
/ 10
Critical
Network
Low
None
None
Unchanged
High
High
High
Edge3 Worker RPC RCE on Airflow 2. This issue affects Apache Airflow Providers Edge3: before 2.0.0 - and only if projects installed and configured it on Airflow 2. The Edge3 provider support in Airflow 2 has been always development-only and not officially released, however if projects installed and configured Edge3 provider in Airflow 2, it implicitly enabled non-public (normally) API which was used to test Edge Provider in Airflow 2 during the development. This API allowed Dag author to perform Remote Code Execution in the webserver context, which Dag Author was not supposed to be able to do. If projects installed and configured Edge3 provider for Airflow 2, they should uninstall it and migrate to Airflow 3. The new Edge3 provider versions (>=2.0.0) has a minimum version of Airflow set to 3 and the RCE-prone Airflow 2 code is removed, so it should no longer be possible to use the Edge3 provider 2.0.0+ on Airflow 2. If projects used Edge Provider in Airflow 3, you they are not affected. Affected versions
1.0.0
1.0.0rc1
1.0.0rc2
1.1.0
1.1.0rc1
1.1.1
1.1.1rc1
1.1.2
1.1.2rc1
1.1.2rc2
1.1.3
1.1.3rc1
+ 17 more Show less
1.2.0
1.2.0rc1
1.3.0
1.3.0rc1
1.3.1
1.3.1rc1
1.4.0
1.4.0rc1
1.4.1
1.4.1rc1
1.4.1rc2
1.5.0
1.5.0rc1
1.6.0
1.6.0rc1
1.6.0rc2
2.0.0rc1
Fixed in
2.0.0
References
Updated Jul 01, 2026 · Source: OSV.dev |
1.5.0
minor
Dependencies (4)
|
|
1.5.0rc1
pre
1 CVE
CVE-2025-67895
PYSEC-2026-276
GHSA-66h8-3g48-6hx8
PYSEC-2025-87
Jun 29, 2026
Apache Airflow Providers Edge3 exposes internal API allowing RCE in web server context
9.8
/ 10
Critical
Network
Low
None
None
Unchanged
High
High
High
Edge3 Worker RPC RCE on Airflow 2. This issue affects Apache Airflow Providers Edge3: before 2.0.0 - and only if projects installed and configured it on Airflow 2. The Edge3 provider support in Airflow 2 has been always development-only and not officially released, however if projects installed and configured Edge3 provider in Airflow 2, it implicitly enabled non-public (normally) API which was used to test Edge Provider in Airflow 2 during the development. This API allowed Dag author to perform Remote Code Execution in the webserver context, which Dag Author was not supposed to be able to do. If projects installed and configured Edge3 provider for Airflow 2, they should uninstall it and migrate to Airflow 3. The new Edge3 provider versions (>=2.0.0) has a minimum version of Airflow set to 3 and the RCE-prone Airflow 2 code is removed, so it should no longer be possible to use the Edge3 provider 2.0.0+ on Airflow 2. If projects used Edge Provider in Airflow 3, you they are not affected. Affected versions
1.0.0
1.0.0rc1
1.0.0rc2
1.1.0
1.1.0rc1
1.1.1
1.1.1rc1
1.1.2
1.1.2rc1
1.1.2rc2
1.1.3
1.1.3rc1
+ 17 more Show less
1.2.0
1.2.0rc1
1.3.0
1.3.0rc1
1.3.1
1.3.1rc1
1.4.0
1.4.0rc1
1.4.1
1.4.1rc1
1.4.1rc2
1.5.0
1.5.0rc1
1.6.0
1.6.0rc1
1.6.0rc2
2.0.0rc1
Fixed in
2.0.0
References
Updated Jul 01, 2026 · Source: OSV.dev |
1.5.0rc1
pre
Dependencies (4)
|
|
1.4.1
patch
1 CVE
CVE-2025-67895
PYSEC-2026-276
GHSA-66h8-3g48-6hx8
PYSEC-2025-87
Jun 29, 2026
Apache Airflow Providers Edge3 exposes internal API allowing RCE in web server context
9.8
/ 10
Critical
Network
Low
None
None
Unchanged
High
High
High
Edge3 Worker RPC RCE on Airflow 2. This issue affects Apache Airflow Providers Edge3: before 2.0.0 - and only if projects installed and configured it on Airflow 2. The Edge3 provider support in Airflow 2 has been always development-only and not officially released, however if projects installed and configured Edge3 provider in Airflow 2, it implicitly enabled non-public (normally) API which was used to test Edge Provider in Airflow 2 during the development. This API allowed Dag author to perform Remote Code Execution in the webserver context, which Dag Author was not supposed to be able to do. If projects installed and configured Edge3 provider for Airflow 2, they should uninstall it and migrate to Airflow 3. The new Edge3 provider versions (>=2.0.0) has a minimum version of Airflow set to 3 and the RCE-prone Airflow 2 code is removed, so it should no longer be possible to use the Edge3 provider 2.0.0+ on Airflow 2. If projects used Edge Provider in Airflow 3, you they are not affected. Affected versions
1.0.0
1.0.0rc1
1.0.0rc2
1.1.0
1.1.0rc1
1.1.1
1.1.1rc1
1.1.2
1.1.2rc1
1.1.2rc2
1.1.3
1.1.3rc1
+ 17 more Show less
1.2.0
1.2.0rc1
1.3.0
1.3.0rc1
1.3.1
1.3.1rc1
1.4.0
1.4.0rc1
1.4.1
1.4.1rc1
1.4.1rc2
1.5.0
1.5.0rc1
1.6.0
1.6.0rc1
1.6.0rc2
2.0.0rc1
Fixed in
2.0.0
References
Updated Jul 01, 2026 · Source: OSV.dev |
1.4.1
patch
Dependencies (4)
|
|
1.4.1rc2
pre
1 CVE
CVE-2025-67895
PYSEC-2026-276
GHSA-66h8-3g48-6hx8
PYSEC-2025-87
Jun 29, 2026
Apache Airflow Providers Edge3 exposes internal API allowing RCE in web server context
9.8
/ 10
Critical
Network
Low
None
None
Unchanged
High
High
High
Edge3 Worker RPC RCE on Airflow 2. This issue affects Apache Airflow Providers Edge3: before 2.0.0 - and only if projects installed and configured it on Airflow 2. The Edge3 provider support in Airflow 2 has been always development-only and not officially released, however if projects installed and configured Edge3 provider in Airflow 2, it implicitly enabled non-public (normally) API which was used to test Edge Provider in Airflow 2 during the development. This API allowed Dag author to perform Remote Code Execution in the webserver context, which Dag Author was not supposed to be able to do. If projects installed and configured Edge3 provider for Airflow 2, they should uninstall it and migrate to Airflow 3. The new Edge3 provider versions (>=2.0.0) has a minimum version of Airflow set to 3 and the RCE-prone Airflow 2 code is removed, so it should no longer be possible to use the Edge3 provider 2.0.0+ on Airflow 2. If projects used Edge Provider in Airflow 3, you they are not affected. Affected versions
1.0.0
1.0.0rc1
1.0.0rc2
1.1.0
1.1.0rc1
1.1.1
1.1.1rc1
1.1.2
1.1.2rc1
1.1.2rc2
1.1.3
1.1.3rc1
+ 17 more Show less
1.2.0
1.2.0rc1
1.3.0
1.3.0rc1
1.3.1
1.3.1rc1
1.4.0
1.4.0rc1
1.4.1
1.4.1rc1
1.4.1rc2
1.5.0
1.5.0rc1
1.6.0
1.6.0rc1
1.6.0rc2
2.0.0rc1
Fixed in
2.0.0
References
Updated Jul 01, 2026 · Source: OSV.dev |
1.4.1rc2
pre
Dependencies (4)
|
|
1.4.1rc1
pre
1 CVE
CVE-2025-67895
PYSEC-2026-276
GHSA-66h8-3g48-6hx8
PYSEC-2025-87
Jun 29, 2026
Apache Airflow Providers Edge3 exposes internal API allowing RCE in web server context
9.8
/ 10
Critical
Network
Low
None
None
Unchanged
High
High
High
Edge3 Worker RPC RCE on Airflow 2. This issue affects Apache Airflow Providers Edge3: before 2.0.0 - and only if projects installed and configured it on Airflow 2. The Edge3 provider support in Airflow 2 has been always development-only and not officially released, however if projects installed and configured Edge3 provider in Airflow 2, it implicitly enabled non-public (normally) API which was used to test Edge Provider in Airflow 2 during the development. This API allowed Dag author to perform Remote Code Execution in the webserver context, which Dag Author was not supposed to be able to do. If projects installed and configured Edge3 provider for Airflow 2, they should uninstall it and migrate to Airflow 3. The new Edge3 provider versions (>=2.0.0) has a minimum version of Airflow set to 3 and the RCE-prone Airflow 2 code is removed, so it should no longer be possible to use the Edge3 provider 2.0.0+ on Airflow 2. If projects used Edge Provider in Airflow 3, you they are not affected. Affected versions
1.0.0
1.0.0rc1
1.0.0rc2
1.1.0
1.1.0rc1
1.1.1
1.1.1rc1
1.1.2
1.1.2rc1
1.1.2rc2
1.1.3
1.1.3rc1
+ 17 more Show less
1.2.0
1.2.0rc1
1.3.0
1.3.0rc1
1.3.1
1.3.1rc1
1.4.0
1.4.0rc1
1.4.1
1.4.1rc1
1.4.1rc2
1.5.0
1.5.0rc1
1.6.0
1.6.0rc1
1.6.0rc2
2.0.0rc1
Fixed in
2.0.0
References
Updated Jul 01, 2026 · Source: OSV.dev |
1.4.1rc1
pre
Dependencies (4)
|
|
1.4.0
minor
1 CVE
CVE-2025-67895
PYSEC-2026-276
GHSA-66h8-3g48-6hx8
PYSEC-2025-87
Jun 29, 2026
Apache Airflow Providers Edge3 exposes internal API allowing RCE in web server context
9.8
/ 10
Critical
Network
Low
None
None
Unchanged
High
High
High
Edge3 Worker RPC RCE on Airflow 2. This issue affects Apache Airflow Providers Edge3: before 2.0.0 - and only if projects installed and configured it on Airflow 2. The Edge3 provider support in Airflow 2 has been always development-only and not officially released, however if projects installed and configured Edge3 provider in Airflow 2, it implicitly enabled non-public (normally) API which was used to test Edge Provider in Airflow 2 during the development. This API allowed Dag author to perform Remote Code Execution in the webserver context, which Dag Author was not supposed to be able to do. If projects installed and configured Edge3 provider for Airflow 2, they should uninstall it and migrate to Airflow 3. The new Edge3 provider versions (>=2.0.0) has a minimum version of Airflow set to 3 and the RCE-prone Airflow 2 code is removed, so it should no longer be possible to use the Edge3 provider 2.0.0+ on Airflow 2. If projects used Edge Provider in Airflow 3, you they are not affected. Affected versions
1.0.0
1.0.0rc1
1.0.0rc2
1.1.0
1.1.0rc1
1.1.1
1.1.1rc1
1.1.2
1.1.2rc1
1.1.2rc2
1.1.3
1.1.3rc1
+ 17 more Show less
1.2.0
1.2.0rc1
1.3.0
1.3.0rc1
1.3.1
1.3.1rc1
1.4.0
1.4.0rc1
1.4.1
1.4.1rc1
1.4.1rc2
1.5.0
1.5.0rc1
1.6.0
1.6.0rc1
1.6.0rc2
2.0.0rc1
Fixed in
2.0.0
References
Updated Jul 01, 2026 · Source: OSV.dev |
1.4.0
minor
Dependencies (4)
|
|
1.4.0rc1
pre
1 CVE
CVE-2025-67895
PYSEC-2026-276
GHSA-66h8-3g48-6hx8
PYSEC-2025-87
Jun 29, 2026
Apache Airflow Providers Edge3 exposes internal API allowing RCE in web server context
9.8
/ 10
Critical
Network
Low
None
None
Unchanged
High
High
High
Edge3 Worker RPC RCE on Airflow 2. This issue affects Apache Airflow Providers Edge3: before 2.0.0 - and only if projects installed and configured it on Airflow 2. The Edge3 provider support in Airflow 2 has been always development-only and not officially released, however if projects installed and configured Edge3 provider in Airflow 2, it implicitly enabled non-public (normally) API which was used to test Edge Provider in Airflow 2 during the development. This API allowed Dag author to perform Remote Code Execution in the webserver context, which Dag Author was not supposed to be able to do. If projects installed and configured Edge3 provider for Airflow 2, they should uninstall it and migrate to Airflow 3. The new Edge3 provider versions (>=2.0.0) has a minimum version of Airflow set to 3 and the RCE-prone Airflow 2 code is removed, so it should no longer be possible to use the Edge3 provider 2.0.0+ on Airflow 2. If projects used Edge Provider in Airflow 3, you they are not affected. Affected versions
1.0.0
1.0.0rc1
1.0.0rc2
1.1.0
1.1.0rc1
1.1.1
1.1.1rc1
1.1.2
1.1.2rc1
1.1.2rc2
1.1.3
1.1.3rc1
+ 17 more Show less
1.2.0
1.2.0rc1
1.3.0
1.3.0rc1
1.3.1
1.3.1rc1
1.4.0
1.4.0rc1
1.4.1
1.4.1rc1
1.4.1rc2
1.5.0
1.5.0rc1
1.6.0
1.6.0rc1
1.6.0rc2
2.0.0rc1
Fixed in
2.0.0
References
Updated Jul 01, 2026 · Source: OSV.dev |
1.4.0rc1
pre
Dependencies (4)
|