CVE Binary Tool Release Notes page hasn't been updated for v3.3 and now v3.4 was just made

[tzirn]

Description

The CVE Binary Tool Release Notes page wasn't updated for v3.3 and now v3.4 has been released.

To reproduce

Steps to reproduce the behavior:

1. go to https://cve-bin-tool.readthedocs.io/en/latest/RELEASE.html
2. see the last version to be documented is v3.2

Expected behavior: that v3.3 release would have been documented
Actual behavior: release notes are missing for v3.3 ( and please also add in v3.4 now)

Version/platform info

N/A

Anything else?

I was asked to do some v3.4r* preliminary testing and found the options/parameters were changed since v3.3 so please make sure when the documentation is updated for 3.4 that the change in parameter/options for the tool command are documented and also the fact that with the move to *.json triage files -previous users can just copy their *.vex triage file to *.json and it will work.
Thanks so much!

[tzirn]

This is the manual that needs updating https://cve-bin-tool.readthedocs.io/en/latest/MANUAL.html

[terriko]

The release notes thing is manually done and has always lagged months (or years) behind what's in github's releases list. I"m not even sure if I should maintain it or remove it or automate it.

I'm going to mark this as a good first issue since someone just needs to cut/paste stuff over into the release notes file.

If anyone wants a more exciting task, we could use some automation so what's in the release notes gets copied into the appropriate file (preferably not just during release, but during any update.)

[uday-rana]

I'd like to try this.

[tzirn]

I'd like to try this.

Thanks! any chance that includes updating the user manual too? :-)

[uday-rana]

I'd like to try this.

Thanks! any chance that includes updating the user manual too? :-)

Sure, what exactly would you like me to update? As far as I can tell it's been updated for v3.4. #4443

[tzirn]

@uday-rana looks like the user manual was updated right after I had last loaded the page. The parameters that were changed are now updated.
Thank you for taking on the release notes for the 3.3 and 3.4 version as it will be important that these release notes list that 3.4 changed the parameters AND that vex input files aren't supported anymore but can just be copied to *.json and still used. 4421 notes the loss of *.vex file usage.