forgejo/forgejo
forgejo/forgejo
109
3.8k
Fork 659
Code Issues 1.2k Pull requests 160 Releases 95 Packages 1 Activity Actions 24

chore(Dockerfile.rootless): remove legacy config file support #11098

Merged
0ko merged 7 commits from jaylinski/forgejo:rootless-image-remove-legacy-ini into forgejo 2026-03-02 06:03:41 +01:00
Conversation 17 Commits 7 Files changed 4 +6 -26
jaylinski commented 2026-01-29 18:14:11 +01:00
Contributor
Copy link

Docs PR: forgejo/docs#1740

This legacy support was added in version 8. We now have version 14, so this deprecated feature can be confidently removed.

See dad16cd589 for a detailed explanation.

Checklist

The contributor guide contains information that will be helpful to first time contributors. There also are a few conditions for merging Pull Requests in Forgejo repositories. You are also welcome to join the Forgejo development chatroom.

Tests

  • I added test coverage for Go changes...
    • in their respective *_test.go for unit tests.
    • in the tests/integration directory if it involves interactions with a live Forgejo server.
  • I added test coverage for JavaScript changes...

Documentation

  • I created a pull request to the documentation to explain to Forgejo users how to use this change.
  • I did not document these changes and I do not expect someone else to do it.

Release notes

  • This change will be noticed by a Forgejo user or admin (feature, bug fix, performance, etc.). I suggest to include a release note for this change.
  • This change is not visible to a Forgejo user or admin (refactor, dependency upgrade, etc.). I think there is no need to add a release note for this change.

The decision if the pull request will be shown in the release notes is up to the mergers / release team.

The content of the release-notes/<pull request number>.md file will serve as the basis for the release notes. If the file does not exist, the title of the pull request will be used instead.

Release notes

  • Breaking changes without a feature or bug label
    • PR: In Forgejo v8.0.0, the default location for the config file was changed from /etc/gitea/app.ini to /var/lib/gitea/app.ini. Backward compatibility logic and startup warnings were added to container setup and entrypoint scripts. Now they are removed. This change only affects those using container deployments with rootless images. If you have the config file stored in a volume bound to container's /etc/gitea, move it to the new location or override the environment variable GITEA_APP_INI. An unused volume /etc/gitea can be safely removed from the container after moving the config or if the deployment never used versions prior to v8.0.0.
Docs PR: https://codeberg.org/forgejo/docs/pulls/1740 --- This legacy support was added in version 8. We now have version 14, so this deprecated feature can be confidently removed. See dad16cd5895a945c067ec6a2dacdac67afc8aa04 for a detailed explanation. ## Checklist The [contributor guide](https://forgejo.org/docs/next/contributor/) contains information that will be helpful to first time contributors. There also are a few [conditions for merging Pull Requests in Forgejo repositories](https://codeberg.org/forgejo/governance/src/branch/main/PullRequestsAgreement.md). You are also welcome to join the [Forgejo development chatroom](https://matrix.to/#/#forgejo-development:matrix.org). ### Tests - I added test coverage for Go changes... - [x] in their respective `*_test.go` for unit tests. - [x] in the `tests/integration` directory if it involves interactions with a live Forgejo server. - I added test coverage for JavaScript changes... - [x] in `web_src/js/*.test.js` if it can be unit tested. - [x] in `tests/e2e/*.test.e2e.js` if it requires interactions with a live Forgejo server (see also the [developer guide for JavaScript testing](https://codeberg.org/forgejo/forgejo/src/branch/forgejo/tests/e2e/README.md#end-to-end-tests)). ### Documentation - [x] I created a pull request [to the documentation](https://codeberg.org/forgejo/docs) to explain to Forgejo users how to use this change. - [ ] I did not document these changes and I do not expect someone else to do it. ### Release notes - [x] This change will be noticed by a Forgejo user or admin (feature, bug fix, performance, etc.). I suggest to include a release note for this change. - [ ] This change is not visible to a Forgejo user or admin (refactor, dependency upgrade, etc.). I think there is no need to add a release note for this change. *The decision if the pull request will be shown in the release notes is up to the mergers / release team.* The content of the `release-notes/<pull request number>.md` file will serve as the basis for the release notes. If the file does not exist, the title of the pull request will be used instead. <!--start release-notes-assistant--> ## Release notes <!--URL:https://codeberg.org/forgejo/forgejo--> - Breaking changes without a feature or bug label - [PR](https://codeberg.org/forgejo/forgejo/pulls/11098): <!--number 11098 --><!--line 0 --><!--description SW4gRm9yZ2VqbyB2OC4wLjAsIHRoZSBkZWZhdWx0IGxvY2F0aW9uIGZvciB0aGUgY29uZmlnIGZpbGUgd2FzIGNoYW5nZWQgZnJvbSBgL2V0Yy9naXRlYS9hcHAuaW5pYCB0byBgL3Zhci9saWIvZ2l0ZWEvYXBwLmluaWAuIEJhY2t3YXJkIGNvbXBhdGliaWxpdHkgbG9naWMgYW5kIHN0YXJ0dXAgd2FybmluZ3Mgd2VyZSBhZGRlZCB0byBjb250YWluZXIgc2V0dXAgYW5kIGVudHJ5cG9pbnQgc2NyaXB0cy4gTm93IHRoZXkgYXJlIHJlbW92ZWQuIFRoaXMgY2hhbmdlIG9ubHkgYWZmZWN0cyB0aG9zZSB1c2luZyBjb250YWluZXIgZGVwbG95bWVudHMgd2l0aCByb290bGVzcyBpbWFnZXMuIElmIHlvdSBoYXZlIHRoZSBjb25maWcgZmlsZSBzdG9yZWQgaW4gYSB2b2x1bWUgYm91bmQgdG8gY29udGFpbmVyJ3MgL2V0Yy9naXRlYSwgbW92ZSBpdCB0byB0aGUgbmV3IGxvY2F0aW9uIG9yIG92ZXJyaWRlIHRoZSBlbnZpcm9ubWVudCB2YXJpYWJsZSBgR0lURUFfQVBQX0lOSWAuIEFuIHVudXNlZCB2b2x1bWUgYC9ldGMvZ2l0ZWFgIGNhbiBiZSBzYWZlbHkgcmVtb3ZlZCBmcm9tIHRoZSBjb250YWluZXIgYWZ0ZXIgbW92aW5nIHRoZSBjb25maWcgb3IgaWYgdGhlIGRlcGxveW1lbnQgbmV2ZXIgdXNlZCB2ZXJzaW9ucyBwcmlvciB0byB2OC4wLjAu-->In Forgejo v8.0.0, the default location for the config file was changed from `/etc/gitea/app.ini` to `/var/lib/gitea/app.ini`. Backward compatibility logic and startup warnings were added to container setup and entrypoint scripts. Now they are removed. This change only affects those using container deployments with rootless images. If you have the config file stored in a volume bound to container's /etc/gitea, move it to the new location or override the environment variable `GITEA_APP_INI`. An unused volume `/etc/gitea` can be safely removed from the container after moving the config or if the deployment never used versions prior to v8.0.0.<!--description--> <!--end release-notes-assistant-->
chore(Dockerfile.rootless): remove legacy config file support
Some checks failed
issue-labels / backporting (pull_request_target) Has been skipped
Details
issue-labels / cascade (pull_request_target) Has been skipped
Details
issue-labels / release-notes (pull_request_target) Successful in 1m4s
Details
Integration tests for the release process / release-simulation (pull_request) Has been cancelled
Details
requirements / merge-conditions (pull_request) Has been cancelled
Details
testing / frontend-checks (pull_request) Failing after 25s
Details
testing / backend-checks (pull_request) Failing after 1m5s
Details
testing / test-mysql (pull_request) Has been skipped
Details
testing / test-unit (pull_request) Has been skipped
Details
testing / test-sqlite (pull_request) Has been skipped
Details
testing / test-e2e (pull_request) Has been skipped
Details
testing / test-pgsql (pull_request) Has been skipped
Details
testing / test-remote-cacher (redict) (pull_request) Has been skipped
Details
testing / test-remote-cacher (redis) (pull_request) Has been skipped
Details
testing / test-remote-cacher (valkey) (pull_request) Has been skipped
Details
testing / test-remote-cacher (garnet) (pull_request) Has been skipped
Details
testing / security-check (pull_request) Has been skipped
Details
050d9c291e 
This legacy support was added in version 8. We now
have version 14, so this deprecated feature can be
confidently removed.

See dad16cd589 for a
detailed explanation.
jaylinski commented 2026-01-29 18:23:16 +01:00
Author
Contributor
Copy link

Pull request to change documentation: forgejo/docs#1740

Pull request to change documentation: https://codeberg.org/forgejo/docs/pulls/1740
forgejo-release-notes-assistant commented 2026-02-01 19:29:48 +01:00
Member
Copy link
Where does that come from? The following is a preview of the release notes for this pull request, as they will appear in the upcoming release. They are derived from the content of the `release-notes/11098.md` file, if it exists, or the title of the pull request. They were also added at the bottom of the description of this pull request for easier reference.

This message and the release notes originate from a call to the release-notes-assistant.

@@ -30,2 +30,10 @@
 
 The content of the `release-notes/<pull request number>.md` file will serve as the basis for the release notes. If the file does not exist, the title of the pull request will be used instead.
+
+<!--start release-notes-assistant-->
+
+## Release notes
+<!--URL:https://codeberg.org/forgejo/forgejo-->
+- Breaking changes without a feature or bug label
+  - [PR](https://codeberg.org/forgejo/forgejo/pulls/11098): <!--number 11098 --><!--line 0 --><!--description Y2hvcmUoRG9ja2VyZmlsZS5yb290bGVzcyk6IHJlbW92ZSBsZWdhY3kgY29uZmlnIGZpbGUgc3VwcG9ydA==-->chore(Dockerfile.rootless): remove legacy config file support<!--description-->
+<!--end release-notes-assistant-->

Release notes

  • Breaking changes without a feature or bug label
    • PR: chore(Dockerfile.rootless): remove legacy config file support
<details> <summary>Where does that come from?</summary> The following is a preview of the release notes for this pull request, as they will appear in the upcoming release. They are derived from the content of the `release-notes/11098.md` file, if it exists, or the title of the pull request. They were also added at the bottom of the description of this pull request for easier reference. This message and the release notes originate from a call to the [release-notes-assistant](https://code.forgejo.org/forgejo/release-notes-assistant). ```diff @@ -30,2 +30,10 @@ The content of the `release-notes/<pull request number>.md` file will serve as the basis for the release notes. If the file does not exist, the title of the pull request will be used instead. + +<!--start release-notes-assistant--> + +## Release notes +<!--URL:https://codeberg.org/forgejo/forgejo--> +- Breaking changes without a feature or bug label + - [PR](https://codeberg.org/forgejo/forgejo/pulls/11098): <!--number 11098 --><!--line 0 --><!--description Y2hvcmUoRG9ja2VyZmlsZS5yb290bGVzcyk6IHJlbW92ZSBsZWdhY3kgY29uZmlnIGZpbGUgc3VwcG9ydA==-->chore(Dockerfile.rootless): remove legacy config file support<!--description--> +<!--end release-notes-assistant--> ``` </details> <!--start release-notes-assistant--> ## Release notes <!--URL:https://codeberg.org/forgejo/forgejo--> - Breaking changes without a feature or bug label - [PR](https://codeberg.org/forgejo/forgejo/pulls/11098): <!--number 11098 --><!--line 0 --><!--description Y2hvcmUoRG9ja2VyZmlsZS5yb290bGVzcyk6IHJlbW92ZSBsZWdhY3kgY29uZmlnIGZpbGUgc3VwcG9ydA==-->chore(Dockerfile.rootless): remove legacy config file support<!--description--> <!--end release-notes-assistant-->
Gusted commented 2026-02-03 14:42:39 +01:00
Owner
Copy link

I don't use docker, so not sure how big of a problem this still is (as in how many users) and if the warning has been seen by many. @viceice maybe you have some insights into this?

I don't use docker, so not sure how big of a problem this still is (as in how many users) and if the warning has been seen by many. @viceice maybe you have some insights into this?
viceice commented 2026-02-03 15:28:16 +01:00
Owner
Copy link

@Gusted wrote in #11098 (comment):

I don't use docker, so not sure how big of a problem this still is (as in how many users) and if the warning has been seen by many. @viceice maybe you have some insights into this?

I only use it in the helm chart which is always override the app ini path explicit. so it was ok to maintain the workaround for a while and can now be removed.

https://code.forgejo.org/forgejo-helm/forgejo-helm/search/branch/main?path=&q=GITEA_APP_INI&mode=exact

@Gusted wrote in https://codeberg.org/forgejo/forgejo/pulls/11098#issuecomment-10341430: > I don't use docker, so not sure how big of a problem this still is (as in how many users) and if the warning has been seen by many. @viceice maybe you have some insights into this? I only use it in the helm chart which is always override the app ini path explicit. so it was ok to maintain the workaround for a while and can now be removed. https://code.forgejo.org/forgejo-helm/forgejo-helm/search/branch/main?path=&q=GITEA_APP_INI&mode=exact
viceice approved these changes 2026-02-03 15:29:34 +01:00
Gusted commented 2026-02-07 01:45:42 +01:00
Owner
Copy link

Is this worth of a dedicated release note entry that explains what support is being removed and the migration path? It's already clearly given for the past few releases but will now be removed along with the support. @forgejo/Releases.

Is this worth of a dedicated release note entry that explains what support is being removed and the migration path? It's already clearly given for the past few releases but will now be removed along with the support. @forgejo/Releases.
0ko approved these changes 2026-02-07 15:07:04 +01:00
0ko commented 2026-02-07 15:08:00 +01:00
Owner
Copy link

@Gusted wrote in #11098 (comment):

@forgejo/Releases

The addition in Forgejo 8 was long enough for people to get used to ignoring the warning, so a little explanation linking to a detailed one is good to add.

@Gusted wrote in https://codeberg.org/forgejo/forgejo/pulls/11098#issuecomment-10420714: > @forgejo/Releases The addition in Forgejo 8 was long enough for people to get used to ignoring the warning, so a little explanation linking to a detailed one is good to add.
Beowulf commented 2026-02-07 18:45:54 +01:00
Owner
Copy link

@0ko wrote in #11098 (comment):

people to get used to ignoring the warning

I feel called out...

WARNING: detected configuration file in deprecated default path /etc/gitea/app.ini. The new default is /var/lib/gitea/custom/conf/app.ini. To remove this warning, choose one of the options:
 * Move /etc/gitea/app.ini to /var/lib/gitea/custom/conf/app.ini (or to $GITEA_APP_INI if you want to override this variable)

🥴

And I remember why I haven't changed it, because I did run into it again:
After moving the config file to the new place and deleting the file in the old place, forgejo just crash-looped. Last time I just reverted, because docker logs just showed everything is fine, but this time I took a look and found in the log file:

2026/02/07 18:41:24 modules/ssh/init.go:86:Init() [F] An unexpected ssh public key was discovered. Forgejo will shutdown to require this to be fixed. Fix by either:
Option 1: Delete the file /var/lib/gitea/git/.ssh/authorized_keys, and Forgejo will recreate it with only expected ssh public keys.
Option 2: Permit unexpected keys by setting [server].SSH_ALLOW_UNEXPECTED_AUTHORIZED_KEYS=true in Forgejo's config file.
Option 3: If unused, disable SSH support by setting [server].DISABLE_SSH=true in Forgejo's config file.
        Key on line 2 of /var/lib/gitea/git/.ssh/authorized_keys does not exist in database
        Key on line 4 of /var/lib/gitea/git/.ssh/authorized_keys does not exist in database
        Key on line 6 of /var/lib/gitea/git/.ssh/authorized_keys does not exist in database

I have no idea, how this happened due to moving the config file? 🤔

@0ko wrote in https://codeberg.org/forgejo/forgejo/pulls/11098#issuecomment-10428190: > people to get used to ignoring the warning I feel called out... ``` WARNING: detected configuration file in deprecated default path /etc/gitea/app.ini. The new default is /var/lib/gitea/custom/conf/app.ini. To remove this warning, choose one of the options: * Move /etc/gitea/app.ini to /var/lib/gitea/custom/conf/app.ini (or to $GITEA_APP_INI if you want to override this variable) ``` 🥴 And I remember why I haven't changed it, because I did run into it again: After moving the config file to the new place and deleting the file in the old place, forgejo just crash-looped. Last time I just reverted, because `docker logs` just showed everything is fine, but this time I took a look and found in the log file: ``` 2026/02/07 18:41:24 modules/ssh/init.go:86:Init() [F] An unexpected ssh public key was discovered. Forgejo will shutdown to require this to be fixed. Fix by either: Option 1: Delete the file /var/lib/gitea/git/.ssh/authorized_keys, and Forgejo will recreate it with only expected ssh public keys. Option 2: Permit unexpected keys by setting [server].SSH_ALLOW_UNEXPECTED_AUTHORIZED_KEYS=true in Forgejo's config file. Option 3: If unused, disable SSH support by setting [server].DISABLE_SSH=true in Forgejo's config file. Key on line 2 of /var/lib/gitea/git/.ssh/authorized_keys does not exist in database Key on line 4 of /var/lib/gitea/git/.ssh/authorized_keys does not exist in database Key on line 6 of /var/lib/gitea/git/.ssh/authorized_keys does not exist in database ``` I have no idea, how this happened due to moving the config file? 🤔
mfenniak commented 2026-02-07 18:52:08 +01:00
Member
Copy link

@Beowulf wrote in #11098 (comment):

I have no idea, how this happened due to moving the config file? 🤔

The config file is referenced in the authorized_keys file. If it changes, it doesn't match Forgejo's expected file contents.

# gitea public key
command=".../bin/forgejo --config=...configpath.../app.ini serv key-9",...etc...
@Beowulf wrote in https://codeberg.org/forgejo/forgejo/pulls/11098#issuecomment-10431296: > I have no idea, how this happened due to moving the config file? :thinking: The config file is referenced in the `authorized_keys` file. If it changes, it doesn't match Forgejo's expected file contents. ``` # gitea public key command=".../bin/forgejo --config=...configpath.../app.ini serv key-9",...etc... ```
Beowulf commented 2026-02-07 18:54:21 +01:00
Owner
Copy link

@mfenniak wrote in #11098 (comment):

The config file is referenced in the authorized_keys file. If it changes, it doesn't match Forgejo's expected file contents.

Ah, you're right, I don't even use the authorized_keys file in this instance, this was another reason, why I haven't thought about this.
But I think this is another reason to mention it clearly in the release notes.

@mfenniak wrote in https://codeberg.org/forgejo/forgejo/pulls/11098#issuecomment-10431402: > The config file is referenced in the `authorized_keys` file. If it changes, it doesn't match Forgejo's expected file contents. Ah, you're right, I don't even use the `authorized_keys` file in this instance, this was another reason, why I haven't thought about this. But I think this is another reason to mention it clearly in the release notes.
👍 1
jaylinski commented 2026-02-27 20:47:35 +01:00
Author
Contributor
Copy link

Hi! Thanks for the review. Is there anything else I should do to get this merged?

Hi! Thanks for the review. Is there anything else I should do to get this merged?
0ko commented 2026-02-28 12:40:02 +01:00
Owner
Copy link

Hi! There are some weird CI failures on your branch.

Hi! There are some weird CI failures on your branch.
jaylinski force-pushed rootless-image-remove-legacy-ini from 050d9c291e
Some checks failed
issue-labels / backporting (pull_request_target) Has been skipped
Details
issue-labels / cascade (pull_request_target) Has been skipped
Details
issue-labels / release-notes (pull_request_target) Successful in 1m4s
Details
Integration tests for the release process / release-simulation (pull_request) Has been cancelled
Details
requirements / merge-conditions (pull_request) Has been cancelled
Details
testing / frontend-checks (pull_request) Failing after 25s
Details
testing / backend-checks (pull_request) Failing after 1m5s
Details
testing / test-mysql (pull_request) Has been skipped
Details
testing / test-unit (pull_request) Has been skipped
Details
testing / test-sqlite (pull_request) Has been skipped
Details
testing / test-e2e (pull_request) Has been skipped
Details
testing / test-pgsql (pull_request) Has been skipped
Details
testing / test-remote-cacher (redict) (pull_request) Has been skipped
Details
testing / test-remote-cacher (redis) (pull_request) Has been skipped
Details
testing / test-remote-cacher (valkey) (pull_request) Has been skipped
Details
testing / test-remote-cacher (garnet) (pull_request) Has been skipped
Details
testing / security-check (pull_request) Has been skipped
Details
to 570580356b
All checks were successful
issue-labels / release-notes (pull_request_target) Successful in 25s
Details
requirements / merge-conditions (pull_request) Successful in 3s
Details
testing / semgrep/ci (pull_request) Successful in 11s
Details
testing / frontend-checks (pull_request) Successful in 53s
Details
testing / backend-checks (pull_request) Successful in 2m48s
Details
Integration tests for the release process / release-simulation (pull_request) Successful in 5m38s
Details
testing / test-unit (pull_request) Successful in 5m57s
Details
testing / test-remote-cacher (redict) (pull_request) Successful in 2m0s
Details
testing / test-remote-cacher (valkey) (pull_request) Successful in 2m1s
Details
testing / test-remote-cacher (garnet) (pull_request) Successful in 2m1s
Details
testing / test-remote-cacher (redis) (pull_request) Successful in 2m3s
Details
testing / test-e2e (pull_request) Successful in 18m16s
Details
testing / test-mysql (pull_request) Successful in 20m51s
Details
testing / test-sqlite (pull_request) Successful in 25m55s
Details
testing / test-pgsql (pull_request) Successful in 30m10s
Details
testing / security-check (pull_request) Successful in 1m3s
Details
2026-02-28 19:47:16 +01:00 Compare
jaylinski commented 2026-02-28 19:51:23 +01:00
Author
Contributor
Copy link

@0ko wrote in #11098 (comment):

Hi! There are some weird CI failures on your branch.

I rebased the branch, please run the CI pipelines again.

@0ko wrote in https://codeberg.org/forgejo/forgejo/pulls/11098#issuecomment-11076677: > Hi! There are some weird CI failures on your branch. I rebased the branch, please run the CI pipelines again.
👍 1
add release note
Some checks failed
testing / semgrep/ci (pull_request) Successful in 11s
Details
testing / frontend-checks (pull_request) Successful in 58s
Details
requirements / merge-conditions (pull_request) Successful in 3s
Details
issue-labels / release-notes (pull_request_target) Has been cancelled
Details
Integration tests for the release process / release-simulation (pull_request) Has been cancelled
Details
testing / backend-checks (pull_request) Has been cancelled
Details
testing / test-unit (pull_request) Has been cancelled
Details
testing / test-e2e (pull_request) Has been cancelled
Details
testing / test-remote-cacher (redis) (pull_request) Has been cancelled
Details
testing / test-remote-cacher (valkey) (pull_request) Has been cancelled
Details
testing / test-remote-cacher (garnet) (pull_request) Has been cancelled
Details
testing / test-remote-cacher (redict) (pull_request) Has been cancelled
Details
testing / test-mysql (pull_request) Has been cancelled
Details
testing / test-pgsql (pull_request) Has been cancelled
Details
testing / test-sqlite (pull_request) Has been cancelled
Details
testing / security-check (pull_request) Has been cancelled
Details
5c9821d4b7
rootless
Some checks failed
testing / semgrep/ci (pull_request) Successful in 11s
Details
requirements / merge-conditions (pull_request) Successful in 2s
Details
issue-labels / release-notes (pull_request_target) Successful in 27s
Details
testing / frontend-checks (pull_request) Successful in 1m3s
Details
Integration tests for the release process / release-simulation (pull_request) Has been cancelled
Details
testing / backend-checks (pull_request) Has been cancelled
Details
testing / test-unit (pull_request) Has been cancelled
Details
testing / test-e2e (pull_request) Has been cancelled
Details
testing / test-remote-cacher (redis) (pull_request) Has been cancelled
Details
testing / test-remote-cacher (valkey) (pull_request) Has been cancelled
Details
testing / test-remote-cacher (garnet) (pull_request) Has been cancelled
Details
testing / test-remote-cacher (redict) (pull_request) Has been cancelled
Details
testing / test-mysql (pull_request) Has been cancelled
Details
testing / test-pgsql (pull_request) Has been cancelled
Details
testing / test-sqlite (pull_request) Has been cancelled
Details
testing / security-check (pull_request) Has been cancelled
Details
f099ffcd21
0ko commented 2026-03-01 05:39:25 +01:00
Owner
Copy link

I added a dedicated release note per #11098 (comment) / #11098 (comment).

I think this is mergeable but need someone to approve the release note.

I added a dedicated release note per https://codeberg.org/forgejo/forgejo/pulls/11098#issuecomment-10420714 / https://codeberg.org/forgejo/forgejo/pulls/11098#issuecomment-10428190. I think this is mergeable but need someone to approve the release note.
👍 1
rna hates separate lines?
Some checks failed
testing / semgrep/ci (pull_request) Successful in 12s
Details
requirements / merge-conditions (pull_request) Successful in 2s
Details
issue-labels / release-notes (pull_request_target) Successful in 26s
Details
testing / frontend-checks (pull_request) Successful in 1m2s
Details
Integration tests for the release process / release-simulation (pull_request) Has been cancelled
Details
testing / backend-checks (pull_request) Has been cancelled
Details
testing / test-unit (pull_request) Has been cancelled
Details
testing / test-e2e (pull_request) Has been cancelled
Details
testing / test-remote-cacher (redis) (pull_request) Has been cancelled
Details
testing / test-remote-cacher (valkey) (pull_request) Has been cancelled
Details
testing / test-remote-cacher (garnet) (pull_request) Has been cancelled
Details
testing / test-remote-cacher (redict) (pull_request) Has been cancelled
Details
testing / test-mysql (pull_request) Has been cancelled
Details
testing / test-pgsql (pull_request) Has been cancelled
Details
testing / test-sqlite (pull_request) Has been cancelled
Details
testing / security-check (pull_request) Has been cancelled
Details
7218642145
k rna hates all formatting
Some checks failed
testing / semgrep/ci (pull_request) Successful in 12s
Details
requirements / merge-conditions (pull_request) Successful in 3s
Details
issue-labels / release-notes (pull_request_target) Successful in 27s
Details
testing / frontend-checks (pull_request) Successful in 1m3s
Details
testing / backend-checks (pull_request) Successful in 2m14s
Details
testing / test-unit (pull_request) Has been cancelled
Details
testing / test-e2e (pull_request) Has been cancelled
Details
Integration tests for the release process / release-simulation (pull_request) Has been cancelled
Details
testing / test-pgsql (pull_request) Has been cancelled
Details
testing / test-sqlite (pull_request) Has been cancelled
Details
testing / test-mysql (pull_request) Has been cancelled
Details
testing / test-remote-cacher (redis) (pull_request) Has been cancelled
Details
testing / test-remote-cacher (valkey) (pull_request) Has been cancelled
Details
testing / test-remote-cacher (garnet) (pull_request) Has been cancelled
Details
testing / test-remote-cacher (redict) (pull_request) Has been cancelled
Details
testing / security-check (pull_request) Has been cancelled
Details
e8b9d0a5e3
.
Some checks failed
testing / semgrep/ci (pull_request) Successful in 13s
Details
requirements / merge-conditions (pull_request) Successful in 1s
Details
issue-labels / release-notes (pull_request_target) Successful in 29s
Details
testing / frontend-checks (pull_request) Successful in 1m4s
Details
testing / backend-checks (pull_request) Successful in 2m21s
Details
testing / test-unit (pull_request) Successful in 5m52s
Details
testing / test-remote-cacher (redict) (pull_request) Successful in 2m4s
Details
testing / test-remote-cacher (valkey) (pull_request) Successful in 2m6s
Details
testing / test-remote-cacher (redis) (pull_request) Successful in 2m8s
Details
testing / test-remote-cacher (garnet) (pull_request) Successful in 2m7s
Details
testing / test-e2e (pull_request) Successful in 18m6s
Details
testing / test-mysql (pull_request) Successful in 20m21s
Details
testing / test-sqlite (pull_request) Successful in 25m26s
Details
testing / test-pgsql (pull_request) Successful in 29m39s
Details
testing / security-check (pull_request) Successful in 56s
Details
Integration tests for the release process / release-simulation (pull_request) Has been cancelled
Details
f0c7f00ab4
Gusted reviewed 2026-03-02 02:21:48 +01:00
release-notes/11098.md Outdated
@ -0,0 +1 @@
In Forgejo v8.0.0, the default location for the config file was changed from `/etc/gitea/app.ini` to `/var/lib/gitea/app.ini`. Backward compatibility logic and startup warnings were added to container setup and entrypoint scripts. Now they are removed. This change only affects those using container deployments with rootless images. If you have the config file stored in a volume bound to container's /etc/gitea, move it to the new location or override the environment variable `GITEA_APP_INI`. An unused `/etc/gitea` can be safely from container volumes after moving the config or if the deployment never used versions prior to v8.0.0.
Gusted commented 2026-03-02 02:21:48 +01:00
Owner
Copy link

'An unused /etc/gitea can be safely from container'

Word missing after 'safely'?

'An unused `/etc/gitea` can be safely from container' Word missing after 'safely'?
👍 1
0ko marked this conversation as resolved
Update release-notes/11098.md
All checks were successful
testing / semgrep/ci (pull_request) Successful in 16s
Details
testing / frontend-checks (pull_request) Successful in 1m2s
Details
requirements / merge-conditions (pull_request) Successful in 6s
Details
issue-labels / release-notes (pull_request_target) Successful in 30s
Details
testing / backend-checks (pull_request) Successful in 2m49s
Details
Integration tests for the release process / release-simulation (pull_request) Successful in 5m36s
Details
testing / test-unit (pull_request) Successful in 6m5s
Details
testing / test-remote-cacher (garnet) (pull_request) Successful in 2m3s
Details
testing / test-remote-cacher (valkey) (pull_request) Successful in 2m4s
Details
testing / test-remote-cacher (redis) (pull_request) Successful in 2m6s
Details
testing / test-remote-cacher (redict) (pull_request) Successful in 2m2s
Details
testing / test-e2e (pull_request) Successful in 18m12s
Details
testing / test-mysql (pull_request) Successful in 20m48s
Details
testing / test-sqlite (pull_request) Successful in 25m50s
Details
testing / test-pgsql (pull_request) Successful in 30m6s
Details
testing / security-check (pull_request) Successful in 54s
Details
issue-labels / backporting (pull_request_target) Has been skipped
Details
milestone / set (pull_request_target) Successful in 5s
Details
6713c23c88
forgejo-release-notes-assistant commented 2026-03-02 04:24:18 +01:00
Member
Copy link
Where does that come from? The following is a preview of the release notes for this pull request, as they will appear in the upcoming release. They are derived from the content of the `release-notes/11098.md` file, if it exists, or the title of the pull request. They were also added at the bottom of the description of this pull request for easier reference.

This message and the release notes originate from a call to the release-notes-assistant.

@@ -40,4 +40,4 @@
 <!--URL:https://codeberg.org/forgejo/forgejo-->
 - Breaking changes without a feature or bug label
-  - [PR](https://codeberg.org/forgejo/forgejo/pulls/11098): <!--number 11098 --><!--line 0 --><!--description SW4gRm9yZ2VqbyB2OC4wLjAsIHRoZSBkZWZhdWx0IGxvY2F0aW9uIGZvciB0aGUgY29uZmlnIGZpbGUgd2FzIGNoYW5nZWQgZnJvbSBgL2V0Yy9naXRlYS9hcHAuaW5pYCB0byBgL3Zhci9saWIvZ2l0ZWEvYXBwLmluaWAuIEJhY2t3YXJkIGNvbXBhdGliaWxpdHkgbG9naWMgYW5kIHN0YXJ0dXAgd2FybmluZ3Mgd2VyZSBhZGRlZCB0byBjb250YWluZXIgc2V0dXAgYW5kIGVudHJ5cG9pbnQgc2NyaXB0cy4gTm93IHRoZXkgYXJlIHJlbW92ZWQuIFRoaXMgY2hhbmdlIG9ubHkgYWZmZWN0cyB0aG9zZSB1c2luZyBjb250YWluZXIgZGVwbG95bWVudHMgd2l0aCByb290bGVzcyBpbWFnZXMuIElmIHlvdSBoYXZlIHRoZSBjb25maWcgZmlsZSBzdG9yZWQgaW4gYSB2b2x1bWUgYm91bmQgdG8gY29udGFpbmVyJ3MgL2V0Yy9naXRlYSwgbW92ZSBpdCB0byB0aGUgbmV3IGxvY2F0aW9uIG9yIG92ZXJyaWRlIHRoZSBlbnZpcm9ubWVudCB2YXJpYWJsZSBgR0lURUFfQVBQX0lOSWAuIEFuIHVudXNlZCBgL2V0Yy9naXRlYWAgY2FuIGJlIHNhZmVseSBmcm9tIGNvbnRhaW5lciB2b2x1bWVzIGFmdGVyIG1vdmluZyB0aGUgY29uZmlnIG9yIGlmIHRoZSBkZXBsb3ltZW50IG5ldmVyIHVzZWQgdmVyc2lvbnMgcHJpb3IgdG8gdjguMC4wLg==-->In Forgejo v8.0.0, the default location for the config file was changed from `/etc/gitea/app.ini` to `/var/lib/gitea/app.ini`. Backward compatibility logic and startup warnings were added to container setup and entrypoint scripts. Now they are removed. This change only affects those using container deployments with rootless images. If you have the config file stored in a volume bound to container's /etc/gitea, move it to the new location or override the environment variable `GITEA_APP_INI`. An unused `/etc/gitea` can be safely from container volumes after moving the config or if the deployment never used versions prior to v8.0.0.<!--description-->
+  - [PR](https://codeberg.org/forgejo/forgejo/pulls/11098): <!--number 11098 --><!--line 0 --><!--description SW4gRm9yZ2VqbyB2OC4wLjAsIHRoZSBkZWZhdWx0IGxvY2F0aW9uIGZvciB0aGUgY29uZmlnIGZpbGUgd2FzIGNoYW5nZWQgZnJvbSBgL2V0Yy9naXRlYS9hcHAuaW5pYCB0byBgL3Zhci9saWIvZ2l0ZWEvYXBwLmluaWAuIEJhY2t3YXJkIGNvbXBhdGliaWxpdHkgbG9naWMgYW5kIHN0YXJ0dXAgd2FybmluZ3Mgd2VyZSBhZGRlZCB0byBjb250YWluZXIgc2V0dXAgYW5kIGVudHJ5cG9pbnQgc2NyaXB0cy4gTm93IHRoZXkgYXJlIHJlbW92ZWQuIFRoaXMgY2hhbmdlIG9ubHkgYWZmZWN0cyB0aG9zZSB1c2luZyBjb250YWluZXIgZGVwbG95bWVudHMgd2l0aCByb290bGVzcyBpbWFnZXMuIElmIHlvdSBoYXZlIHRoZSBjb25maWcgZmlsZSBzdG9yZWQgaW4gYSB2b2x1bWUgYm91bmQgdG8gY29udGFpbmVyJ3MgL2V0Yy9naXRlYSwgbW92ZSBpdCB0byB0aGUgbmV3IGxvY2F0aW9uIG9yIG92ZXJyaWRlIHRoZSBlbnZpcm9ubWVudCB2YXJpYWJsZSBgR0lURUFfQVBQX0lOSWAuIEFuIHVudXNlZCB2b2x1bWUgYC9ldGMvZ2l0ZWFgIGNhbiBiZSBzYWZlbHkgcmVtb3ZlZCBmcm9tIHRoZSBjb250YWluZXIgYWZ0ZXIgbW92aW5nIHRoZSBjb25maWcgb3IgaWYgdGhlIGRlcGxveW1lbnQgbmV2ZXIgdXNlZCB2ZXJzaW9ucyBwcmlvciB0byB2OC4wLjAu-->In Forgejo v8.0.0, the default location for the config file was changed from `/etc/gitea/app.ini` to `/var/lib/gitea/app.ini`. Backward compatibility logic and startup warnings were added to container setup and entrypoint scripts. Now they are removed. This change only affects those using container deployments with rootless images. If you have the config file stored in a volume bound to container's /etc/gitea, move it to the new location or override the environment variable `GITEA_APP_INI`. An unused volume `/etc/gitea` can be safely removed from the container after moving the config or if the deployment never used versions prior to v8.0.0.<!--description-->
 <!--end release-notes-assistant-->

Release notes

  • Breaking changes without a feature or bug label
    • PR: In Forgejo v8.0.0, the default location for the config file was changed from /etc/gitea/app.ini to /var/lib/gitea/app.ini. Backward compatibility logic and startup warnings were added to container setup and entrypoint scripts. Now they are removed. This change only affects those using container deployments with rootless images. If you have the config file stored in a volume bound to container's /etc/gitea, move it to the new location or override the environment variable GITEA_APP_INI. An unused volume /etc/gitea can be safely removed from the container after moving the config or if the deployment never used versions prior to v8.0.0.
<details> <summary>Where does that come from?</summary> The following is a preview of the release notes for this pull request, as they will appear in the upcoming release. They are derived from the content of the `release-notes/11098.md` file, if it exists, or the title of the pull request. They were also added at the bottom of the description of this pull request for easier reference. This message and the release notes originate from a call to the [release-notes-assistant](https://code.forgejo.org/forgejo/release-notes-assistant). ```diff @@ -40,4 +40,4 @@ <!--URL:https://codeberg.org/forgejo/forgejo--> - Breaking changes without a feature or bug label - - [PR](https://codeberg.org/forgejo/forgejo/pulls/11098): <!--number 11098 --><!--line 0 --><!--description SW4gRm9yZ2VqbyB2OC4wLjAsIHRoZSBkZWZhdWx0IGxvY2F0aW9uIGZvciB0aGUgY29uZmlnIGZpbGUgd2FzIGNoYW5nZWQgZnJvbSBgL2V0Yy9naXRlYS9hcHAuaW5pYCB0byBgL3Zhci9saWIvZ2l0ZWEvYXBwLmluaWAuIEJhY2t3YXJkIGNvbXBhdGliaWxpdHkgbG9naWMgYW5kIHN0YXJ0dXAgd2FybmluZ3Mgd2VyZSBhZGRlZCB0byBjb250YWluZXIgc2V0dXAgYW5kIGVudHJ5cG9pbnQgc2NyaXB0cy4gTm93IHRoZXkgYXJlIHJlbW92ZWQuIFRoaXMgY2hhbmdlIG9ubHkgYWZmZWN0cyB0aG9zZSB1c2luZyBjb250YWluZXIgZGVwbG95bWVudHMgd2l0aCByb290bGVzcyBpbWFnZXMuIElmIHlvdSBoYXZlIHRoZSBjb25maWcgZmlsZSBzdG9yZWQgaW4gYSB2b2x1bWUgYm91bmQgdG8gY29udGFpbmVyJ3MgL2V0Yy9naXRlYSwgbW92ZSBpdCB0byB0aGUgbmV3IGxvY2F0aW9uIG9yIG92ZXJyaWRlIHRoZSBlbnZpcm9ubWVudCB2YXJpYWJsZSBgR0lURUFfQVBQX0lOSWAuIEFuIHVudXNlZCBgL2V0Yy9naXRlYWAgY2FuIGJlIHNhZmVseSBmcm9tIGNvbnRhaW5lciB2b2x1bWVzIGFmdGVyIG1vdmluZyB0aGUgY29uZmlnIG9yIGlmIHRoZSBkZXBsb3ltZW50IG5ldmVyIHVzZWQgdmVyc2lvbnMgcHJpb3IgdG8gdjguMC4wLg==-->In Forgejo v8.0.0, the default location for the config file was changed from `/etc/gitea/app.ini` to `/var/lib/gitea/app.ini`. Backward compatibility logic and startup warnings were added to container setup and entrypoint scripts. Now they are removed. This change only affects those using container deployments with rootless images. If you have the config file stored in a volume bound to container's /etc/gitea, move it to the new location or override the environment variable `GITEA_APP_INI`. An unused `/etc/gitea` can be safely from container volumes after moving the config or if the deployment never used versions prior to v8.0.0.<!--description--> + - [PR](https://codeberg.org/forgejo/forgejo/pulls/11098): <!--number 11098 --><!--line 0 --><!--description SW4gRm9yZ2VqbyB2OC4wLjAsIHRoZSBkZWZhdWx0IGxvY2F0aW9uIGZvciB0aGUgY29uZmlnIGZpbGUgd2FzIGNoYW5nZWQgZnJvbSBgL2V0Yy9naXRlYS9hcHAuaW5pYCB0byBgL3Zhci9saWIvZ2l0ZWEvYXBwLmluaWAuIEJhY2t3YXJkIGNvbXBhdGliaWxpdHkgbG9naWMgYW5kIHN0YXJ0dXAgd2FybmluZ3Mgd2VyZSBhZGRlZCB0byBjb250YWluZXIgc2V0dXAgYW5kIGVudHJ5cG9pbnQgc2NyaXB0cy4gTm93IHRoZXkgYXJlIHJlbW92ZWQuIFRoaXMgY2hhbmdlIG9ubHkgYWZmZWN0cyB0aG9zZSB1c2luZyBjb250YWluZXIgZGVwbG95bWVudHMgd2l0aCByb290bGVzcyBpbWFnZXMuIElmIHlvdSBoYXZlIHRoZSBjb25maWcgZmlsZSBzdG9yZWQgaW4gYSB2b2x1bWUgYm91bmQgdG8gY29udGFpbmVyJ3MgL2V0Yy9naXRlYSwgbW92ZSBpdCB0byB0aGUgbmV3IGxvY2F0aW9uIG9yIG92ZXJyaWRlIHRoZSBlbnZpcm9ubWVudCB2YXJpYWJsZSBgR0lURUFfQVBQX0lOSWAuIEFuIHVudXNlZCB2b2x1bWUgYC9ldGMvZ2l0ZWFgIGNhbiBiZSBzYWZlbHkgcmVtb3ZlZCBmcm9tIHRoZSBjb250YWluZXIgYWZ0ZXIgbW92aW5nIHRoZSBjb25maWcgb3IgaWYgdGhlIGRlcGxveW1lbnQgbmV2ZXIgdXNlZCB2ZXJzaW9ucyBwcmlvciB0byB2OC4wLjAu-->In Forgejo v8.0.0, the default location for the config file was changed from `/etc/gitea/app.ini` to `/var/lib/gitea/app.ini`. Backward compatibility logic and startup warnings were added to container setup and entrypoint scripts. Now they are removed. This change only affects those using container deployments with rootless images. If you have the config file stored in a volume bound to container's /etc/gitea, move it to the new location or override the environment variable `GITEA_APP_INI`. An unused volume `/etc/gitea` can be safely removed from the container after moving the config or if the deployment never used versions prior to v8.0.0.<!--description--> <!--end release-notes-assistant--> ``` </details> <!--start release-notes-assistant--> ## Release notes <!--URL:https://codeberg.org/forgejo/forgejo--> - Breaking changes without a feature or bug label - [PR](https://codeberg.org/forgejo/forgejo/pulls/11098): <!--number 11098 --><!--line 0 --><!--description SW4gRm9yZ2VqbyB2OC4wLjAsIHRoZSBkZWZhdWx0IGxvY2F0aW9uIGZvciB0aGUgY29uZmlnIGZpbGUgd2FzIGNoYW5nZWQgZnJvbSBgL2V0Yy9naXRlYS9hcHAuaW5pYCB0byBgL3Zhci9saWIvZ2l0ZWEvYXBwLmluaWAuIEJhY2t3YXJkIGNvbXBhdGliaWxpdHkgbG9naWMgYW5kIHN0YXJ0dXAgd2FybmluZ3Mgd2VyZSBhZGRlZCB0byBjb250YWluZXIgc2V0dXAgYW5kIGVudHJ5cG9pbnQgc2NyaXB0cy4gTm93IHRoZXkgYXJlIHJlbW92ZWQuIFRoaXMgY2hhbmdlIG9ubHkgYWZmZWN0cyB0aG9zZSB1c2luZyBjb250YWluZXIgZGVwbG95bWVudHMgd2l0aCByb290bGVzcyBpbWFnZXMuIElmIHlvdSBoYXZlIHRoZSBjb25maWcgZmlsZSBzdG9yZWQgaW4gYSB2b2x1bWUgYm91bmQgdG8gY29udGFpbmVyJ3MgL2V0Yy9naXRlYSwgbW92ZSBpdCB0byB0aGUgbmV3IGxvY2F0aW9uIG9yIG92ZXJyaWRlIHRoZSBlbnZpcm9ubWVudCB2YXJpYWJsZSBgR0lURUFfQVBQX0lOSWAuIEFuIHVudXNlZCB2b2x1bWUgYC9ldGMvZ2l0ZWFgIGNhbiBiZSBzYWZlbHkgcmVtb3ZlZCBmcm9tIHRoZSBjb250YWluZXIgYWZ0ZXIgbW92aW5nIHRoZSBjb25maWcgb3IgaWYgdGhlIGRlcGxveW1lbnQgbmV2ZXIgdXNlZCB2ZXJzaW9ucyBwcmlvciB0byB2OC4wLjAu-->In Forgejo v8.0.0, the default location for the config file was changed from `/etc/gitea/app.ini` to `/var/lib/gitea/app.ini`. Backward compatibility logic and startup warnings were added to container setup and entrypoint scripts. Now they are removed. This change only affects those using container deployments with rootless images. If you have the config file stored in a volume bound to container's /etc/gitea, move it to the new location or override the environment variable `GITEA_APP_INI`. An unused volume `/etc/gitea` can be safely removed from the container after moving the config or if the deployment never used versions prior to v8.0.0.<!--description--> <!--end release-notes-assistant-->
Gusted approved these changes 2026-03-02 05:24:36 +01:00
0ko merged commit cce5f868ce into forgejo 2026-03-02 06:03:41 +01:00
jaylinski deleted branch rootless-image-remove-legacy-ini 2026-03-02 20:13:50 +01:00
Sign in to join this conversation.
Reviewers
No reviewers
viceice
0ko
Gusted
Labels
Clear labels   
arch
riscv64

Archived

  
backport/v1.19

Scheduled for backport to Forgejo v1.19

Archived

  
backport/v1.20

Scheduled for backport to Forgejo v1.20

Archived

  
backport/v1.21/forgejo

Scheduled for backport to Forgejo v1.21

Archived

  
backport/v10.0/forgejo

Automated backport to v10.0

Archived

  
backport/v11.0/forgejo

Automated backport to v11.0

  
backport/v12.0/forgejo

Automated backport to v12.0

Archived

  
backport/v13.0/forgejo

Automated backport to v13.0

Archived

  
backport/v14.0/forgejo

Automated backport to v14.0

  
backport/v7.0/forgejo

Scheduled for backport to Forgejo v7.0

Archived

  
backport/v8.0/forgejo

Scheduled for backport to Forgejo v8.0

Archived

  
backport/v9.0/forgejo

Scheduled for backport to Forgejo v9.0

Archived

  
breaking

The release containing this change is not backward compatible

  
bug

Something is not working

Archived

  
bug
confirmed
it can be reproduced

  
bug
duplicate
bug has already been reported in the Forgejo tracker

  
bug
needs-more-info
the information provided does not contain enough details

  
bug
new-report
bug has just been reported and need triage (default label on issue creation)

  
bug
reported-upstream
bug cannot be fixed within Forgejo easily, it has been reported upstream

  
code/actions

Forgejo Actions feature

  
code/api

API

  
code/auth

Forgejo Authentication

  
code/auth/faidp

Forgejo as Identity Provider (in OAuth/OIDC flow)

  
code/auth/farp

Forgejo as Relying Party / Client (in OAuth/OIDC flow)

  
code/email

Everything related to email in Forgejo

  
code/federation

Federation

  
code/git

Related to the Git backend in Forgejo

  
code/migrations

Migration between Git forges (i.e. for GitHub, GitLab, Gitea, Forgejo, etc.). NOT for database migrations.

  
code/packages

Forgejo package and container registry

  
code/wiki
  
database
MySQL
https://www.mysql.com/

  
database
PostgreSQL
https://www.postgresql.org/

  
database
SQLite
https://sqlite.org/

  
dependency-upgrade

https://codeberg.org/forgejo/forgejo/issues/2779

  
dependency
certmagic
github.com/caddyserver/certmagic

Archived

  
dependency
chart.js
https://github.com/chartjs/Chart.js

Archived

  
dependency
Chi
https://github.com/go-chi/chi/

Archived

  
dependency
Chroma
https://github.com/alecthomas/chroma/

Archived

  
dependency
citation.js
https://github.com/larsgw/citation.js/

Archived

  
dependency
codespell
https://github.com/codespell-project/codespell

Archived

  
dependency
css-loader
https://github.com/webpack-contrib/css-loader

Archived

  
dependency
devcontainers
https://github.com/devcontainers/cli

Archived

  
dependency
dropzone
https://github.com/dropzone/dropzone

Archived

  
dependency
editorconfig-checker
https://github.com/editorconfig-checker/editorconfig-checker

Archived

  
dependency
elasticsearch
https://www.elastic.co/elasticsearch

Archived

  
dependency
enmime
https://github.com/jhillyerd/enmime

Archived

  
dependency
F3
https://f3.forgefriends.org/

  
dependency
ForgeFed
https://forgefed.org

  
dependency
garage
https://git.deuxfleurs.fr/Deuxfleurs/garage

  
dependency
Git
https://git-scm.com/

Archived

  
dependency
git-backporting
https://github.com/kiegroup/git-backporting

Archived

  
dependency
Gitea
https://github.com/go-gitea/gitea

  
dependency
gitignore
https://github.com/github/gitignore

Archived

  
dependency
go-ap
https://github.com/go-ap/activitypub

Archived

  
dependency
go-enry
https://github.com/go-enry/go-enry

Archived

  
dependency
go-gitlab
https://github.com/xanzy/go-gitlab

Archived

  
dependency
Go-org
https://github.com/niklasfasching/go-org

Archived

  
dependency
go-rpmutils
https://github.com/sassoftware/go-rpmutils

Archived

  
dependency
go-sql-driver mysql
https://github.com/go-sql-driver/mysql/

Archived

  
dependency
go-swagger
github.com/go-swagger/go-swagger

Archived

  
dependency
go-version
https://github.com/hashicorp/go-version

Archived

  
dependency
go-webauthn
https://github.com/go-webauthn/webauthn

Archived

  
dependency
gocron
https://github.com/go-co-op/gocron

Archived

  
dependency
Golang
https://go.dev/

  
dependency
goldmark
https://github.com/yuin/goldmark

Archived

  
dependency
goquery
github.com/PuerkitoBio/goquery

Archived

  
dependency
Goth
https://github.com/markbates/goth/

Archived

  
dependency
grpc-go
https://github.com/grpc/grpc-go

Archived

  
dependency
happy-dom
https://github.com/capricorn86/happy-dom

Archived

  
dependency
Helm
https://helm.sh/

Archived

  
dependency
image-spec
https://github.com/opencontainers/image-spec

Archived

  
dependency
jsonschema
https://github.com/santhosh-tekuri/jsonschema

Archived

  
dependency
KaTeX
https://github.com/KaTeX/KaTeX

Archived

  
dependency
lint
All linting tools and libraries

Archived

  
dependency
MariaDB
https://mariadb.com/

Archived

  
dependency
Mermaid
https://github.com/mermaid-js/mermaid/

Archived

  
dependency
minio-go
https://github.com/minio/minio-go/

Archived

  
dependency
misspell
github.com/golangci/misspell/cmd/misspell

Archived

  
dependency
Monaco
https://github.com/microsoft/monaco-editor

Archived

  
dependency
PDFobject
https://pdfobject.com/

Archived

  
dependency
playwright
https://playwright.dev/

Archived

  
dependency
postcss
https://github.com/postcss/postcss

Archived

  
dependency
postcss-plugins
https://github.com/csstools/postcss-plugins

Archived

  
dependency
pprof
https://github.com/google/pprof

Archived

  
dependency
prometheus client_golang
https://github.com/prometheus/client_golang

Archived

  
dependency
protobuf
https://google.golang.org/protobuf

Archived

  
dependency
relative-time-element
https://github.com/github/relative-time-element

Archived

  
dependency
renovate
https://github.com/renovatebot/renovate

Archived

  
dependency
reply
https://code.forgejo.org/forgejo/reply

Archived

  
dependency
ssh
https://github.com/gliderlabs/ssh

Archived

  
dependency
swagger-ui
https://github.com/swagger-api/swagger-ui

Archived

  
dependency
tailwind
https://tailwindcss.com/

Archived

  
dependency
temporal-polyfill
https://github.com/fullcalendar/temporal-polyfill

Archived

  
dependency
terminal-to-html
github.com/buildkite/terminal-to-html

Archived

  
dependency
tests-only
Undifferentiated dependencies used for testing only

Archived

  
dependency
text-expander-element
https://github.com/github/text-expander-element

Archived

  
dependency
urfave
https://github.com/urfave/cli

Archived

  
dependency
vfsgen
https://github.com/lunny/vfsgen

Archived

  
dependency
vite
https://vitejs.dev/

Archived

  
dependency
Woodpecker CI
https://woodpecker-ci.org/

Archived

  
dependency
x tools
https://golang.org/x/tools

Archived

  
dependency
XORM
https://gitea.com/xorm/xorm

Archived

  
Discussion

   
duplicate

This issue or pull request already exists

  
enhancement/feature

New feature

  
forgejo/accessibility

Accessibility (a11y)

  
forgejo/branding

Branding (logo, name, tagline etc.)

  
forgejo/ci

Forgejo Actions CI configuration

  
forgejo/commit-graph

The commit graph feature and page.

  
forgejo/documentation

   
forgejo/furnace cleanup

Keeping Forgejo in sync with its dependencies and contributing back to them

Archived

  
forgejo/i18n

t9n/translation, l10n/localization, and i18n/internationalization of Forgejo

  
forgejo/interop

Interoperability with other services: Webhooks, bridges, integrations

  
forgejo/moderation

Moderation

  
forgejo/privacy

Privacy first

  
forgejo/release

Release management

  
forgejo/scaling

Performance and scaling

  
forgejo/security

Security (please disclose responsibly)

  
forgejo/ui

User interface

  
Gain
High
User research provides indicators that this would be good to have, interested contributors are encouraged to pick this.

  
Gain
Nice to have
This is likely worth having, but the assumption is not backed by user research data (it might benefit a small amount of users only.) Unlikely to receive much attention, but feel free to pick.

  
Gain
Undefined
Not enough information to assess the request's benefits. This issue may be closed if no gain is established: You can help by giving us more input.

  
Gain
Very High
User research indicates that this is an important improvement for Forgejo users. Contributions very welcome!

  
good first issue

Optimal for first-timers! Make sure to look for further explanations and ask for help if needed. If you want, you can consider the person who added this label as a point of contact.

  
i18n/backport-stable

This PR needs to be backported to stable branch of Forgejo safely and manually, using a migration script.

  
impact
large
Large impact: Potential data loss, many users affected, major degradation in UX.

  
impact
medium
Medium impact: Several users affected, degradation in UX, workarounds might be available but inconvenient.

  
impact
small
Small impact: No data loss, workarounds might be available, affects few users.

  
impact
unknown
Report was not yet triaged to assess impact.

  
Incompatible license

This pull request contains changes that are not (yet) compatible with the current Forgejo license

  
issue
closed
The issue was resolved in the repository of the dependency

  
issue
do-not-exist-yet
An issue should be created in the respository of the dependency

  
issue
open
An open issue exists in the upstream repository of the dependency

  
manual test

Pull requests that have been merged with a manual test

Archived

  
Manually tested during feature freeze

The manual test instructions were followed

  
OS
FreeBSD
Specific to the FreeBSD Operating System

  
OS
Linux
Specific to (GNU/)Linux Operating Systems

  
OS
macOS
Specific to the MacOS Operating System

  
OS
Windows
Specific to the Windows Operating System

  
problem

A user report about a problem. Needs to be triaged to find potential solutions.

  
QA

   
regression

found in the version of the milestone and not before

  
release blocker

Issues that must be fixed before the release can be published

  
Release Cycle
Feature Freeze
Only bug fixes with automated tests (except for CSS/JavaScript)

  
release-blocker
v7.0
Issues that must be fixed before Forgejo v7.0 can be released 17 April 2024

Archived

  
release-blocker
v7.0.1
Issues that must be fixed before Forgejo v7.0.1 can be released

Archived

  
release-blocker
v7.0.2
Issues that must be fixed before Forgejo v7.0.2 can be released

Archived

  
release-blocker
v7.0.3
Issues that must be fixed before Forgejo v7.0.3 can be released

Archived

  
release-blocker
v7.0.4
Issues that must be fixed before Forgejo v7.0.4 can be released

Archived

  
release-blocker
v8.0.0
Issues that must be fixed before Forgejo v8.0.0 can be released

Archived

  
release-blocker/v9.0.0

Issues that must be fixed before Forgejo v9.0.0 can be released

Archived

  
run-all-playwright-tests

Add this label to a PR to run all playwright tests manually.

  
run-end-to-end-tests

Trigger additional tests on the PR when it is ready to be merged

  
test
manual
manual testing has been documented

  
test
needed
test should be added

  
test
needs-help
help needed to add a test

  
test
not-needed
no additional test is needed

  
test
present
test has been added

  
untested

Pull requests that have been merged with no test and submitted as is to the dependency where they belong

Archived

  
User research - time-tracker

Time tracking feature for issues and the JS stopwatch.

  
valuable code

This PR was closed because the implementation is incomplete

  
worth a release-note

Add this PR to the release notes

  
User research - Accessibility

Requires input about accessibility features, likely involves user testing.

  
User research - Blocked

Do not pick as-is! We are happy if you can help, but please coordinate with ongoing redesign in this area.

  
User research - Community

Community features, such as discovering other people's work or otherwise feeling welcome on a Forgejo instance.

  
User research - Config (instance)

Instance-wide configuration, authentication and other admin-only needs.

  
User research - Errors

How to deal with errors in the application and write helpful error messages.

  
User research - Filters

How filter and search is being worked with.

  
User research - Future backlog

The issue might be inspiring for future design work.

  
User research - Git workflow

AGit, fork-based and new Git workflow, PR creation etc

  
User research - Labels

Active research about Labels

  
User research - Moderation

Moderation Featuers for Admins are undergoing active User Research

  
User research - Needs input

Use this label to let the User Research team know their input is requested.

  
User research - Notifications/Dashboard

Research on how users should know what to do next.

  
User research - Rendering

Text rendering, markup languages etc

  
User research - Repo creation

Active research about the New Repo dialog.

  
User research - Repo units

The repo sections, disabling them and the "Add more" button.

  
User research - Security

   
User research - Settings (in-app)

How to structure in-app settings in the future?

No labels
arch
riscv64
backport/v1.19
backport/v1.20
backport/v1.21/forgejo
backport/v10.0/forgejo
backport/v11.0/forgejo
backport/v12.0/forgejo
backport/v13.0/forgejo
backport/v14.0/forgejo
backport/v7.0/forgejo
backport/v8.0/forgejo
backport/v9.0/forgejo
breaking
bug
bug
confirmed
bug
duplicate
bug
needs-more-info
bug
new-report
bug
reported-upstream
code/actions
code/api
code/auth
code/auth/faidp
code/auth/farp
code/email
code/federation
code/git
code/migrations
code/packages
code/wiki
database
MySQL
database
PostgreSQL
database
SQLite
dependency-upgrade
dependency
certmagic
dependency
chart.js
dependency
Chi
dependency
Chroma
dependency
citation.js
dependency
codespell
dependency
css-loader
dependency
devcontainers
dependency
dropzone
dependency
editorconfig-checker
dependency
elasticsearch
dependency
enmime
dependency
F3
dependency
ForgeFed
dependency
garage
dependency
Git
dependency
git-backporting
dependency
Gitea
dependency
gitignore
dependency
go-ap
dependency
go-enry
dependency
go-gitlab
dependency
Go-org
dependency
go-rpmutils
dependency
go-sql-driver mysql
dependency
go-swagger
dependency
go-version
dependency
go-webauthn
dependency
gocron
dependency
Golang
dependency
goldmark
dependency
goquery
dependency
Goth
dependency
grpc-go
dependency
happy-dom
dependency
Helm
dependency
image-spec
dependency
jsonschema
dependency
KaTeX
dependency
lint
dependency
MariaDB
dependency
Mermaid
dependency
minio-go
dependency
misspell
dependency
Monaco
dependency
PDFobject
dependency
playwright
dependency
postcss
dependency
postcss-plugins
dependency
pprof
dependency
prometheus client_golang
dependency
protobuf
dependency
relative-time-element
dependency
renovate
dependency
reply
dependency
ssh
dependency
swagger-ui
dependency
tailwind
dependency
temporal-polyfill
dependency
terminal-to-html
dependency
tests-only
dependency
text-expander-element
dependency
urfave
dependency
vfsgen
dependency
vite
dependency
Woodpecker CI
dependency
x tools
dependency
XORM
Discussion
duplicate
enhancement/feature
forgejo/accessibility
forgejo/branding
forgejo/ci
forgejo/commit-graph
forgejo/documentation
forgejo/furnace cleanup
forgejo/i18n
forgejo/interop
forgejo/moderation
forgejo/privacy
forgejo/release
forgejo/scaling
forgejo/security
forgejo/ui
Gain
High
Gain
Nice to have
Gain
Undefined
Gain
Very High
good first issue
i18n/backport-stable
impact
large
impact
medium
impact
small
impact
unknown
Incompatible license
issue
closed
issue
do-not-exist-yet
issue
open
manual test
Manually tested during feature freeze
OS
FreeBSD
OS
Linux
OS
macOS
OS
Windows
problem
QA
regression
release blocker
Release Cycle
Feature Freeze
release-blocker
v7.0
release-blocker
v7.0.1
release-blocker
v7.0.2
release-blocker
v7.0.3
release-blocker
v7.0.4
release-blocker
v8.0.0
release-blocker/v9.0.0
run-all-playwright-tests
run-end-to-end-tests
test
manual
test
needed
test
needs-help
test
not-needed
test
present
untested
User research - time-tracker
valuable code
worth a release-note
User research - Accessibility
User research - Blocked
User research - Community
User research - Config (instance)
User research - Errors
User research - Filters
User research - Future backlog
User research - Git workflow
User research - Labels
User research - Moderation
User research - Needs input
User research - Notifications/Dashboard
User research - Rendering
User research - Repo creation
User research - Repo units
User research - Security
User research - Settings (in-app)
Milestone
Clear milestone
No items
No milestone
Forgejo v15.0.0
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
7 participants
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
forgejo/forgejo!11098
No description provided.