status-site merge requestshttps://gitlab.torproject.org/tpo/tpa/status-site/-/merge_requests2024-03-26T11:45:12Zhttps://gitlab.torproject.org/tpo/tpa/status-site/-/merge_requests/63Mark Tor Weather outage as resolved2024-03-26T11:45:12ZGeorg KoppenMark Tor Weather outage as resolvedCloses: #43.Closes: #43.Georg KoppenGeorg Koppenhttps://gitlab.torproject.org/tpo/tpa/status-site/-/merge_requests/62Add Tor Weather outage (for 2.0 upgrade)2024-03-19T15:35:27ZGeorg KoppenAdd Tor Weather outage (for 2.0 upgrade)Closes: #42.Closes: #42.Georg KoppenGeorg Koppenhttps://gitlab.torproject.org/tpo/tpa/status-site/-/merge_requests/61Mark Exonerator incident as resolved2024-03-12T12:25:43ZGeorg KoppenMark Exonerator incident as resolvedCloses: #41.Closes: #41.Georg KoppenGeorg Koppenhttps://gitlab.torproject.org/tpo/tpa/status-site/-/merge_requests/60clarify outage timings for check-012024-01-31T16:54:32Zanarcatclarify outage timings for check-01After digging in the logs, those were the actual times when the outage
occured, it was longer than originally documented...After digging in the logs, those were the actual times when the outage
occured, it was longer than originally documented...anarcatanarcathttps://gitlab.torproject.org/tpo/tpa/status-site/-/merge_requests/59Mark Tor Check incident as resolved2024-01-31T16:18:12ZGeorg KoppenMark Tor Check incident as resolvedSee: #40 for details.See: #40 for details.Georg KoppenGeorg Koppenhttps://gitlab.torproject.org/tpo/tpa/status-site/-/merge_requests/58Add Tor Check outage2024-01-31T14:43:00ZGeorg KoppenAdd Tor Check outageCloses: #40.Closes: #40.Georg KoppenGeorg Koppenhttps://gitlab.torproject.org/tpo/tpa/status-site/-/merge_requests/56fix submodule update procedure & update to latest cstate2024-01-29T16:42:43Zanarcatfix submodule update procedure & update to latest cstateThe procedure, as is, didn't pull from upstream so it failed to find
new tags.The procedure, as is, didn't pull from upstream so it failed to find
new tags.anarcatanarcathttps://gitlab.torproject.org/tpo/tpa/status-site/-/merge_requests/55attempt to follow git tags updates in submodules2024-01-30T02:29:56Zanarcatattempt to follow git tags updates in submodulesThis is cargo-culted from:
https://www.gaige.net/renovating-git-tags.html
I have no idea if or how this will work: I am not familiar with a #foo
suffix to submodules URLs and suspect this just won't do anything at
all. Maybe it's some ...This is cargo-culted from:
https://www.gaige.net/renovating-git-tags.html
I have no idea if or how this will work: I am not familiar with a #foo
suffix to submodules URLs and suspect this just won't do anything at
all. Maybe it's some magic convention that will trigger something
internally in renovate?
Idea from @micah.anarcatanarcathttps://gitlab.torproject.org/tpo/tpa/status-site/-/merge_requests/47add component links2023-11-22T15:48:26Zanarcatadd component linksCloses: tpo/tpa/status-site#34Closes: tpo/tpa/status-site#34anarcatanarcathttps://gitlab.torproject.org/tpo/tpa/status-site/-/merge_requests/46fix review apps links2023-11-09T22:42:28Zanarcatfix review apps linksThis tweaks the `baseURL` variable to the review app URL, also known
as the environment URL.
Alternatively, we could use `--baseURL /`, but according to the config
file, that has problems with RSS feeds. We do not use those, but it
seem...This tweaks the `baseURL` variable to the review app URL, also known
as the environment URL.
Alternatively, we could use `--baseURL /`, but according to the config
file, that has problems with RSS feeds. We do not use those, but it
seems safer to use a full URL here.
Closes: #36anarcatanarcathttps://gitlab.torproject.org/tpo/tpa/status-site/-/merge_requests/45chore(deps): update themes/cstate digest to ed865ee2023-11-09T17:04:32ZRenovate Botchore(deps): update themes/cstate digest to ed865eeThis MR contains the following updates:
| Package | Update | Change |
|---|---|---|
| themes/cstate | digest | `b5d0763` -> `ed865ee` |
---
### Configuration
📅 **Schedule**: Branch creation - At any time (no schedule defined), Autome...This MR contains the following updates:
| Package | Update | Change |
|---|---|---|
| themes/cstate | digest | `b5d0763` -> `ed865ee` |
---
### Configuration
📅 **Schedule**: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 **Automerge**: Disabled by config. Please merge this manually once you are satisfied.
♻ **Rebasing**: Whenever MR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 **Ignore**: Close this MR and you won't be reminded about this update again.
---
- [ ] <!-- rebase-check -->If you want to rebase/retry this MR, check this box
---
This MR has been generated by [Renovate Bot](https://github.com/renovatebot/renovate).
<!--renovate-debug:eyJjcmVhdGVkSW5WZXIiOiIzNy41Mi4wIiwidXBkYXRlZEluVmVyIjoiMzcuNTIuMCIsInRhcmdldEJyYW5jaCI6Im1haW4ifQ==-->
Closes: #33https://gitlab.torproject.org/tpo/tpa/status-site/-/merge_requests/44renovate: enable submodules tracking2023-11-09T16:46:01Zanarcatrenovate: enable submodules trackingThis is a "beta" feature, according to:
https://docs.renovatebot.com/modules/manager/git-submodules/
I am not sure it will actually work the way we want: I suspect it will
actually pull the latest ref, and not the latest tag. But we'll...This is a "beta" feature, according to:
https://docs.renovatebot.com/modules/manager/git-submodules/
I am not sure it will actually work the way we want: I suspect it will
actually pull the latest ref, and not the latest tag. But we'll see!https://gitlab.torproject.org/tpo/tpa/status-site/-/merge_requests/43chore(deps): update registry.gitlab.com/pages/hugo/hugo_extended docker tag t...2023-11-09T16:43:50ZRenovate Botchore(deps): update registry.gitlab.com/pages/hugo/hugo_extended docker tag to v0.120.4This MR contains the following updates:
| Package | Type | Update | Change |
|---|---|---|---|
| registry.gitlab.com/pages/hugo/hugo_extended | image | minor | `0.65.3` -> `0.120.4` |
---
### Configuration
📅 **Schedule**: Branch crea...This MR contains the following updates:
| Package | Type | Update | Change |
|---|---|---|---|
| registry.gitlab.com/pages/hugo/hugo_extended | image | minor | `0.65.3` -> `0.120.4` |
---
### Configuration
📅 **Schedule**: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 **Automerge**: Disabled by config. Please merge this manually once you are satisfied.
♻ **Rebasing**: Whenever MR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 **Ignore**: Close this MR and you won't be reminded about this update again.
---
- [ ] <!-- rebase-check -->If you want to rebase/retry this MR, check this box
---
This MR has been generated by [Renovate Bot](https://github.com/renovatebot/renovate).
<!--renovate-debug:eyJjcmVhdGVkSW5WZXIiOiIzNy41Mi4wIiwidXBkYXRlZEluVmVyIjoiMzcuNTIuMCIsInRhcmdldEJyYW5jaCI6Im1haW4ifQ==-->https://gitlab.torproject.org/tpo/tpa/status-site/-/merge_requests/42Configure Renovate2023-11-29T17:56:39ZRenovate BotConfigure RenovateWelcome to [Renovate](https://github.com/renovatebot/renovate)! This is an onboarding MR to help you understand and configure settings before regular Merge Requests begin.
🚦 To activate Renovate, merge this Merge Request. To disable Ren...Welcome to [Renovate](https://github.com/renovatebot/renovate)! This is an onboarding MR to help you understand and configure settings before regular Merge Requests begin.
🚦 To activate Renovate, merge this Merge Request. To disable Renovate, simply close this Merge Request unmerged.
---
### Detected Package Files
* `.gitlab-ci.yml` (gitlabci)
* `.gitlab-ci.yml` (gitlabci-include)
### Configuration Summary
Based on the default config's presets, Renovate will:
- Start dependency updates only once this onboarding MR is merged
- Use semantic commit type `fix` for dependencies and `chore` for all others if semantic commits are in use.
- Ignore `node_modules`, `bower_components`, `vendor` and various test/tests directories.
- Group known monorepo packages together.
- Use curated list of recommended non-monorepo package groupings.
- Apply crowd-sourced package replacement rules.
- Apply crowd-sourced workarounds for known problems with packages.
🔡 Would you like to change the way Renovate is upgrading your dependencies? Simply edit the `renovate.json` in this branch with your custom config and the list of Merge Requests in the "What to Expect" section below will be updated the next time Renovate runs.
---
### What to Expect
With your current configuration, Renovate will create 1 Merge Request:
<details>
<summary>chore(deps): update registry.gitlab.com/pages/hugo/hugo_extended docker tag to v0.120.4</summary>
- Schedule: ["at any time"]
- Branch name: `renovate/registry.gitlab.com-pages-hugo-hugo_extended-0.x`
- Merge into: `main`
- Upgrade registry.gitlab.com/pages/hugo/hugo_extended to `0.120.4`
</details>
---
❓ Got questions? Check out Renovate's [Docs](https://docs.renovatebot.com/), particularly the Getting Started section.
If you need any further assistance then you can also [request help here](https://github.com/renovatebot/renovate/discussions).
---
This MR has been generated by [Renovate Bot](https://github.com/renovatebot/renovate).
<!--renovate-config-hash:16b5d9aaa4c1b72cbe8c97df5985b530c94d3cb61c84931d45dcc539f5fbf9f7-->https://gitlab.torproject.org/tpo/tpa/status-site/-/merge_requests/41expand the downtime range from the time of the database failure2023-11-09T04:06:21Zanarcatexpand the downtime range from the time of the database failureThe argument here is that this shows up as "resolved in N hours", and
we should be honest that the outage actually started when we started
losing data.
Another way to put this would mark the upgrade time (2023-10-31) as
the start of the...The argument here is that this shows up as "resolved in N hours", and
we should be honest that the outage actually started when we started
losing data.
Another way to put this would mark the upgrade time (2023-10-31) as
the start of the outage, but I think that would be slightly less
honest, as that's just when the service was *visibly* down: all data
in the four days preceeding that are still lsot.
This MR also grew to include expansive cleanup and rewording.
See: tpo/tpa/team#41388anarcatanarcathttps://gitlab.torproject.org/tpo/tpa/status-site/-/merge_requests/40mark weather issue as resolved, add post-mortem (tpo/tpa/team#41388)2023-11-09T01:30:33Zanarcatmark weather issue as resolved, add post-mortem (tpo/tpa/team#41388)/cc @gk @lavamind/cc @gk @lavamindhttps://gitlab.torproject.org/tpo/tpa/status-site/-/merge_requests/39Add Tor Weather incident regarding Debian Bookworm upgrade2023-11-08T19:51:14ZGeorg KoppenAdd Tor Weather incident regarding Debian Bookworm upgradeCloses: #31.Closes: #31.Georg KoppenGeorg Koppenhttps://gitlab.torproject.org/tpo/tpa/status-site/-/merge_requests/37Resolve Network DDoS incident2023-05-10T06:55:24ZGeorg KoppenResolve Network DDoS incidentCloses: #30.Closes: #30.Georg KoppenGeorg Koppenhttps://gitlab.torproject.org/tpo/tpa/status-site/-/merge_requests/36Mark latest weather.torproject.org incident as resolved2023-04-17T16:20:46ZGeorg KoppenMark latest weather.torproject.org incident as resolvedCloses: #30.Closes: #30.Georg KoppenGeorg Koppenhttps://gitlab.torproject.org/tpo/tpa/status-site/-/merge_requests/35Add Tor Weather incident regarding tor-commits spam2023-04-05T14:18:29ZGeorg KoppenAdd Tor Weather incident regarding tor-commits spamCloses: #28.Closes: #28.Georg KoppenGeorg Koppen