Skip to content

Releases: hitblast/IgKnite

2025.3.3

03 Mar 12:12
@hitblast hitblast
2025.3.3
This tag was signed with the committer’s verified signature.
hitblast HitBlast
SSH Key Fingerprint: fc9q4k1Dxnnq8aEicht7V5me7Ajcqu0P3dOW+Gr2U2Y
Verified
Learn about vigilant mode.
ff300fc
This commit was signed with the committer’s verified signature.
hitblast HitBlast
SSH Key Fingerprint: fc9q4k1Dxnnq8aEicht7V5me7Ajcqu0P3dOW+Gr2U2Y
Verified
Learn about vigilant mode.
Compare
Choose a tag to compare
2025.3.3 Latest
Latest

🔨 Bug Fixes

  • Fixed a SyncWarning at bot startup which was caused due to improper interaction context type assignments.

Additional release material such as the full Docker image build will be available in the GitHub Packages section shortly.

Full Changelog: 2025.2.28...2025.3.3

Assets 2
Loading

2025.2.28

28 Feb 14:29
@hitblast hitblast
2025.2.28
This tag was signed with the committer’s verified signature.
hitblast HitBlast
SSH Key Fingerprint: fc9q4k1Dxnnq8aEicht7V5me7Ajcqu0P3dOW+Gr2U2Y
Verified
Learn about vigilant mode.
be84738
This commit was signed with the committer’s verified signature.
hitblast HitBlast
SSH Key Fingerprint: fc9q4k1Dxnnq8aEicht7V5me7Ajcqu0P3dOW+Gr2U2Y
Verified
Learn about vigilant mode.
Compare
Choose a tag to compare
2025.2.28

🎉 (Technically) First Release

After the initial launch back in 2022, IgKnite had grown into a community-driven project by heart. However, a few recent incidents regarding organization shifts have resulted in total star count loss for this project.

Hopefully this release will be a major part for a more stable development path for IgKnite. That being said, stay tuned for future releases!

Loading