When conducting a regular review of our app dependencies as part of our normal development workflow, we noted that a new version of @atlassian/atlassian-connect-express was available on NPM.
Our app currently uses version 11.5.3.
The latest version on npm is 11.6.0.
However the release notes only go up to 11.5.3.
Furthermore, looking at the commit history, it appears that 11.6.0 is not the only new version. There have also been interim 11.5.4 and 11.5.5 versions, neither or which are included in the release notes.
The last unscoped package (atlassian-connect-express) version was 11.5.3, so is it possible that as part of moving to scoped packages, the process changed and the RELEASENOTES.md file is not being automatically updated when a new version is published?
(Also worth noting that corresponding git tags for these versions don’t seem to exist either, if that means anything.)
As I’m sure you will appreciate, when upgrading a core dependency as fundamental as ACE, we need a clear understanding of exactly what is new/changed in the update so that we can plan & test accordingly.
It would be greatly appreciated if the team that owns the ACE repo could ensure that release notes are kept up to date.
Thank you.