Hi everyone,
I guess this section is the best way to tell someone of the nextcloud team that according to the nextcloud changelog https://nextcloud.com/changelog/ on March 21 2022 those nextcloud changelogs have been published:
23.04
23.03
22.2.7
22.2.6
Maybe someone reused the timestamp of the previous changelog?
Best regards
tflidd
April 26, 2022, 8:14am
2
Thanks, the problem was already reported to the bugtracker:
opened 10:04AM - 22 Apr 22 UTC
bug
0. Needs triage
### ⚠️ This issue respects the following points: ⚠️
- [X] This is a **bug**, no… t a question or a configuration/webserver/proxy issue.
- [X] This issue is **not** already reported on Github _(I've searched it)_.
- [X] Nextcloud Server **is** up to date. See [Maintenance and Release Schedule](https://github.com/nextcloud/server/wiki/Maintenance-and-Release-Schedule) for supported versions.
- [X] I agree to follow Nextcloud's [Code of Conduct](https://nextcloud.com/contribute/code-of-conduct/).
### Bug description
https://nextcloud.com/Changelog/ says 22.2.7 and 23.0.4 were released 21 March (same as previous releases) instead of April.
### Steps to reproduce
Look at https://nextcloud.com/Changelog/
Reading "March 21"
### Expected behavior
Reading "April 21".
### Installation method
_No response_
### Operating system
_No response_
### PHP engine version
_No response_
### Web server
_No response_
### Database engine version
_No response_
### Is this bug present after an update or on a fresh install?
_No response_
### Are you using the Nextcloud Server Encryption module?
_No response_
### What user-backends are you using?
- [ ] Default user-backend _(database)_
- [ ] LDAP/ Active Directory
- [ ] SSO - SAML
- [ ] Other
### Configuration report
_No response_
### List of activated Apps
```shell
None
```
### Nextcloud Signing status
_No response_
### Nextcloud Logs
_No response_
### Additional info
_No response_
1 Like