Add notice for supported Forgejo version #163

noxifoxi commented 2026年07月13日 11:56:20 +02:00

Hey,
Today, I encountered some issues when trying to use version 0.11.0 of this crate on my Forgejo 15.0.4 instance.

I suggest adding a notice to the readme file indicating which Forgejo versions are compatible with the current crate version, as there is no obvious information about this at the moment.

Hey, Today, I encountered some issues when trying to use version 0.11.0 of this crate on my Forgejo 15.0.4 instance. I suggest adding a notice to the readme file indicating which Forgejo versions are compatible with the current crate version, as there is no obvious information about this at the moment.

Fluffinity commented 2026年07月13日 13:04:28 +02:00

Can you describe the concrete issues you encountered? Just so I have a clearer idea what is going on

Can you describe the concrete issues you encountered? Just so I have a clearer idea what is going on

Fluffinity commented 2026年07月13日 13:14:53 +02:00

Ok, nvm. I think the best path forward is, as you mentioned, to just state the single Forgejo version, that the current version of the crate supports. We should make it clear, that essentially every new version of the crate supporting a new Forgejo version presents a breaking change. Users should only update the crate if they want to migrate to a new Forgejo version. forgejo-apijust isn't built to support multiple Forgejo versions simultaneously and backwards compatibility only goes as far as Forgejo itself delivers it

Ok, nvm. I think the best path forward is, as you mentioned, to just state the single Forgejo version, that the current version of the crate supports. We should make it clear, that essentially every new version of the crate supporting a new Forgejo version presents a breaking change. Users should only update the crate if they want to migrate to a new Forgejo version. `forgejo-api`just isn't built to support multiple Forgejo versions simultaneously and backwards compatibility only goes as far as Forgejo itself delivers it

Fluffinity commented 2026年07月13日 13:17:16 +02:00

I recommend checking out the Forgejo repo itself and potentially report your issues there, in case they aren't documented

I recommend checking out the [Forgejo repo itself](https://codeberg.org/forgejo/forgejo) and potentially report your issues there, in case they aren't documented

Cyborus commented 2026年07月13日 17:46:31 +02:00

I'm still curious exactly what the problem is, though. I'm aware of a problem where the crate doesn't deserialize missing fields properly, so any added fields break when interfacing with an older forgejo instance.

I'm still curious exactly what the problem is, though. I'm aware of a problem where the crate doesn't deserialize missing fields properly, so any added fields break when interfacing with an older forgejo instance.

dmoonfire commented 2026年07月13日 18:23:30 +02:00

Is there a chance of being able to use the /api/v1/nodeinfo to do a version check against the library? Even an optional one that could be there which would give a useful message?

Is there a chance of being able to use the `/api/v1/nodeinfo` to do a version check against the library? Even an optional one that could be there which would give a useful message?