Changelog for
forgejo-7.0.1-1.1.x86_64.rpm :
* Sat Apr 27 2024 Richard Rahl
- update to 7.0.1:
* LFS data corruption when running the forgejo doctor check --fix CLI command or setting [cron.gc_lfs].ENABLED=true (the default is false)
* non backward compatible change in the forgejo admin user create CLI command
* error 500 because of an incorrect evaluation of the template when visiting the LFS settings of a repository
* GET /repos/{owner}/{name} API endpoint always returns an empty string for the object_format_name field
* fuzzy search may fail with bleve
* Thu Apr 25 2024 Richard Rahl - update to 7.0.0: This is only an excerpt from the full changelog, which you can find in your RELEASE-NOTES.md or at https://codeberg.org/forgejo/forgejo/src/branch/forgejo/RELEASE-NOTES.md#7-0-0
* MySQL 8.0 or PostgreSQL 12 are the minimum supported versions. The database must be migrated before upgrading. The requirements regarding SQLite did not change.
* The per_page parameter is no longer a synonym for limit in the /repos/{owner}/{repo}/releases API endpoint.
* The date format of the created and last_update fields of the /repos/{owner}/{repo}/push_mirrors and /repos/{owner}/{repo}/push_mirrors API endpoint changed to be timestamps instead of numbers.
* Labels used by pprof endpoint have been changed
* The fogejo admin user create CLI command requires a password change by default when creating the first user
* Sat Apr 20 2024 Richard Rahl - update to 1.21.11-1:
* error 500 on tag creation when a workflow exists- update to 1.21.11-0:
* Fixed a privilege escalation through git push options that allows any user to change the visibility of any repository they can see, regardless of their level of access.
* Fixed a bug that allows user-supplied, non-sandboxed JavaScript to be run from the same domain as the forge, via /{owner}/{repo}/render/branch/{branch}/{filename} URLs.
* Close file in upload function
* Prevent registering runners for deleted repositories. Prevents 500 Internal Server Error in admin interface.
* More reliable pagination support when migrating from gitbucket
* Fix automerge when used with actions- fix apparmor profile
* Fri Apr 05 2024 Richard Rahl - update to 1.21.10-0:
* CVE-2023-45288 which permits an attacker to cause an HTTP/2 endpoint to read arbitrary amounts of header data
* Fix to not remove repository avatars when the doctor runs with --fix on the repository archives.
* Detect protected branch on branch rename.
* Don\'t delete inactive emails explicitly.
* Fix user interface when a review is deleted without refreshing.
* Fix paths when finding files via the web interface that were not escaped.
* Respect DEFAULT_ORG_MEMBER_VISIBLE setting when adding creator to org.
* Fix duplicate migrated milestones.
* Fix inline math blocks can\'t be preceeded/followed by alphanumerical characters.
* Thu Mar 28 2024 Richard Rahl - increase golang dep to 1.22, to imitate the CI/CD of forgejo- revise how the apparmor package gets build + add selinux
* Sat Mar 23 2024 Richard Rahl - update to 1.21.8-0:
* Fix /api/v1/{owner}/{repo}/issue_templates which was always failing with a 500 error.
* Prevent error 500 on /user/settings/security when SignedUser has a linked account from a deactivated authentication source.
* Fix error 500 when pushing release to an empty repo.
* Fix incorrect rendering csv file when file size is larger than UI.CSV.MaxFileSize.
* Fix error 500 when deleting account with incorrect password or unsupported login type.
* handle user-defined name anchors like [Link](#link) linking to Link.
* Use correct head commit for CODEOWNER.
* Fix manual merge button.
* Make meilisearch do exact search for issues.
* Fix PR creation via api between branches of same repo with head field namespaced.
* Fri Mar 08 2024 Richard Rahl - add apparmor profile leeched off of the gitea packaging- update to 1.21.7-0:
* Fix tarball/zipball download bug.
* Ensure HasIssueContentHistory takes into account comment_id.
* The google.golang.org/protobuf module was bumped to version v1.33.0 to fix a bug in the google.golang.org/protobuf/encoding/protojson package which could cause the Unmarshal function to enter an infinite loop when handling some invalid inputs
* Fri Feb 09 2024 Richard Rahl - initial packaging
