Skip to content

Commit 2e3bc33

Browse files
authored
Update ChangeLog.md
1 parent 9bb7ba1 commit 2e3bc33

File tree

1 file changed

+10
-11
lines changed

1 file changed

+10
-11
lines changed

ChangeLog.md

Lines changed: 10 additions & 11 deletions
Original file line numberDiff line numberDiff line change
@@ -4,6 +4,9 @@ This change log will contain information on updates to the Congress.gov API, the
44
## Changes #1
55
### Impacted Endpoints: NEW Congressional Research Service (CRS) Reports Endpoints
66
A new list-level endpoint will be created that returns CRS Report data. A new detail-level endpoint will be created that returns detailed information for a particular CRS Report. Updated documentation with relevant information on data elements will be uploaded to the documentation section of this Git repository when the new endpoints go live. These new endpoints are related to [Issue #19](https://github.com/LibraryOfCongress/api.congress.gov/issues/19).
7+
## Change #2
8+
### Impacted endpoint: /committee
9+
The default sort in the committee list-level endpoint will be adjusted so that it is by `<updateDate>`. This is partially related to [Issue #117](https://github.com/LibraryOfCongress/api.congress.gov/issues/117).
710
# UPCOMING February 2025 | [Milestone](https://github.com/LibraryOfCongress/api.congress.gov/milestone/41)
811
**Expected Production Release Date: February 18, 2025**
912
## Change #1
@@ -17,9 +20,6 @@ New beta House Roll Call Votes API endpoints are targeted for release. The House
1720

1821
This is related to [Issue #64](https://github.com/LibraryOfCongress/api.congress.gov/issues/64).
1922
## Change #2
20-
### Impacted endpoint: /committee
21-
The default sort in the committee list-level endpoint will be adjusted so that it is by `<updateDate>`. This is partially related to [Issue #117](https://github.com/LibraryOfCongress/api.congress.gov/issues/117).
22-
## Change #2
2323
### Impacted endpoints: /bill/{congress}/{billType}/{billNumber}, /amendment/{congress}/{amendmentType}/{amendmentNumber}
2424
On behalf of sponsor data will be incorporated into the Congress.gov API where applicable (for certain bills and amendments).
2525
# UPCOMING January 2025, Part 2 | [Milestone](https://github.com/LibraryOfCongress/api.congress.gov/milestone/40)
@@ -36,22 +36,21 @@ Filters will be added to the /committee-meeting endpoint. Users will have the ab
3636
# UPCOMING January 2025, Part 1 | [Milestone](https://github.com/LibraryOfCongress/api.congress.gov/milestone/39)
3737
**Expected Production Release Date: January 6, 2025**
3838
## Change #1
39-
### Impacted endpoint: /committee-meeting
40-
The date format for the committee meeting will be updated to the API's existing standard: `YYYY-MM-DDT00:00:00Z`.
41-
## Change #2
4239
### Impacted endpoint: /daily-congressional-record
4340
When requesting a record from the daily-congressional-record API, links to the "Formatted Text" version of `entireIssue` do not include all of the text from the Daily Congressional Record. This will be investigated and fixed. This is related to [Issue #220](https://github.com/LibraryOfCongress/api.congress.gov/issues/220).
44-
## Change #3
41+
## Change #2
4542
### Impacted endpoint: /bill/{congress}/{billType}
4643
Currently, the bill list-level API endpoint returns at least one item out of order when requested with the sort=updateDate+desc parameter. This will be investigated and fixed. This is related to [Issue #231](https://github.com/LibraryOfCongress/api.congress.gov/issues/231).
47-
# UPCOMING December 2024 | [Milestone](https://github.com/LibraryOfCongress/api.congress.gov/milestone/38)
48-
**Expected Production Release Date: December 16, 2024**
44+
## Change #3
45+
### Impacted endpoint: /congress
46+
An `<updateDate>` element will be added to the Congress endpoint. This is related to [Issue #117](https://github.com/LibraryOfCongress/api.congress.gov/issues/117).
47+
# COMPLETED December 2024 | [Milestone](https://github.com/LibraryOfCongress/api.congress.gov/milestone/38)
4948
## Change #1
5049
### Impacted endpoint: /daily-congressional-record
51-
The daily Congressional Record API endpoints will be adjusted so that the default sort is by `<updateDate>`. This is related to [Issue #223](https://github.com/LibraryOfCongress/api.congress.gov/issues/223).
50+
The daily Congressional Record API endpoints were adjusted so that the default sort is by `<updateDate>`. This was related to [Issue #223](https://github.com/LibraryOfCongress/api.congress.gov/issues/223).
5251
## Change #2
5352
### Impacted endpoint: /committee-report
54-
The committee report API endpoints will be adjusted so that the default sort is by `<updateDate>`. This is related to [Issue #224](https://github.com/LibraryOfCongress/api.congress.gov/issues/224).
53+
The committee report API endpoints were adjusted so that the default sort is by `<updateDate>`. This was related to [Issue #224](https://github.com/LibraryOfCongress/api.congress.gov/issues/224).
5554
# COMPLETED November 2024, Part 2 | [Milestone](https://github.com/LibraryOfCongress/api.congress.gov/milestone/37)
5655
## Change #1
5756
### Impacted endpoint: /committee-meeting

0 commit comments

Comments
 (0)