chore(deps): update codeberg.org/forgejo/forgejo docker tag to v15 #27
Reference in New Issue
Block a user
No description provided.
Delete Branch "renovate/codeberg.org-forgejo-forgejo-15.x"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
This PR contains the following updates:
14.0.4-rootless->15.0.0-rootlessRelease Notes
forgejo/forgejo (codeberg.org/forgejo/forgejo)
v15.0.0Compare Source
See https://codeberg.org/forgejo/forgejo/src/branch/forgejo/release-notes-published/15.0.0.md
Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR has been generated by Renovate Bot.
7a1337e8b1tocb6de09976cb6de09976toec7c0a706eec7c0a706eto209cd83075209cd83075tobcc1b43c42@p4u1 do we want to try keeping a different branch for v14 patches?
You mean if we want to maintain v14 too?
@p4u1 yeah
@p4u1 please test, i did the deploy correctly but just now i realised the app.ini had changed locations and forgejo was waiting on the install page
Edited/Blocked Notification
Renovate will not automatically rebase this PR, because it does not recognize the last commit author and assumes somebody else may have edited the PR.
You can manually request rebase by checking the rebase/retry box above.
⚠️ Warning: custom changes will be lost.
@ -7,3 +7,3 @@configs:- source: app_initarget: /etc/gitea/app.initarget: /var/lib/gitea/custom/conf/app.inishall we take the opportunity to rename to forgejo?
Successfully deployed this on code.klasse-methode.it