Skip to content

Commit

Permalink
Update CHANGELOG.md
Browse files Browse the repository at this point in the history
- Fix typos.
- Add clarification for HTTP 500 bugfix.
- Add clarification for required signoff.

Signed-off-by: Szymon Duchniewicz <[email protected]>
  • Loading branch information
Willmish authored Jul 24, 2023
1 parent e6c4735 commit af5d5ec
Showing 1 changed file with 10 additions and 11 deletions.
21 changes: 10 additions & 11 deletions CHANGELOG.md
Original file line number Diff line number Diff line change
Expand Up @@ -12,9 +12,9 @@ All notable changes to the Carbon Aware SDK will be documented in this file.
### Fixed

- Fixed generated test data that had time bomb bug that was in test data, which caused integration tests to fail. This is now automatically generated each time.
- Fixed some bugs that related to underlying data source errors surfacing as 500 errors from the API. These should now be more consistent.
- Fixed some bugs that related to underlying data source errors surfacing as HTTP 500 errors from the API. These should now be more consistent.
- Fixed an issue where UTF-8 passwords were encoded as ASCII for WattTime API, causing integration failure.
- Fixes some bugs in unit tests with uncaught scenarios, or faulty tests
- Fixes some bugs in unit tests with uncaught scenarios, or faulty tests.

### Changed

Expand All @@ -25,31 +25,30 @@ All notable changes to the Carbon Aware SDK will be documented in this file.
#### API

- `/locations` - Show the list of configured named locations that can be used in the API.
- `/api/v1/swagger.yaml` - Provides OpenAPI document now at public endpoint when deployed
- `/api/v1/swagger.yaml` - Provides OpenAPI document now at public endpoint when deployed.

#### API Deployment

- Configuration has changed. Refer to upgrading from 1.0.0 to 1.1.0 below.

#### SDK

- SDK was abstracted to provide a library for DLL import usage, which now allows users to use the SDK in their projects directly without the need to deploy an API. This is useful in scenarios where the API can not be centralised. Note - we still highly recommend centralising for management of the API adn audit capabilities with observability.
- Functionality for forecast and historical data have been seperated into seperate interfaces. This impacts
configuration, see upgrading from 1.0.0 to 1.1.0 for more information
- Additional tests across the SDK have been added
- SDK was abstracted to provide a library for DLL import usage, which now allows users to use the SDK in their projects directly without the need to deploy an API. This is useful in scenarios where the API can not be centralised. Note - we still highly recommend centralising for management of the API and audit capabilities with observability.
- Functionality for forecast and historical data have been seperated into seperate interfaces. This impacts configuration, see upgrading from 1.0.0 to 1.1.0 for more information.
- Additional tests across the SDK have been added.
- Aggregation tier in the SDK was removed, this should not impact users of the SDK, but may impact maintainers who were actively contributing.


#### Other

- All contributors need to sign commit for contribution using `git commit -S`
- Added PR release workflow improvements for the project management of the CA SDK project team
- Updated the project to prune stale PR's and issues to help with the management of the CA SDK project
- All contributors need to signoff commits for contribution using `git commit -s`.
- Added PR release workflow improvements for the project management of the CA SDK project team.
- Updated the project to prune stale PR's and issues to help with the management of the CA SDK project.


### Upgrading from 1.0.0 to 1.1.0

- Configuration changes are required due to historical and forecast configuration now being decoupled. Refer to - [Configuration](docs/configuration.md) for a guide. The following is provided as an example of the new data source configuration format.
- Configuration changes are required due to historical and forecast configuration now being decoupled. Refer to - [Configuration](docs/configuration.md) for a guide. The following is provided as an example of the new data source configuration format.
```json
{
"DataSources": {
Expand Down

0 comments on commit af5d5ec

Please sign in to comment.