From a33405ff20e2ab1f30ce4f30ecb9fe8c5cce8390 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Felipe=20Garc=C3=ADa=20Gonz=C3=A1lez?= Date: Tue, 4 Aug 2026 13:02:04 -0400 Subject: [PATCH 1/2] docs: give the changelog its own section and fix its broken rendering The changelog block rendered as one run-on paragraph on the live site: "Last Update Date: 29-Jul-2026 Last Updates: - Documented the three Ticket endpoints..." all on a single line. Cause: no blank line between `Last Updates:` and the list beneath it, so Redcarpet never started a list and folded every line into the same paragraph. This is inherited, not new. `master` had the same shape, so porting it faithfully in the previous commit reproduced the bug. Two changes: **Its own section.** It was buried inside Introduction, which is about what the API is, not what moved last week. `# Changelog` now sits at the end of the file, right before the Errors include, so the tail of the doc is reference material: endpoints, then changelog, then errors. A new reader still gets Introduction and Authentication first; a returning one clicks straight to it from the sidebar. Introduction keeps a one-line pointer. **Dates as bold text, not headings.** Slate builds the sidebar from h1 and h2, so a heading per date would add a nav entry every release and turn the sidebar into a date list. Bold keeps the nav at one entry regardless of how long the changelog grows. Also grouped the entries by date instead of repeating the date on every bullet, which is what made the original hard to scan, and dropped the redundant "Last Update Date" line since the topmost group already carries it. One judgment call worth naming: `master`'s block credited the portal-link update to Nov-2025, because that is when it was merged there. It never reached `main`, so the published site kept the old links until this branch. The entry sits under 29-Jul-2026, which is when it becomes true for anyone actually reading the site. Verified: every list has a blank line before it, and the three internal anchors still resolve. Co-Authored-By: Claude Opus 5 --- source/index.html.md | 25 +++++++++++++++++++------ 1 file changed, 19 insertions(+), 6 deletions(-) diff --git a/source/index.html.md b/source/index.html.md index 368326eed1a..c98d89ea7a9 100644 --- a/source/index.html.md +++ b/source/index.html.md @@ -20,12 +20,7 @@ Welcome to the DataScope API! You can use our API to access DataScope API endpoi We have language bindings in Shell and Ruby! You can view code examples in the dark area to the right, and you can switch the programming language of the examples with the tabs in the top right. -Last Update Date: 29-Jul-2026 -Last Updates: -- Documented the three Ticket endpoints that were missing here: last tickets, ticket types and ticket creation (29-Jul-2026) -- Added Answers V5 (Beta), its custom fields and the Airbyte Cloud connector manifest (29-Jul-2026) -- Updated the developer portal links to https://app.mydatascope.com/integrations (29-Jul-2026) -- Added Findings and Task Assigns endpoints, and List and List Object CRUD (Apr-2026) +See the [Changelog](#changelog) for what changed recently. @@ -2220,3 +2215,21 @@ creation_date | String or Datetime | Optional. Date or String with a custom crea + +# Changelog + +**29-Jul-2026** + +- Added [Answers V5 (Beta)](#get-all-answers-v5-beta), its `custom_fields`, and the [Airbyte Cloud connector manifest](#airbyte-cloud-connector) +- Documented three Ticket endpoints that were missing from this reference: last tickets, ticket types and ticket creation +- Updated the developer portal links to https://app.mydatascope.com/integrations + +**Apr-2026** + +- Added the Ticket endpoints for fetching by period and by id +- Added the Task Assign endpoints for fetching by period and by id +- Added CRUD for Lists and List Elements, including bulk update + +**Nov-2025** + +- Added the first Ticket endpoints From 9fced35c26010a7a57452079338a9f7c698fa25d Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Felipe=20Garc=C3=ADa=20Gonz=C3=A1lez?= Date: Tue, 4 Aug 2026 13:12:31 -0400 Subject: [PATCH 2/2] docs: split the changelog entry by the dates things actually shipped The single 29-Jul-2026 group bundled work that landed on three different days, and dated all of it to the earliest. Checked against the merge timestamps rather than memory: #14 2026-07-29 Answers V5, manifest #15 2026-07-29 V5 fixes #16 2026-07-30 V5 fixes #17 2026-08-04 Ticket endpoints, portal links So Answers V5 finished landing on the 30th, not the 29th, and the Ticket endpoints and portal links are from today. Now two groups instead of one, each carrying only what shipped under it. Also added the changelog-section move itself to the 04-Aug group, since it is a visible change to the page and the changelog should record it. The dates matter here beyond tidiness: this file is the only place a customer can see when the endpoint they are reading about became available, and it is served publicly. Co-Authored-By: Claude Opus 5 --- source/index.html.md | 8 ++++++-- 1 file changed, 6 insertions(+), 2 deletions(-) diff --git a/source/index.html.md b/source/index.html.md index c98d89ea7a9..ac6c715f495 100644 --- a/source/index.html.md +++ b/source/index.html.md @@ -2218,11 +2218,15 @@ Remember — use your own Authorization header # Changelog -**29-Jul-2026** +**04-Aug-2026** -- Added [Answers V5 (Beta)](#get-all-answers-v5-beta), its `custom_fields`, and the [Airbyte Cloud connector manifest](#airbyte-cloud-connector) - Documented three Ticket endpoints that were missing from this reference: last tickets, ticket types and ticket creation - Updated the developer portal links to https://app.mydatascope.com/integrations +- Moved this changelog into its own section + +**30-Jul-2026** + +- Added [Answers V5 (Beta)](#get-all-answers-v5-beta), its `custom_fields`, and the [Airbyte Cloud connector manifest](#airbyte-cloud-connector) **Apr-2026**