Skip to content

Commit f0d8537

Browse files
move to dedicated section
1 parent d1b0585 commit f0d8537

File tree

1 file changed

+7
-5
lines changed

1 file changed

+7
-5
lines changed

src/pages/docs/deprecations/index.md

Lines changed: 7 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -23,11 +23,6 @@ Deprecations are subject to change in detail or time frame. If you need help ass
2323

2424
## Planned Deprecations
2525

26-
### System and Space Level `/events` API Endpoint in 2025.4
27-
The `GET /events` and `GET /{spaceId}/events` API endpoints will be replaced by new versions that don't return pagination properties. Events are created constantly, minimising the value of providing individual page numbers, and calculating the total number of results can be very expensive on instances with larger data sets.
28-
29-
The `GET /events/v2` and `GET /{spaceId}/events/v2` endpoints will be available to retrieve events in JSON format. CSV exporting will be available with the `GET /events/export` and `GET /events/{spaceId}/export` endpoints.
30-
3126
### Dropping capability for Windows Server 2008 Workers and Targets in 2025.1
3227
Microsoft [dropped extended support](https://learn.microsoft.com/en-us/lifecycle/products/windows-server-2008) for the Windows Server 2008 family in January 2020. This operating system is also the last Windows OS that does not support .NET Core, one of the languages used to build Octopus Deploy. The complexity required to support this legacy platform outweighs the value to our customers.
3328

@@ -37,6 +32,13 @@ To provide ample time to act, from Octopus Server `2024.1`, workloads that run o
3732

3833
Further notes about this pending change can be found in the [2024.1 deprecation blog post](https://octopus.com/blog/2024-deprecated-features#windows-server-2008)
3934

35+
## Deprecations for 2025.1
36+
37+
### System and Space Level `/events` API Endpoint
38+
The `GET /events` and `GET /{spaceId}/events` API endpoints will be replaced by new versions that don't return pagination properties. Events are created constantly, minimising the value of providing individual page numbers, and calculating the total number of results can be very expensive on instances with larger data sets.
39+
40+
For similar functionality without pagination, use the `GET /events/v2` and `GET /{spaceId}/events/v2` endpoints. To export events in CSV format, use the `GET /events/export` or `GET /events/{spaceId}/export` endpoints.
41+
4042
## Deprecations for 2024.3
4143

4244
### Azure Resource Manager Powershell Module

0 commit comments

Comments
 (0)