maxlath

thanks! Any particular reason made you try to upgrade commander?

I'm curious now (as I tried to look into packaging wikibase-cli for debian but gave up), how do you install it? Do you have a deb repo installing each dependencies...

would you be up for documenting the process or pointing to some resource where that's documented? It could be added to the installation options

I haven't looked at FederatedProperties yet, I guess some adaptation would be required in `wikibase-edit` to support it: I opened an issue on that matter https://github.com/maxlath/wikibase-edit/issues/75

as I see it: - OAuth would be an improvement as it would lower the power of the credentials we have to handle, but we would still have credentials supposedly...

OAuth authentification is now possible (and recommanded!) in `wikibase-cli >= v8` \o/ see [config documentation](https://github.com/maxlath/wikibase-cli/blob/master/docs/config.md)

what about having a `--config` parameter instead, to force alternative config resolution? ```sh wb somecmd --config ./path/to/wb.config.a.json wb somecmd --config ./path/to/wb.config.b.json ```

that could work well with aliases ```sh alias wda="wd --config ~/.config/wikibase-cli/config.a.json" alias wdb="wd --config ~/.config/wikibase-cli/config.b.json" wda set-label Q4115189 en foo ```

or we could look for the `WB_CONFIG` [environment variable, like we already do for `WB_INSTANCE` and others](https://github.com/maxlath/wikibase-cli/blob/master/docs/config.md#environment-variables)

the uniqueness requirements of a property could actually be pulled from the properties constraints (ex: [P268 constraints](https://www.wikidata.org/wiki/Property:P268#P2302)); we could default to applying the property constraints and having a flag to...