List available rollbacks by pchila · Pull Request #11751 · elastic/elastic-agent

pchila · 2025-12-11T16:15:17Z

What does this PR do?

Add elastic-agent upgrade list-rollbacks subcommand to show whether there are versions of agent that can be used to trigger a manual rollback with elastic-agent upgrade --rollback <version>

Available rollbacks are listed by version and include versioned home and TTL for each.
Output is available in either 'human', 'json' or 'yaml' format

Output looks similar to this

vagrant@elastic-agent-dev:/vagrant/build/distributions$ sudo elastic-agent upgrade list-rollbacks
── 9.4.0-SNAPSHOT
   ├─ VersionedHome: data/elastic-agent-9.4.0-SNAPSHOT-facbd1
   └─ ValidUntil: 2026-01-12T12:54:30Z
vagrant@elastic-agent-dev:/vagrant/build/distributions$ sudo elastic-agent upgrade list-rollbacks -o yaml
- version: 9.4.0-SNAPSHOT
  versioned_home: data/elastic-agent-9.4.0-SNAPSHOT-facbd1
  valid_until: 2026-01-12T12:54:30Z
vagrant@elastic-agent-dev:/vagrant/build/distributions$ sudo elastic-agent upgrade list-rollbacks -o json
[
  {
    "version": "9.4.0-SNAPSHOT",
    "versioned_home": "data/elastic-agent-9.4.0-SNAPSHOT-facbd1",
    "valid_until": "2026-01-12T12:54:30Z"
  }
]

Why is it important?

Checklist

I have read and understood the pull request guidelines of this project.
My code follows the style guidelines of this project
I have commented my code, particularly in hard-to-understand areas
I have made corresponding changes to the documentation
I have made corresponding change to the default configuration files
I have added tests that prove my fix is effective or that my feature works
I have added an entry in ./changelog/fragments using the changelog tool
I have added an integration test or an E2E test

Disruptive User Impact

How to test this PR locally

Package the agent from this PR (it can be packaged twice using an IAR-style version or any version greater or equal to 9.3.0-SNAPSHOT can be used)

USE_PACKAGE_VERSION=true AGENT_PACKAGE_VERSION=9.4.0+build20260112 BEAT_VERSION=9.4.0 SNAPSHOT=true PACKAGES="tar.gz" PLATFORMS=linux/amd64 mage package && USE_PACKAGE_VERSION=true SNAPSHOT=true PACKAGES="tar.gz" PLATFORMS=linux/amd64 mage package

unpack the initial agent package and add agent.upgrade.rollback.window: "2h" to elastic-agent.yml config file
install elastic-agent as standalone

upgrade agent to the version packaged from this PR

sudo elastic-agent upgrade --skip-verify --source-uri=file://<path where the package is located> 9.4.0+build20260112-SNAPSHOT

Wait for the upgrade to complete, then list the available rollbacks with elastic-agent upgrade list-rollbacks subcommand

vagrant@elastic-agent-dev:/vagrant/build/distributions/elastic-agent-9.4.0-SNAPSHOT-linux-x86_64$ sudo elastic-agent upgrade list-rollbacks
── 9.4.0-SNAPSHOT
   ├─ VersionedHome: data/elastic-agent-9.4.0-SNAPSHOT-facbd1
   └─ ValidUntil: 2026-01-12T14:31:09Z
vagrant@elastic-agent-dev:/vagrant/build/distributions/elastic-agent-9.4.0-SNAPSHOT-linux-x86_64$ sudo elastic-agent upgrade list-rollbacks -o json
[
  {
    "version": "9.4.0-SNAPSHOT",
    "versioned_home": "data/elastic-agent-9.4.0-SNAPSHOT-facbd1",
    "valid_until": "2026-01-12T14:31:09Z"
  }
]
vagrant@elastic-agent-dev:/vagrant/build/distributions/elastic-agent-9.4.0-SNAPSHOT-linux-x86_64$ sudo elastic-agent upgrade list-rollbacks -o yaml
- version: 9.4.0-SNAPSHOT
  versioned_home: data/elastic-agent-9.4.0-SNAPSHOT-facbd1
  valid_until: 2026-01-12T14:31:09Z
vagrant@elastic-agent-dev:/vagrant/build/distributions/elastic-agent-9.4.0-SNAPSHOT-linux-x86_64$ sudo elastic-agent upgrade list-rollbacks -o human
── 9.4.0-SNAPSHOT
   ├─ VersionedHome: data/elastic-agent-9.4.0-SNAPSHOT-facbd1
   └─ ValidUntil: 2026-01-12T14:31:09Z
vagrant@elastic-agent-dev:/vagrant/build/distributions/elastic-agent-9.4.0-SNAPSHOT-linux-x86_64$ sudo elastic-agent upgrade list-rollbacks -o wrong
unsupported output format "wrong": defaulting to "human"
── 9.4.0-SNAPSHOT
   ├─ VersionedHome: data/elastic-agent-9.4.0-SNAPSHOT-facbd1
   └─ ValidUntil: 2026-01-12T14:31:09Z

Related issues

Closes Add --list-rollbacks option to elastic-agent upgrade subcommand #6888

Questions to ask yourself

How are we going to support this in production?
How are we going to measure its adoption?
How are we going to debug this?
What are the metrics I should take care of?
...

elasticmachine · 2026-01-12T12:49:26Z

Pinging @elastic/elastic-agent-control-plane (Team:Elastic-Agent-Control-Plane)

cmacknz

Code LGTM, is there a test that can be added to ensure this works?

mergify · 2026-01-13T05:14:43Z

This pull request is now in conflicts. Could you fix it? 🙏
To fixup this pull request, you can check out it locally. See documentation: https://help.github.com/articles/checking-out-pull-requests-locally/

git fetch upstream
git checkout -b list-available-rollbacks upstream/list-available-rollbacks
git merge upstream/main
git push upstream list-available-rollbacks

pchila · 2026-01-13T08:25:16Z

Code LGTM, is there a test that can be added to ensure this works?

@cmacknz
The UpgradeCmd instantiates its own client, making unit testing unnecessarily difficult (there is a need for a mockServer running with hardcoded behavior)

Request and responses messages are generated with cproto and the server operation implementation is pretty simple.

I suppose that this could be tested in an integration test (a new or an existing one) but that would seem overkill.

cmacknz · 2026-01-13T15:19:55Z

Adding a check for available rollbacks in an existing integration test works for me. I wouldn't write a new integration test for this if unit testing isn't convenient.

For example we could list rollbacks right before manually triggering one in the block below for example and that would cover this and seems straight forward:

elastic-agent/testing/integration/ess/upgrade_rollback_test.go

Lines 401 to 406 in 10d1902

    
           rollbackTrigger: func(ctx context.Context, t *testing.T, client client.Client, startFixture, endFixture *atesting.Fixture) { 
        
           	t.Logf("sending version=%s rollback=%v upgrade to agent", startFixture.Version(), true) 
        
           	retVal, err := client.Upgrade(ctx, startFixture.Version(), true, "", false, false) 
        
           	require.NoError(t, err, "error triggering manual rollback to version %s", startFixture.Version()) 
        
           	t.Logf("received output %s from upgrade command", retVal) 
        
           },

mergify · 2026-01-14T18:18:47Z

This pull request is now in conflicts. Could you fix it? 🙏
To fixup this pull request, you can check out it locally. See documentation: https://help.github.com/articles/checking-out-pull-requests-locally/

git fetch upstream
git checkout -b list-available-rollbacks upstream/list-available-rollbacks
git merge upstream/main
git push upstream list-available-rollbacks

…ack tests

ebeahan · 2026-01-14T18:56:15Z

@pchila sorry for my shenanigans with force pushing to fix the commit history 😢 . I think I correctly fixed the Beats submodule conflict with my latest commit.

elasticmachine · 2026-01-14T20:20:17Z

💔 Build Failed

Buildkite Build
Commit: 18b84ec

Failed CI Steps

History

💔 Build #33300 failed c17a254
💔 Build #33299 failed 1e10b16
💔 Build #33292 failed e90fad7
💔 Build #33270 failed b9537d7

cc @pchila

* add new messages and operation * List available rollbacks from CLI * Add output flag for human, json, yaml * assert list rollback command in standalone manual rollback tests * bump beats * fixup! assert list rollback command in standalone manual rollback tests * fixup! fixup! assert list rollback command in standalone manual rollback tests --------- Co-authored-by: Eric Beahan <eric.beahan@elastic.co> (cherry picked from commit 876106c)

* add new messages and operation * List available rollbacks from CLI * Add output flag for human, json, yaml * assert list rollback command in standalone manual rollback tests * bump beats * fixup! assert list rollback command in standalone manual rollback tests * fixup! fixup! assert list rollback command in standalone manual rollback tests --------- (cherry picked from commit 876106c) Co-authored-by: Paolo Chilà <paolo.chila@elastic.co> Co-authored-by: Eric Beahan <eric.beahan@elastic.co>

* add new messages and operation * List available rollbacks from CLI * Add output flag for human, json, yaml * assert list rollback command in standalone manual rollback tests * bump beats * fixup! assert list rollback command in standalone manual rollback tests * fixup! fixup! assert list rollback command in standalone manual rollback tests --------- Co-authored-by: Eric Beahan <eric.beahan@elastic.co>

…ead of MY_POD_IP (#12205) * Update OTel collector gateway to use 0.0.0.0 instead of MY_POD_IP This allows the gateway to listen on all network interfaces for traffic, this follows the same pattern that the daemon collector uses. This prevents warnings being logged in k8s * Add changelog for OTel gateway endpoint update * Update gateway collector binding address to use specific K8s OTEL_K8S_POD_IP This is done as using 0.0.0.0 can be more risky in the case of DDOS attacks, see https://opentelemetry.io/docs/security/config-best-practices/#protect-against-denial-of-service-attacks * Update OTel gateway otlp endpoint to be OTEL_K8S_POD_IP in k8s tests * Update changelog with OTEL_K8S_POD_IP for kube-stack gateway OTLP update * Revert update to k8s integration test for OTel gateway These tests are automatically updated from upstream * docs: update security url to link to central policy (#12241) * docs: update security url to link to central policy * docs: update security url to link to central policy * [main][Automation] Update elastic/beats to eff88abc6dc8 (#12237) Co-authored-by: swiatekm <93588780+swiatekm@users.noreply.github.com> Co-authored-by: Mikołaj Świątek <mail@mikolajswiatek.com> * Update elastic-agent-libs 0.31.0 -> 0.32.0 (#12240) Co-authored-by: Mikołaj Świątek <mail@mikolajswiatek.com> * List available rollbacks (#11751) * add new messages and operation * List available rollbacks from CLI * Add output flag for human, json, yaml * assert list rollback command in standalone manual rollback tests * bump beats * fixup! assert list rollback command in standalone manual rollback tests * fixup! fixup! assert list rollback command in standalone manual rollback tests --------- Co-authored-by: Eric Beahan <eric.beahan@elastic.co> * [main][Automation] Update elastic/beats to 990735bb782a (#12252) Co-authored-by: swiatekm <93588780+swiatekm@users.noreply.github.com> --------- Co-authored-by: Mikołaj Świątek <mail@mikolajswiatek.com> Co-authored-by: Paul McCann <paul.mccann@elastic.co> Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com> Co-authored-by: swiatekm <93588780+swiatekm@users.noreply.github.com> Co-authored-by: Michal Pristas <michal.pristas@elastic.co> Co-authored-by: Paolo Chilà <paolo.chila@elastic.co> Co-authored-by: Eric Beahan <eric.beahan@elastic.co>

…ead of MY_POD_IP (#12205) * Update OTel collector gateway to use 0.0.0.0 instead of MY_POD_IP This allows the gateway to listen on all network interfaces for traffic, this follows the same pattern that the daemon collector uses. This prevents warnings being logged in k8s * Add changelog for OTel gateway endpoint update * Update gateway collector binding address to use specific K8s OTEL_K8S_POD_IP This is done as using 0.0.0.0 can be more risky in the case of DDOS attacks, see https://opentelemetry.io/docs/security/config-best-practices/#protect-against-denial-of-service-attacks * Update OTel gateway otlp endpoint to be OTEL_K8S_POD_IP in k8s tests * Update changelog with OTEL_K8S_POD_IP for kube-stack gateway OTLP update * Revert update to k8s integration test for OTel gateway These tests are automatically updated from upstream * docs: update security url to link to central policy (#12241) * docs: update security url to link to central policy * docs: update security url to link to central policy * [main][Automation] Update elastic/beats to eff88abc6dc8 (#12237) Co-authored-by: swiatekm <93588780+swiatekm@users.noreply.github.com> Co-authored-by: Mikołaj Świątek <mail@mikolajswiatek.com> * Update elastic-agent-libs 0.31.0 -> 0.32.0 (#12240) Co-authored-by: Mikołaj Świątek <mail@mikolajswiatek.com> * List available rollbacks (#11751) * add new messages and operation * List available rollbacks from CLI * Add output flag for human, json, yaml * assert list rollback command in standalone manual rollback tests * bump beats * fixup! assert list rollback command in standalone manual rollback tests * fixup! fixup! assert list rollback command in standalone manual rollback tests --------- Co-authored-by: Eric Beahan <eric.beahan@elastic.co> * [main][Automation] Update elastic/beats to 990735bb782a (#12252) Co-authored-by: swiatekm <93588780+swiatekm@users.noreply.github.com> --------- Co-authored-by: Mikołaj Świątek <mail@mikolajswiatek.com> Co-authored-by: Paul McCann <paul.mccann@elastic.co> Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com> Co-authored-by: swiatekm <93588780+swiatekm@users.noreply.github.com> Co-authored-by: Michal Pristas <michal.pristas@elastic.co> Co-authored-by: Paolo Chilà <paolo.chila@elastic.co> Co-authored-by: Eric Beahan <eric.beahan@elastic.co> (cherry picked from commit 6ae71f4)

…ead of MY_POD_IP (#12205) (#12256) * Update OTel collector gateway to use 0.0.0.0 instead of MY_POD_IP This allows the gateway to listen on all network interfaces for traffic, this follows the same pattern that the daemon collector uses. This prevents warnings being logged in k8s * Add changelog for OTel gateway endpoint update * Update gateway collector binding address to use specific K8s OTEL_K8S_POD_IP This is done as using 0.0.0.0 can be more risky in the case of DDOS attacks, see https://opentelemetry.io/docs/security/config-best-practices/#protect-against-denial-of-service-attacks * Update OTel gateway otlp endpoint to be OTEL_K8S_POD_IP in k8s tests * Update changelog with OTEL_K8S_POD_IP for kube-stack gateway OTLP update * Revert update to k8s integration test for OTel gateway These tests are automatically updated from upstream * docs: update security url to link to central policy (#12241) * docs: update security url to link to central policy * docs: update security url to link to central policy * [main][Automation] Update elastic/beats to eff88abc6dc8 (#12237) * Update elastic-agent-libs 0.31.0 -> 0.32.0 (#12240) * List available rollbacks (#11751) * add new messages and operation * List available rollbacks from CLI * Add output flag for human, json, yaml * assert list rollback command in standalone manual rollback tests * bump beats * fixup! assert list rollback command in standalone manual rollback tests * fixup! fixup! assert list rollback command in standalone manual rollback tests --------- * [main][Automation] Update elastic/beats to 990735bb782a (#12252) --------- (cherry picked from commit 6ae71f4) Co-authored-by: Dónal O'Sullivan <92297851+osullivandonal@users.noreply.github.com> Co-authored-by: Mikołaj Świątek <mail@mikolajswiatek.com> Co-authored-by: Paul McCann <paul.mccann@elastic.co> Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com> Co-authored-by: swiatekm <93588780+swiatekm@users.noreply.github.com> Co-authored-by: Michal Pristas <michal.pristas@elastic.co> Co-authored-by: Paolo Chilà <paolo.chila@elastic.co> Co-authored-by: Eric Beahan <eric.beahan@elastic.co>

…ead of MY_POD_IP (#12205) (#12257) * Update OTel collector gateway to use 0.0.0.0 instead of MY_POD_IP This allows the gateway to listen on all network interfaces for traffic, this follows the same pattern that the daemon collector uses. This prevents warnings being logged in k8s * Add changelog for OTel gateway endpoint update * Update gateway collector binding address to use specific K8s OTEL_K8S_POD_IP This is done as using 0.0.0.0 can be more risky in the case of DDOS attacks, see https://opentelemetry.io/docs/security/config-best-practices/#protect-against-denial-of-service-attacks * Update OTel gateway otlp endpoint to be OTEL_K8S_POD_IP in k8s tests * Update changelog with OTEL_K8S_POD_IP for kube-stack gateway OTLP update * Revert update to k8s integration test for OTel gateway These tests are automatically updated from upstream * docs: update security url to link to central policy (#12241) * docs: update security url to link to central policy * docs: update security url to link to central policy * [main][Automation] Update elastic/beats to eff88abc6dc8 (#12237) * Update elastic-agent-libs 0.31.0 -> 0.32.0 (#12240) * List available rollbacks (#11751) * add new messages and operation * List available rollbacks from CLI * Add output flag for human, json, yaml * assert list rollback command in standalone manual rollback tests * bump beats * fixup! assert list rollback command in standalone manual rollback tests * fixup! fixup! assert list rollback command in standalone manual rollback tests --------- * [main][Automation] Update elastic/beats to 990735bb782a (#12252) --------- (cherry picked from commit 6ae71f4) Co-authored-by: Dónal O'Sullivan <92297851+osullivandonal@users.noreply.github.com> Co-authored-by: Mikołaj Świątek <mail@mikolajswiatek.com> Co-authored-by: Paul McCann <paul.mccann@elastic.co> Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com> Co-authored-by: swiatekm <93588780+swiatekm@users.noreply.github.com> Co-authored-by: Michal Pristas <michal.pristas@elastic.co> Co-authored-by: Paolo Chilà <paolo.chila@elastic.co> Co-authored-by: Eric Beahan <eric.beahan@elastic.co>

…ead of MY_POD_IP (#12205) (#12255) * Update OTel collector gateway to use 0.0.0.0 instead of MY_POD_IP This allows the gateway to listen on all network interfaces for traffic, this follows the same pattern that the daemon collector uses. This prevents warnings being logged in k8s * Add changelog for OTel gateway endpoint update * Update gateway collector binding address to use specific K8s OTEL_K8S_POD_IP This is done as using 0.0.0.0 can be more risky in the case of DDOS attacks, see https://opentelemetry.io/docs/security/config-best-practices/#protect-against-denial-of-service-attacks * Update OTel gateway otlp endpoint to be OTEL_K8S_POD_IP in k8s tests * Update changelog with OTEL_K8S_POD_IP for kube-stack gateway OTLP update * Revert update to k8s integration test for OTel gateway These tests are automatically updated from upstream * docs: update security url to link to central policy (#12241) * docs: update security url to link to central policy * docs: update security url to link to central policy * [main][Automation] Update elastic/beats to eff88abc6dc8 (#12237) * Update elastic-agent-libs 0.31.0 -> 0.32.0 (#12240) * List available rollbacks (#11751) * add new messages and operation * List available rollbacks from CLI * Add output flag for human, json, yaml * assert list rollback command in standalone manual rollback tests * bump beats * fixup! assert list rollback command in standalone manual rollback tests * fixup! fixup! assert list rollback command in standalone manual rollback tests --------- * [main][Automation] Update elastic/beats to 990735bb782a (#12252) --------- (cherry picked from commit 6ae71f4) Co-authored-by: Dónal O'Sullivan <92297851+osullivandonal@users.noreply.github.com> Co-authored-by: Mikołaj Świątek <mail@mikolajswiatek.com> Co-authored-by: Paul McCann <paul.mccann@elastic.co> Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com> Co-authored-by: swiatekm <93588780+swiatekm@users.noreply.github.com> Co-authored-by: Michal Pristas <michal.pristas@elastic.co> Co-authored-by: Paolo Chilà <paolo.chila@elastic.co> Co-authored-by: Eric Beahan <eric.beahan@elastic.co>

pchila self-assigned this Dec 11, 2025

pchila added enhancement New feature or request Team:Elastic-Agent-Control-Plane Label for the Agent Control Plane team backport-skip skip-changelog labels Dec 11, 2025

ebeahan mentioned this pull request Dec 19, 2025

Set manual rollback default window to 7 days #11955

Merged

ebeahan added backport-9.3 Automated backport to the 9.3 branch and removed backport-skip labels Jan 5, 2026

ebeahan mentioned this pull request Jan 5, 2026

Add rollback_window to elastic agent configuration with a default value of 7d #6881

Closed

pchila force-pushed the list-available-rollbacks branch from 3dcce8d to 444311e Compare January 12, 2026 12:34

pchila marked this pull request as ready for review January 12, 2026 12:49

pchila requested a review from a team as a code owner January 12, 2026 12:49

pchila requested review from michel-laterman and swiatekm January 12, 2026 12:49

cmacknz reviewed Jan 12, 2026

View reviewed changes

pchila force-pushed the list-available-rollbacks branch from 91e7b92 to 9fd3ea4 Compare January 13, 2026 08:33

cmacknz previously approved these changes Jan 13, 2026

View reviewed changes

pchila dismissed cmacknz’s stale review via e74b496 January 13, 2026 21:31

pchila force-pushed the list-available-rollbacks branch from fa37784 to e74b496 Compare January 13, 2026 21:31

cmacknz previously approved these changes Jan 13, 2026

View reviewed changes

pchila dismissed cmacknz’s stale review via b9537d7 January 14, 2026 06:58

cmacknz previously approved these changes Jan 14, 2026

View reviewed changes

ebeahan enabled auto-merge (squash) January 14, 2026 17:48

ebeahan dismissed cmacknz’s stale review via 1e10b16 January 14, 2026 18:21

add new messages and operation

a8c223f

pchila added 6 commits January 14, 2026 12:25

List available rollbacks from CLI

7a78855

Add output flag for human, json, yaml

f1ec97f

assert list rollback command in standalone manual rollback tests

2583516

bump beats

44eb310

fixup! assert list rollback command in standalone manual rollback tests

e592b65

fixup! fixup! assert list rollback command in standalone manual rollb…

c17a254

…ack tests

ebeahan force-pushed the list-available-rollbacks branch from 1e10b16 to c17a254 Compare January 14, 2026 18:27

bump beats

18b84ec

ebeahan approved these changes Jan 14, 2026

View reviewed changes

ebeahan merged commit 876106c into elastic:main Jan 14, 2026
22 checks passed

mergify bot mentioned this pull request Jan 14, 2026

[9.3] (backport #11751) List available rollbacks #12250

Merged

8 tasks

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

List available rollbacks#11751

List available rollbacks#11751
ebeahan merged 8 commits intoelastic:mainfrom
pchila:list-available-rollbacks

pchila commented Dec 11, 2025 •

edited

Loading

Uh oh!

elasticmachine commented Jan 12, 2026

Uh oh!

cmacknz left a comment

Uh oh!

mergify bot commented Jan 13, 2026

Uh oh!

pchila commented Jan 13, 2026 •

edited

Loading

Uh oh!

cmacknz commented Jan 13, 2026

Uh oh!

mergify bot commented Jan 14, 2026

Uh oh!

ebeahan commented Jan 14, 2026

Uh oh!

elasticmachine commented Jan 14, 2026 •

edited

Loading

Uh oh!

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

4 participants

Conversation

pchila commented Dec 11, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

What does this PR do?

Why is it important?

Checklist

Disruptive User Impact

How to test this PR locally

Related issues

Questions to ask yourself

Uh oh!

elasticmachine commented Jan 12, 2026

Uh oh!

cmacknz left a comment

Choose a reason for hiding this comment

Uh oh!

mergify bot commented Jan 13, 2026

Uh oh!

pchila commented Jan 13, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

cmacknz commented Jan 13, 2026

Uh oh!

mergify bot commented Jan 14, 2026

Uh oh!

ebeahan commented Jan 14, 2026

Uh oh!

elasticmachine commented Jan 14, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

💔 Build Failed

Failed CI Steps

History

Uh oh!

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

4 participants

pchila commented Dec 11, 2025 •

edited

Loading

pchila commented Jan 13, 2026 •

edited

Loading

elasticmachine commented Jan 14, 2026 •

edited

Loading