Skip to content

Commit d50df57

Browse files
committed
Create Changelogs “4-59-2-2020-03-10”
1 parent e27aa9d commit d50df57

File tree

1 file changed

+37
-0
lines changed

1 file changed

+37
-0
lines changed
Lines changed: 37 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,37 @@
1+
---
2+
title: '4.59.2: 2020-03-10'
3+
date: 2020-03-10T04:00:00.000Z
4+
version: 4.59.2
5+
changelog:
6+
- API
7+
---
8+
<!-- API changelog requirements - delete this before merging -->
9+
- Replace all instances of X.X.X in the frontmatter with the appropriate API spec.
10+
- Replace all instances of 2019-01-01 with the production release date for the API.
11+
- All items in the changelog should mention which endpoints are affected.
12+
- For changes and bugfixes, describe the previous behavior AND the new behavior.
13+
14+
<!-- Where to put things - delete this before merging -->
15+
Some heuristics for which heading to put API reference updates under:
16+
17+
*Added*
18+
- New endpoints.
19+
- New fields in the request or a response of an existing endpoint.
20+
21+
*Changed*
22+
- Changes in the behavior of an existing endpoing, when the previous behavior was working as it was designed. In other words, non-bugfix changes.
23+
24+
*Fixes*
25+
- Bugfixes: Changes to the behavior of an endpoint, where the previous behavior was not working as intended/expected/documented.
26+
27+
<!-- Sample syntax - delete this before merging -->
28+
29+
- References to an endpoint should be in this format: `the Endpoint Name ([VERB /path/to/endpoint/{endpointVariable}](https://developers.linode.com/api/docs/v4/{endpoint}/{#endpointVariable})) endpoint` *Example*: `the Clone Linode ([POST /linode/instances/{linodeId}/clone](https://developers.linode.com/api/v4/linode-instances-linode-id-clone/#post)) endpoint`
30+
31+
<!-- Fill these sections out: -->
32+
33+
### Added
34+
35+
### Changed
36+
37+
### Fixed

0 commit comments

Comments
 (0)