Skip to content

release notes for 3.0.0 rolling release #338

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
ScharfViktor merged 2 commits into from
Jun 11, 2025
Merged

release notes for 3.0.0 rolling release #338

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
d6057d9
add release notes
ScharfViktor Jun 11, 2025
081059d
add link to github release for more information
Svanvith Jun 11, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion docs/admin/resources/common-issues.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,5 +1,5 @@
---
sidebar_position: 3
sidebar_position: 4
id: common-issues
title: Common Issues & Help
---
Expand Down
2 changes: 1 addition & 1 deletion docs/admin/resources/demo-user.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,5 +1,5 @@
---
sidebar_position: 4
sidebar_position: 5
id: demo-user
title: Demo User
---
Expand Down
2 changes: 1 addition & 1 deletion docs/admin/resources/lifecycle.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -39,7 +39,7 @@ With LTS, businesses can continue using an older production release without need
| - | 2025 August 11 | - |
| - | 2025 July 21 | - |
| - | 2025 June 30 | - |
| - | 2025 June 10 | - |
| v3.0.0 | 2025 June 10 | [Details · Download](https://github.com/opencloud-eu/opencloud/releases/tag/v3.0.0) |
| v2.3.0 | 2025 May 19 | [Details · Download](https://github.com/opencloud-eu/opencloud/releases/tag/v2.3.0) |
| v2.2.0 | 2025 April 28 | [Details · Download](https://github.com/opencloud-eu/opencloud/releases/tag/v2.2.0) |
| v2.1.0 | 2025 April 07 | [Details · Download](https://github.com/opencloud-eu/opencloud/releases/tag/v2.1.0) |
Expand Down
31 changes: 31 additions & 0 deletions docs/admin/resources/release-notes.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,31 @@
---
sidebar_position: 3
id: release-notes
title: "Release Notes"
draft: false
---

# 📦 Release Notes: Migration from v2.x.x to v3.0.0

- Version: 3.0.0
- Type: Major Release (Breaking Changes)
- [Details · Download](https://github.com/opencloud-eu/opencloud/releases/tag/v3.0.0)

## Key Changes
### Performance Optimization (Breaking Change)
#### Old Behavior:

```
GET /drives/{drive-id}/root/permissions
```

👉 Automatically returned full permission details with all nested properties.


#### New Behavior:

```
GET /drives/{drive-id}/root/permissions?$select=@libre.graph.permissions.actions.allowedValues
```

👉 Now requires explicit selection of needed fields.
Comment on lines +10 to +31
Copy link
Copy Markdown
Member

@rhafer rhafer Jun 11, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Key Changes

The breaking change only affects software accessing OpenCloud via the GraphAPI. If you're accessing OpenCloud only via the clients provided by OpenCloud no migration is needed.

If you're using any other software that utilizes the GraphAPI, that software might need to be adjust to follow the new behavior of the GraphAPI. The following endpoints of the GraphAPI where changed in a way that is not backwards compatible with the previous releases:

GET /v1.0/me/drives/
GET /v1.0/drives/
GET /v1beta1/drives
GET /v1beta1/me/drives/

With the new release these endpoints do no longer automatically expand the all permissions the permissions on the drives' root items. If needed, the premission can be explicitly requested via the appropriate $expand query option.