Event JSON
{
"id": "4289479aa9beab1d9b9e1a162c3aeeeef0347d3625761eb385060635ea048a04",
"pubkey": "6c79e5c5386ee1cbe5b80303c40f8d781831ef78b63ce76c726c3c0b47f622de",
"created_at": 1725711904,
"kind": 1,
"tags": [
[
"p",
"ab76f863533780a6d4b6dcbf6c249811207239e83a2a57094ecce5cf53bdbdd2"
],
[
"e",
"161b26c2b2da8bee495f37b664a10d7b49bbcca296be7596ad07381d04f22d1b",
"",
"root",
"ab76f863533780a6d4b6dcbf6c249811207239e83a2a57094ecce5cf53bdbdd2"
],
[
"proxy",
"https://mastodon.social/@mistersql/113096255360779481",
"web"
],
[
"proxy",
"https://mastodon.social/users/mistersql/statuses/113096255360779481",
"activitypub"
],
[
"L",
"pink.momostr"
],
[
"l",
"pink.momostr.activitypub:https://mastodon.social/users/mistersql/statuses/113096255360779481",
"pink.momostr"
],
[
"-"
]
],
"content": "Most automatic change log generators are using commit comments, which rarely are tidy enough to make a good log. I've been manually writing my change log and then validating it: https://pypi.org/project/keepachangelog/\n\nI like the idea of `scriv` and towncrier both solve the problem of many people attempting to edit a change log at the same time in git. My org doesn't dictate change log compilation, so I don't have that problem.\n\nReleases (in the sense of a zip + artifacts) depends on which CI you have",
"sig": "6e5110d347c0bac90303416cc83dd20598023e23e7566bd4ba9f1798016b3c4718d25ac2ea18eb1f9136aef86d7d5562f58105481fc46eac0b0276b8be218611"
}