Good question. Thanks for bringing this up.

The component notation in conventional commits (e.g. fix(component): bla) is not picked up by NX in order to assign changes to projects. The actual changes in git do. The component notation is used to distinguish between different parts within a project.

I think we should not squash the commits though, realizing just now as you question it. If we just merge this to main without squashing, and release everything unreleased, we will already have a version bump and changelog entry for wikibase triggered by this commit as well as a version bump and changelog entry for deploy triggered by this commit. I think this is ok. I will update the lint commit to follow conventional commits too though in order to not have unconventional commits on main.

I think after merging to main we should release wikibase and deploy, while the latter is the actual fix, the former is just to have the release on docker hub built by the latest build code.

@lorenjohnson if you agree with that procedure, I would just go ahead, merge and release.

That is fine, and I get it. I would just prefer feat(): format in our conventional commit messages for consistency and clarity when perusing at the git log level. Don't care a bunch though, it is just what I had thought we had done fairly consistently to this point.