Start maintaining a CHANGELOG.md

[Guzz-T]

The changelog should be expanded bit by bit.

[github-actions]

Coverage Report

File	Stmts	Miss	Cover	Missing
luxtronik
__main__.py	25	25	0%	3–66
collections.py	125	1	99%	304
datatypes.py	412	2	99%	61, 133
discover.py	58	1	98%	63
luxtronik/cfi
interface.py	168	13	92%	80–93, 243–244, 249
luxtronik/definitions
__init__.py	237	1	99%	172
luxtronik/scripts
__init__.py	35	5	86%	7–16, 51
discover_shi.py	60	60	0%	8–98
dump_cfi.py	14	6	57%	18–25, 29
dump_shi.py	15	6	60%	21–28, 32
performance_shi.py	63	63	0%	7–89
update_screen.py	105	82	22%	6, 20–41, 46–48, 51–61, 64, 70–75, 78, 81–85, 88–92, 95–97, 100–103, 106–111, 115–116, 119–126, 129–136
watch_cfi.py	32	16	50%	36–47, 50–56, 60
watch_shi.py	33	16	52%	38–49, 52–58, 62
luxtronik/shi
contiguous.py	121	2	98%	224–225
TOTAL	2429	299	88%

Tests	Skipped	Failures	Errors	Time
381	0 💤	0 ❌	0 🔥	36.034s ⏱️

[kbabioch]

Do we want / need to enforce this? When should an entry be made to the changelog? Along with the commit / PR that introduces a change?

[Guzz-T]

Whenever there is a noteworthy change for the user. It is best to mention the change right away in the PR.