feat: allow configuring simple strategy version file

[chingor13]

Fixes #921

[goatwu1993]

Please ignore. Off topic.

Any chance simple strategy to take a list of string and use ["version.txt"] as default values?

[bcoe]

Thinking outloud, could the versionFile be a JSON file, and if so we take a key to update?

[axieum]

Perhaps the generic updaters (#1157) could take a replacement method, e.g.

{
  "extra-files": [
    {
      "path": "version.json",
      "method": "regex",
      "version": ["\"version\": \"(.+?)\""], // arg for full version
      "minor": ["\"minor\": \"(.+?)\""] // arg for minor, can add more for major, patch, build, etc.
    },
    {
      "path": "some.txt",
      "method": "annotation" // optional/default
    },
    {
      "path": "other.json",
      "method": "json",
      "major": "version.items[2].major" // arg for major
  ]
}

I'm not sure how this would be set on the CLI though if wanting to allow configuration through that as well?

[chingor13]

Perhaps the generic updaters (#1157) could take a replacement method, e.g.

{
  "extra-files": [
    {
      "path": "version.json",
      "method": "regex",
      "version": ["\"version\": \"(.+?)\""], // arg for full version
      "minor": ["\"minor\": \"(.+?)\""] // arg for minor, can add more for major, patch, build, etc.
    },
    {
      "path": "some.txt",
      "method": "annotation" // optional/default
    },
    {
      "path": "other.json",
      "method": "json",
      "major": "version.items[2].major" // arg for major
  ]
}

I'm not sure how this would be set on the CLI though if wanting to allow configuration through that as well?

Thinking outloud, could the versionFile be a JSON file, and if so we take a key to update?

I think the issue both of you are describing is more related to #1180 than this fix. The versionFile here is a simple text file that only contains the version number.

[bcoe]

nice 🥳

Is it worth adding a test that we default to version.txt?