Release 1.3 changelog

[danuw]

Pull Request

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

Summary

Release 1.3 changelog

Changes

• Updated changelog for release 1.3

Checklist

• Local Tests Passing?
• CICD and Pipeline Tests Passing?
• Documentation Updates Made?
• This is not a breaking change. If it is, please describe it below.

Are there API Changes?

No

Is this a breaking change?

No

Anything else?

Other comments, collaborators, etc.

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

This PR Closes #474

[danuw]

I have used the following commands to help me create the release notes

gh pr list -R Green-Software-Foundation/carbon-aware-sdk --search "label:1.3 is:closed" --json number,title,url --template \
        '{{range .}}{{ printf "\n-[PR #%v" .number | autocolor "green"}} {{.title}} {{ printf "](%v)" .url}}{{end}}'

gh issue list -R Green-Software-Foundation/carbon-aware-sdk --search "label:1.3 is:closed" --json number,title,url --template \
        '{{range .}}{{ printf "\n-[#%v" .number | autocolor "green"}} {{.title}} {{ printf "](%v)" .url}}{{end}}'

This based on tags, but we could also use per date to match all changes such as using criteria like closed:>=2024-01-17 such as

gh pr list -R Green-Software-Foundation/carbon-aware-sdk --search "-label:agenda closed:>=2024-01-17" --json number,title,url --template \
        '{{range .}}{{ printf "\n-[PR #%v" .number | autocolor "green"}} {{.title}} {{ printf "](%v)" .url}}{{end}}'

gh issue list -R Green-Software-Foundation/carbon-aware-sdk --search "-label:agenda closed:>=2024-01-17" --json number,title,url --template \
        '{{range .}}{{ printf "\n-[#%v" .number | autocolor "green"}} {{.title}} {{ printf "](%v)" .url}}{{end}}'

which returns a more exhaustive list I may use more of:
-PR #472 Update README.md
-PR #469 Update SECURITY.md
-PR #466 New documentation site with Docusaurus
-PR #464 Create SECURITY.md
-PR #463 Carbon hack 24 banner image fix
-PR #462 Docs/test coverage
-PR #461 CarbonHack24 Update to README.md
-PR #459 Readme updates for clarity
-PR #457 Features/codespaces quickstart
-PR #454 Update quickstart.md
-PR #453 Update overview.md
-PR #452 Update carbon-aware-cli.md
-PR #449 Support location source setting in Helm chart
-PR #442 Update containerization.md
-PR #441 Draft of enablement.md
-PR #432 Ignore - This is a test for copilot for PRs please ignore
-PR #431 Update documentation of Usefulness (adopters.md)
-PR #430 Update WattTime registration link
-PR #359 Add 2b-generate-java-client.yaml
-#467 Update the Carbon Aware SDK docusaurus link
-#460 [Feature Contribution]: CarbonHack 24 banner added to readme to match IF and other GSF repos
-#438 [Bug]: Code coverage: Main release check issues to review
-#416 Add disclaimer banner to any public-facing documentation (docusaurus webpage)
-#415 Update documentation of secureness (security.md)
-#414 Update documentation of Usefulness (adopters.md)
-#413 Update documentation for Test Coverage
-#412 Update documentation for End User Guide (enablement.md)
-#411 Update documentation for Project overview (ReadMe)
-#382 [Bug]: Some GHA were failed due to empty workflow
-#344 [Bug]: Fix and update doc deployment workflow
-#260 [Feature Request]: Missing option to select WattTime model version (Auditability)
-#207 [Feature Contribution]: Enable codespaces for the SDK repo %

[danuw]

FYI we can use this PR to remove the top banner and add the change log for 1.3 as a blog post

cc @vaughanknight @Sophietn @Willmish

[Sophietn]

Great thanks Dan. Rather than just removing the top banner we should change it to this copy from the project lifecycle:

[!important] Graduated Project This project is a Graduated Project, supported by the Green Software Foundation. The publicly available version documented in the README is trusted by the GSF. New versions of the project may be released, or it may move to the Maintained or Archived Stage.

[vaughanknight]

Happy to approve Dan and merge now, might be best to do the banner updates separate since it has different impacts?