Version v1.0.5 Release

Changelog:

• Added Fulp ban parsing (Closes #9)
• Added unit tests for bans, job bans, and ckey parsing
• Ensured ckeys were properly parsed for all three possible locations in Ban objects
• Fixed bug with comparing JobBan objects (Closes #8)
• Fixed bug with comparing Ban objects with JobBans (Closes #8)
• Fixed bug with comparing Ban objects with IPAddresses (Closes #8)
• Ensured all timestamps being sent to DB are stored as UTC
• Version bump to v1.0.5
• Fixed JSON encoding for JobBan, Ban, and BanSource objects

CentCom requires .NET 3.1 runtimes to run.

Version v1.0.4 Release

• Flat format ban data has been refactored to include versioning and the ability to update a server's version of that data automatically. (Closes #1)
• The API server will now return bans in descending order of the banned_on datetime value (Closes #2)

Running CentCom requires .NET Core 3.1 runtimes.

Version v1.0.3 Release

• Updated Postgres configuration such that the generated database objects will now use proper camel casing.

If you previous had a Postgres instance, you will need to manually rename _EFCoreMigationsHistory's columns to migration_id and product_version respectively, though I suspect this doesn't effect anyone. Anyone setting up new Postgres instances will have no issues.

CentCom requires .NET Core 3.1 runtimes.

Version v1.0.2 Release

• Deleting a BanSource will now cascade to the associated bans
• Fixed typo labeling /vg/ as yogstation in logging

Requires .NET Core 3.1 runtimes

Version v1.0.0 Release

Initial functional release of the CentCom software suite. Expect instability, but it has been fine in testing.

Requires .NET Core 3.1 runtimes.

Version v1.0.1 Release

Updated the OracleStation flat data to remove expiration datetimes for bans which are permanent, this was an artifact of how they were storing this data in their database.

This will require anyone who previously ran v1.0.0 on their database to remove the OracleStation bansource from their database and associated bans to allow for re-insertion of that dataset.

Requires .NET Core 3.1 runtimes