ChillerDragon
f6955fbc5b
fix: conventional commit release messages
2023-07-13 13:00:44 +02:00
ChillerDragon
6c158c8841
Suggest minor bump on breaking changes
...
https://www.conventionalcommits.org/en/v1.0.0/
closed #11
2023-06-01 11:03:08 +02:00
ChillerDragon
a11a3cbb42
Switch back to setup.cfg in release script
2023-04-07 09:27:49 +02:00
ChillerDragon
d8790e94f4
Could also run python -m venv venv in CI
2023-04-06 19:43:29 +02:00
ChillerDragon
674e40c286
Ensure release passes all tests
2023-04-06 19:12:17 +02:00
ChillerDragon
2cbc3671bd
Stricter release testing in venv
...
https://gitlab.com/teeworlds-network/twnet_parser/-/issues/3
2023-04-06 19:07:41 +02:00
ChillerDragon
ccbc15d230
Move setup.cfg into pyproject.toml
2023-04-06 18:15:08 +02:00
ChillerDragon
78ea668487
Build twice to avoid having dirty working tree
...
Makes debugging build issues much more fun
2023-04-06 17:56:25 +02:00
ChillerDragon
bffa9f70cb
Warn about open todos on major release
...
During this early development I love hacking down
half finished unpolished code with open todos
and then mark them with a TODO comment
Then at some later point I might forget how everything
is held together by duck tape and do a 1.0.0 release
This check in the release script should avoid this mistake
and ensure that the 1.x.x and all other major releases
are what they claim to be: a finished, polished and working version
2023-04-02 19:37:27 +02:00
ChillerDragon
845845b7b9
Some more semver thoughts
2023-03-19 11:41:49 +01:00
ChillerDragon
a58ae3aaca
Some changelog helpers
2023-03-18 10:29:28 +01:00
ChillerDragon
2ca10fc4f5
drunk devs
2023-03-18 10:09:24 +01:00
ChillerDragon
ba12559348
Nicer release script format
2023-03-18 10:07:51 +01:00
ChillerDragon
03efdeba83
Thoughts about semver
2023-03-18 10:01:24 +01:00
ChillerDragon
54f0f8cb7c
Push commit & tag and check branch in release script
2023-03-16 16:59:59 +01:00
ChillerDragon
18f5c146b4
Overengineer release script
2023-03-16 16:51:57 +01:00
ChillerDragon