Wrong version in the 1.0.0 packaged releases

[k2niner]

Releases here: https://github.com/ocsf/ocsf-schema/releases/tag/v1.0.0

contain the following version.json:

{
  "version": "1.0.0-rc.3"
}

[mikeradka]

Nice catch here, @k2niner. Thanks for bringing it up in our sync yesterday. I don't think it is breaking for the creation of OCSF documents, but it may cause an issue when building a v1 server and could theoretically cause downstream issues for anyone utilizing that file.

@rmouritzen-splunk I looked at this a little bit, but am unsure of the best course of action. Since a tag is just a commit, I don't think it is as easy as just updating the version. If i understand, this could be immutable.

[mikeradka]

I looked at this once more. Perhaps there is still a way to approach this. Since there is also a v1 branch, and the v1 branch indeed has the correct version.json - I think we may be able to simply cut a fresh- v1.0.0 release from the v1.0.0 branch, and delete the old v1 tagged release.

We can try out a diff between the v1 branch and v1 tagged release - if this is the only difference, then I think we will be safe to delete the old v1 tagged commit and create a new one from the v1 branch.

[mikeradka]

Update: Looks like there are only two very small non-breaking changes between this build - an attribute description, and the update of the version from rc3 to v1.0.0.

For reference, this is the commit from where the old inaccurate release was cut: 6f73e0e

Here is the commit from which I created an accurate v1.0.0 release: 9608805

[mikeradka]

The v1 release has been tested, verified, and updated. Here is the link: https://github.com/ocsf/ocsf-schema/releases/tag/v1.0.0