Docs fixes and release notes post for 1.6

[danuw]

Pull Request

Issue Number: (Link to Github Issue or Azure Dev Ops Task/Story)

Summary

Fix for the release where docs workflow fails

Changes

• List of comprehensive changes

Checklist

• Local Tests Passing?
• CICD and Pipeline Tests Passing?
• Added any new Tests?
• Documentation Updates Made?
• Are there any API Changes? If yes, please describe below.
• This is not a breaking change. If it is, please describe it below.

Are there API Changes?

If yes, what are the expected API Changes? Please link to an API-Comparison
workflow with the API Diff.

Is this a breaking change?

If yes, what workflow does this break?

Anything else?

Other comments, collaborators, etc.

Please follow
GitHub's suggested syntax
to link Pull Requests to Issues via keywords

This PR Closes #<issue_number>

[danuw]

Workflow fails again.

FYI
My local uses

node -v
v20.9.0
npm -v
10.8.2

and docusaurus is 3.4.0 (as it is telling me to update to 3.5.2)

[danuw]

we probably need to freeze the dependencies into a yarn lock which we dont yet have to see if that helps secure a steady set of dependencies for docusaurus to work seemlessly.

[tiwatsuka]

@danuw
I succeeded to build the docs with changing versions of the libraries.
tiwatsuka@8173906
https://github.com/tiwatsuka/carbon-aware-sdk/actions/runs/11010398839/job/30572233520

Could you generate yarn.lock by running yarn install on your local machine without --frozen-lockfile option and commit it to the repository? I suppose package-lock.json is no longer needed as long as we use yarn to build.

[tiwatsuka]

@danuw My apologies for the lack of clarity. You also need to apply the change I made below before generate yarn.lock.
tiwatsuka@8173906

[danuw]

Thank you very much I was creating a new test folder to get just that - thank you

[danuw]

@tiwatsuka / @YaSuenag could you review and approve please? and I hope do the same for the main branch too please?

[danuw]

Thank you @YaSuenag