2022-May-23 - Prerelease - 2.6.789

Bump jdbiVersion from 3.28.0 to 3.29.0 (#10495)

Bumps `jdbiVersion` from 3.28.0 to 3.29.0.

Updates `jdbi3-core` from 3.28.0 to 3.29.0
- [Release notes](https://github.com/jdbi/jdbi/releases)
- [Changelog](https://github.com/jdbi/jdbi/blob/master/RELEASE_NOTES.md)
- [Commits](https://github.com/jdbi/jdbi/compare/v3.28.0...v3.29.0)

Updates `jdbi3-sqlobject` from 3.28.0 to 3.29.0
- [Release notes](https://github.com/jdbi/jdbi/releases)
- [Changelog](https://github.com/jdbi/jdbi/blob/master/RELEASE_NOTES.md)
- [Commits](https://github.com/jdbi/jdbi/compare/v3.28.0...v3.29.0)

---
updated-dependencies:
- dependency-name: org.jdbi:jdbi3-core
  dependency-type: direct:production
  update-type: version-update:semver-minor
- dependency-name: org.jdbi:jdbi3-sqlobject
  dependency-type: direct:production
  update-type: version-update:semver-minor
...

Signed-off-by: dependabot[bot] <[email protected]>

Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>

2022-May-23 - Prerelease - 2.6.788

Fix history errors when seeking through history. (#10494)

Fix history errors when seeking through history. Unfortunately, my fix for #10429, which fixed history errors on Imperialism 1974, introduced a different bug where seeking back in time in history would cause errors.

This is because the "last change" of a Node that's not a leaf is not always consistent, since more child nodes get added to it over time, and thus seeking to such a node and then later seeking away from it would result in an inconsistent sequence of changes.

This PR reworks the History class to explicitly keep track of the change index we're past, instead of the tree node (whose last change index may change), which fixes the problem. There is no problem with serialization because the History class uses writeReplace() (i.e. serializing a different object in its place) and the properties being changed are only relevant for the History object in "seek mode", which is never serialized (it's on a copy of the game data).

Tested by playing Feudal Japan Warlords 5 players with all-AIs and moving around history nodes while it's advancing. Before this change, an error dialog about trying to remove non-existent units would be encountered.

2022-May-23 - Prerelease - 2.6.787

Make ChangeAttachmentChanges save a copy of the previous value. (#10483)

Make ChangeAttachmentChanges save a copy of the previous value of the property.

The previous value is used when inverting the change (e.g. when going back in history and reverting changes). By copying the properties, this fixes several issues:

* Ensuring that the inverted change is actually correct, as we don't want to be reverting to a "live view" of the current state.
* Fixing exceptions caused by my recent change where property getters return unmodifiable collections (we don't want to set the property to an unmodifiable collection, since future changes will fail).

Additionally, switches to improved syntax for some locking in a few related places and some small clean ups.

2022-May-23 - Prerelease - 2.6.786

Remove an unused method only referenced by tests. (#10492)

* Remove an unused method only referenced by tests.

* Remove imports.

2022-May-22 - Prerelease - 2.6.785

Clean up some code in HistoryPanel. No logic changes. (#10482)

2022-May-21 - Prerelease - 2.6.784

Remove unneeded copies done by CollectionUtils. (#10474)

* Remove unneeded copies done by CollectionUtils.

* Formatting.

2022-May-21 - Prerelease - 2.6.783

Introduce a cleaner pattern for locking GameData. (#10481)

2022-May-21 - Prerelease - 2.6.782

Fix issue with tooltips where they may appear while TripleA is in the…

2022-May-20 - Prerelease - 2.6.781

Fix game history and add Options class specifying what to include. (#…

2022-May-19 - Prerelease - 2.6.780

WW2 V3 Build Caps & Upkeep (#10465)

Added WW2 V3 Build Caps & Upkeep