ci: automate version bumps in module README.md files

[matifali]

closes #138

[mafredri]

One improvement suggestion, but otherwise looks good.

One thing to observe here is that a module can go e.g. from v1.0.0 to v1.5.2 in the blink of an eye since we're always bumping them by the coder/modules tag.

We shouldn't fix it in this PR, but eventually it could be nice for them to have their own versions.

[matifali]

@mafredri, is it possible for each module to have its own versions, given our current setup?

[mafredri]

@mafredri, is it possible for each module to have its own versions, given our current setup?

Kinda, maybe? Each folder could have its own VERSION file, and it could be incremented based on the change in coder/modules.

Example:

1. coder/modules v1.5.0 -> v1.5.1
2. vscode-web/VERSION v1.3.0 -> v1.3.1

Example 2:

1. coder/modules v1.5.1 -> v1.6.0
2. vscode-web/VERSION v1.3.1 -> v1.4.0

Perhaps not as ideal as controlling each module individually, but could be an option ¯\_(ツ)_/¯.

[matifali]

@mafredri, but our registry API needs to be changed then, currently, it is based on tags.

[mafredri]

@mafredri, but our registry API needs to be changed then, currently, it is based on tags.

Don't think it would be a huge effort to do that, if we get some others on board of this being a good idea. Alternatively we can continue using tags but prefix them, like vscode-web-v1.4.0. I bet that would also require some small change to the registry.

[matifali]

Let's see what @bpmct thinks about this?