Also, if we use app.ini (I believe we do), then we should also reflect this permission change in our recipe.
https://blog.gitea.io/2021/08/gitea-1.15.0-is-released/
[Requires a manual migration for Drone](https://blog.gitea.io/2021/08/gitea-1.15.0-is-released/#-asymmetric-jwt-signing-key-16010httpsgithubcomgo-giteagiteapull16010
), because they improved OAuth key security. We may also have to re-generate its client secret.
Also, if we use `app.ini` (I believe we do), then we should also reflect [this permission change](https://blog.gitea.io/2021/08/gitea-1.15.0-is-released/#-more-restrictive-appini-permissions-16266httpsgithubcomgo-giteagiteapull16266) in our recipe.
Some nice new features in there again. This one would be useful for migrating more of our repos off of GitHub for core work, but have them still be there for new contributors to find and interact with:
Adds the ability to push-mirror a repository to a remote destination.
Some nice new features in there again. This one would be useful for migrating more of our repos off of GitHub for core work, but have them still be there for new contributors to find and interact with:
> Adds the ability to push-mirror a repository to a remote destination.
https://blog.gitea.io/2021/08/gitea-1.15.0-is-released/#add-push-to-remote-mirror-repository-15157httpsgithubcomgo-giteagiteapull15157
raucao
self-assigned this 2021-11-25 00:39:54 +00:00
Gitea is now upgraded to 1.15.6. But I had to remove the expired Let's Encrypt root certificate from /opt/chef/embedded/ssl/cert.pem on centaurus, as explained here:
Gitea is now upgraded to `1.15.6`. But I had to remove the expired Let's Encrypt root certificate from `/opt/chef/embedded/ssl/cert.pem` on `centaurus`, as explained here:
https://github.com/chef/chef/issues/12126#issuecomment-932067530
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
https://blog.gitea.io/2021/08/gitea-1.15.0-is-released/
Requires a manual migration for Drone, because they improved OAuth key security. We may also have to re-generate its client secret.
Also, if we use
app.ini(I believe we do), then we should also reflect this permission change in our recipe.Some nice new features in there again. This one would be useful for migrating more of our repos off of GitHub for core work, but have them still be there for new contributors to find and interact with:
https://blog.gitea.io/2021/08/gitea-1.15.0-is-released/#add-push-to-remote-mirror-repository-15157httpsgithubcomgo-giteagiteapull15157
Gitea is now upgraded to
1.15.6. But I had to remove the expired Let's Encrypt root certificate from/opt/chef/embedded/ssl/cert.pemoncentaurus, as explained here:https://github.com/chef/chef/issues/12126#issuecomment-932067530