Release Notes and Schedule
The release notes list the GitHub issues and a summary of what has changed in PeeringDB software releases.
Each new release has a one week beta test period on the beta server before it goes live. The beta and new releases are announced on the PeeringDB Announce Mailing List and on Twitter, LinkedIn and Facebook.
Release schedule
This schedule provides planned dates for PeeringDB’s future releases. We are sharing these dates to help PeeringDB users plan ahead for testing new and improved features in beta. We also want to help volunteer developers know the date on which their code changes are needed for internal testing before beta release.
We provide a rolling schedule. Dates can change, so if you have a question or request please contact us at: support@peeringdb.com.
Our releases are generally deployed at around 04:00 UTC.
| Release number | Internal testing | Beta release | Production release |
|---|---|---|---|
| 2.45.0 | 2023-03-08 | 2023-03-15 | 2023-03-22 |
| 2.46.0 | 2023-04-05 | 2023-04-12 | 2023-04-19 |
| 2.47.0 | 2023-05-10 | 2023-05-17 | 2023-05-24 |
| 2.48.0 | 2023-06-14 | 2023-06-21 | 2023-06-28 |
Release 2.45.0
Beta Announcement Date: 15 March 2023
Release Date: 22 March 2023
| GitHub Issue | Summary |
|---|---|
| #1295 Allow anonymous users to change languages | It is now possible to select a PeeringDB translation without logging in to the website. |
| #1281 better <title> tags | The HTML <title> tag of pages on www.peeringdb.com now shows key information from the page, like a network name or search term. |
| #749 Rename Private Peering Facilities to Interconnection Facilities in the UI | Private Peering Facilities have been renamed to Interconnection Facilities in the UI. |
| #1308 Deploy Google Analytics on www and docs | We have deployed Google Analytics to measure website traffic. |
| #1271 Implement auto-removal of stale networks according to DOTF recommendations | Stay networks are now automatically removed as per the DOTF recommendations. |
| #389 It should be impossible to save an active entity under an entity that is marked as deleted. | It is no longer possible to save an object under one that's marked as deleted. |
Release 2.44.0
Beta Announcement Date: 15 February 2023
Release Date: 22 February 2023
| GitHub Issue | Summary |
|---|---|
| #1110 Add campus object | Initial deployment of a Campus object – a record to describe facilities where inter-facility cross connects are available as easily as intra-facility cross connects. |
| #1191 OAuth logins with 2FA don't complete first time | Fixes a bug that broke the OAuth flow when MFA was enabled. |
| #668 Add "self" as an object identifier, for documentation purposes | Adds a "self" object identifier to API and views for GET requests. Authenticated users going to https://www.peeringdb.com/{net |
Release 2.43.1
Release Date: 10 February 2023
| GitHub Issue | Summary |
|---|---|
| #1315 issues when accepting / denying carrier presence requests | Fix permission issues when accepting or rejecting carrier facility presence requests and automatically approve them when they are from the same organization. |
Release 2.43.0
Beta Announcement Date: 18 January 2023
Release Date: 25 January 2023
| GitHub Issue | Summary |
|---|---|
| #909 Add Carrier Record Type | Initial deployment of a Carrier record – a record to describe providers of high capacity links between facilities, running at layers 1 or 2. |
| #1140 API keys: disabling of user account by a PeeringDB admin does not disable access via a User API key. Also no disable mech, only revoke. | Fixes a bug where user API Keys were not disabled when their account was disabled. |
| #1220 API requests with invalid Authentication headers should notify users in some way | Requests with an invalid API key now return appropriate error codes. |
| #1130 Allow user to change account username | Users can now change their account name. |
| #970 Cache hints are needed for optimal CDN use | Adds cache hints to make CDN deployment more effective. |
| #1278 Commandline tool "Run command" button gone | Fixes a problem affecting Admins – a tool was hidden. |
| #1279 RIR status gets deleted when changes are made to the network | Improves the new process for validating networks against RIR data (see: #1280). |
| #658 Improve MTU field | MTUs now default to 1500 and there's a new dropdown list of options to select from. |
| #1282 Ops: Emails to OPERATIONS_EMAIL need to be rate-limited | Introduces a rate limit for automatic mail sent to Operations. |
| #1283 Footer "Global System Statistics" should be cached within django instance, not updated with every page load | Global System Statistics are now generated periodically instead of on each page load. |
| #1284 Ops: django needs lightweight healthcheck route that confirms database connectivity | Introduces a lightweight health check for database availability. |
| #1285 Ops: various indexes are needed | Introduces new database indexes. |
| #1288 Ops: Expose CSP_CONNECT_SRC to .env | Add configuration options for ease of operations. |
| #1296 CSRF cookie not set error from email confirmation view | Fix a bug with CSRF cookies not being set. |