Version 1.2.3 Release

Changelog:

• Fixed #24, which caused lifted bans from TGMC to appear as active

Version v1.2.2 Release

Changelog:

• Added BuildBundlerMinifier to properly minify CSS assets
• Updated several packages to latest

Version v1.2.1 Release

Changelog:

• Hotfix for minification of CSS assets

Version v1.2.0 Release

Changelog:

• Added a built-in viewer to the API project, allows for viewing of ban entries in a reasonable interface.

Version v1.1.0 Release

Changelog:

• Added attributes to bans, which allows for individual ban sources to tag specific strings onto their bans. (Closes #19)
• Fixed bug in finding newest bans for a source which could result in an infinite loop.

Version v1.0.7 Release

Changelog:

• Removed IP and CID from bans (Resolves #16)
• Updated Fulp to be MRP by default
• Fixed absolute path for XML documentation (Fixes #17)
• Fixed error in logic for getting active bans from API (#14 / #15)

Version v1.0.6 Release

Changelog:

• Added TGMC bans (Closes #12)
• Improved handling of equality for EFCore entities, removed use of IEquatable in favor of isolated IEqualityComparers
• Added support for detecting and updating changed job bans
• Minor refactor of how jobs are added to bans to prevent code duplication and improve maintainability

CentCom requires .NET 3.1 runtimes to run.

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.