7.3: Changing release cadence to .x0 patches; Removal of pendingFields and pendingName

[WorkingRobot]

1. It seems that my idea of making breaking changes at the first of every month was not the best idea, so I'll be changing this to only happen on major patch update days. I'll see if I can automate this somehow.

• Is there even a point to making 'releases'? You should ideally be pinning by commit if you're worried about breaking changes. I'll be doing so with Lumina.Excel (with the exception of the Experimental namespace).

2. I think my current implementation of backwards compatible changes is just flawed, so I'll be removing the pending fields effective 7.3.
3. In addition to these changes, as mentioned in the README, all branches containing no column changes will be removed. If you require schemas for versions that don't have a branch, you'll need to find the earliest (by version) branch that matches your version. Luckily, I believe this can be done via a simple lexicographical compare.

All in all, 1 and 2 should greatly simplify version tracking processes. Changing the release cadence to major patches allows consumers (see: Dalamud, XIVAPI?) to only require making breaking changes when other parts of their systems would also require changes. I've also planned to remove pending fields since they seem to be at conflict with the idea of making breaking changes when you should be pinning by commit hash (see the bullet point above).

Please let me know if you have any concerns or comments, I don't want to drop these changes on top of anyone unaware.

[mattantonelli]

Is there even a point to making 'releases'?

Releases can still serve as a convenient notification to let people know when the schema has been updated on patch days.

[NotNite]

Is there even a point to making 'releases'?

I think releases can also be useful for all the things added between .X0 breaking changes, like how Occult Crescent (and thus its sheet data) was added in 7.25.

[WorkingRobot]

Yeah, that is a fair point; and all consumers can decide when they want to update