chore: automatically increment version in package.json on new release

[divinetettey]

This PR attempts to resolve this issue Automatically increment version in package.json on new release 📦 . The PR aims at automating the update off the version in pacakge.json

1. A new step has been added to extract the version number from the draft release. this version number is then used in subsequent steps to update the package.json
2. The extracted version number is used to update the package.json,package-lock.json and the docusaurus.config.js
3. after update the update a commit is pushed back to the repository

[linux-foundation-easycla]

The committers listed above are authorized under a signed CLA.

• ✅ login: divinecodes / name: Divine Tettey (a3e29e0)
• ✅ login: JamieSlome / name: Jamie Slome (778c12f, 7fbc690, e4b400d, a69cdde, 9d9db92, 6b86691)
• ✅ login: divinetettey / name: Divine Sedem Tettey (499969a, 663e030, 0be28b9, bbf6e0f, 54a7efe, 3e29af9, 3cb7cd5, cae8f79, d6bcfa4, c357671, 111457f, 5f26b95, b7b8a11, 1027f2e, 3ef3465)

[netlify]

✅ Deploy Preview for endearing-brigadeiros-63f9d0 canceled.

Name	Link
🔨 Latest commit	54a7efe
🔍 Latest deploy log	https://app.netlify.com/sites/endearing-brigadeiros-63f9d0/deploys/66633207a7d8a5000830adc6

[netlify]

✅ Deploy Preview for endearing-brigadeiros-63f9d0 canceled.

Name	Link
🔨 Latest commit	6b86691
🔍 Latest deploy log	https://app.netlify.com/sites/endearing-brigadeiros-63f9d0/deploys/66fd617d02b9890008718bf3

[JamieSlome]

Thanks for the PR, @divinetettey 👍 Is there anyway we can update the package.json and package-lock.json version before we run the release? i.e. include the latest version number in the actual release itself

[divinetettey]

Thanks for the PR, @divinetettey 👍 Is there anyway we can update the package.json and package-lock.json version before we run the release? i.e. include the latest version number in the actual release itself

sure, let me take a look at this

[divinetettey]

Thanks for the PR, @divinetettey 👍 Is there anyway we can update the package.json and package-lock.json version before we run the release? i.e. include the latest version number in the actual release itself

sure, let me take a look at this

should this run before/after the release-drafter

[JamieSlome]

@divinetettey - we want the file bumps to occur before we make the NPM and GitHub releases. This is to ensure that the releases themselves include the correct version number.

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 57.39%. Comparing base (3b6cb6b) to head (6b86691).

Additional details and impacted files

@@           Coverage Diff           @@
##             main     #596   +/-   ##
=======================================
  Coverage   57.39%   57.39%           
=======================================
  Files          46       46           
  Lines        1582     1582           
=======================================
  Hits          908      908           
  Misses        674      674           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[JamieSlome]

@divinetettey, the @divinecodes will also need to authorise with EasyCLA to merge this pull request (heads up).

[divinetettey]

@divinetettey, the @divinecodes will also need to authorise with EasyCLA to merge this pull request (heads up).

yeah, my gitconfigs got messed and the commit was pushed with my personal account. I am going to squash the commit and push it with @divinetettey

[JamieSlome]

Happy from my end. @divinetettey - have you been able to test the update_version step?

[divinetettey]

Happy from my end. @divinetettey - have you been able to test the update_version step?

Yes, getting some failures with release-drafter, taking a look

[divinetettey]

Happy from my end. @divinetettey - have you been able to test the update_version step?

all good on my end