ACVM changelogs in release PRs accrue instead of start fresh on new versions

[Savio-Sou]

Aim

Reading ACVM changelogs to learn what is new in new versions.

Expected Behavior

Changelogs should capture new changes in each new version, instead of accumulative changes across versions.

Bug

ACVM changelogs currently accumulate across versions in release PRs.

For example:

• 0.42.0: chore: Release Noir(0.26.0) #4526
• 0.43.0: chore: Release Noir(0.27.0) #4632
• Difference: https://www.diffchecker.com/eLBiTPXI/

Project Impact

Nice-to-have

Impact Context

Fixing it could make developers' lives checking and working with ACVM changes easier.

Additional Context

The changelogs aren't formally published anywhere today, so the number of developers this Issue currently affects is likely limited.

Growing interest in integrating different proving backends with ACIR could drive up impact of this Issue.

Would you like to submit a PR for this Issue?

None

Support Needs

No response

[TomAFrench]

Duplicate of #3604