feat: implement mint command and rename binaries #196

Keinberger · 2025-12-10T11:28:50Z

Summary

This PR implements a mint CLI command, that users can use to request a public P2ID note from a faucet, i.e. "mint" tokens from a faucet.

Furthermore, this PR introduces a new miden-faucet-client binary, which implements the "mint" functionality. The reasoning as to why this decision was made is described in more detail at the "Binary refactoring" section below. This explains the large amount of file changes, although most are just due to renaming the existing "faucet" binary folder.

The mint command is part of the miden mint command that will be implemented at midenup. See this comment here on how the miden mint command will work on midenup: #192 (comment)

This feature was discussed on this issue: #192

Usage

The new command can be used as follows:

miden-faucet-client mint --amount <AMOUNT> --account <ACCOUNT_ID> --url <FAUCET_URL>

Note that the --url parameter is optional, the faucet will default to the testnet faucet URL if the flag has not been provided.

Open Questions

There is a helper function that I implemented here: I borrowed this helper function from the code present at the miden-client repository. Since both miden-client and miden-faucet will now use the same logic, I think it might make sense to include that function in miden-base so that both repositories can import it from there. Let me know about your thoughts!
I placed the tests inside of the miden-faucet-client into a dedicated tests/ folder, which speaks against the fashion of how tests are laid out across the rest of the faucet repository. I think it's still better in terms of code organization to have them in a dedicated tests/´ folder, but happy to move them inside of the mint.rs` file directly if that's what we prefer.

Closes #192

EDITS

CI `action.yml` file changes

As part of this PR, I made changes to the action.yml file workflow to make sure that it references all crate, file and directory names correctly (since some have been renamed). Checking these changes for accuracy is still pending. I have outlined those changes in the following comment: #196 (comment)

Request Struct exports

As outlined in the following comment, the PR also changes the faucet-operator to export request structs that are used by the faucet-client for making requests to a faucet: #196 (comment)

Binary refactoring

The new mint command is implemented inside of a dedicated binary called miden-faucet-client.

The two libraries will and are responsible for holding distinct logic:

miden-faucet: Existing miden-faucet binary.
miden-faucet-client: This one contains the mint logic (and any future logic we may want to add to interact with live faucets). Not sure if the naming is perfect, let me know if you have any other proposals!

This has been outlined in the following comment: #196 (comment)

Throughout the development of this PR, the faucet binary was temporarily renamed to miden-faucet-operator. However, after discussion with reviewers, we've reverted this change to maintain backward compatibility. The final implementation keeps the original miden-faucet binary name unchanged, while adding the new miden-faucet-client binary. This avoids unnecessary infrastructure changes and deployment work. See comment: #196 (comment)

lima-limon-inc

Overall looks good, I tested on my machine a couple of times* and managed to mint tokens, here's the midenscan link.

I think my main question is if whether encapsulate the functionality in a separate library and also a separate binary. Would love to hear other thoughts!

save for this small issue

lima-limon-inc · 2025-12-10T14:33:52Z

bin/faucet/src/main.rs

 mod api_key;
 mod frontend;
 mod logging;
+mod mint;


What if the mint functionality was implemented on a separate binary/crate, rather than adding it in the same binary as the other faucet utilities. Mainly since, minting/interacting and serving a faucet are fairly distinct from each other.

This was briefly mentioned in the original discussion, but what if the main bulk of the logic was implemented inside the faucet's library (or maybe even a separate, smaller library altogether) and then the actual command simply served as a wrapper to said library. I believe this library could potentially serve other uses in the future, besides minting.

What do you think?

I'm also tagging @TomasArrachea here.

What if the mint functionality was implemented on a separate binary/crate, rather than adding it in the same binary as the other faucet utilities. Mainly since, minting/interacting and serving a faucet are fairly distinct from each other.

Completely agree, I was going to suggest the same thing

I imagine the split along the lines of: miden-faucet-{operator/admin/setup} and miden-faucet-client (names TBD)

Yeah I think that could make sense. How would you go about naming that library, especially since you said it could serve other use cases too?

Yeah I think that could make sense. How would you go about naming that library, especially since you said it could serve other use cases too?

Great question, my first instinct was going with miden-faucet-client since it would contain the "client side" logic; but maybe people who are more involved with the faucet have better insight.

Will code out the split!

lima-limon-inc · 2025-12-10T14:57:40Z

bin/faucet-client/src/mint.rs

+            .await?;
+
+        println!("Mint request accepted. Transaction: {}", minted_note.tx_id);
+        println!("Public P2ID note commitment: {}", minted_note.note_id.to_hex());


Just a heads up (related to @igamigo comment); midenup will probably need a way to communicate values in between binaries that are run in succession.
In this case, the minted note's ID will need to be passed down to the subsequent miden-client consume-notes call.

My first guess would be to pipe specific values in between binaries, but it's not yet defined.

Like I said, just a heads up.

Thanks for bringing this to my attention. I think we should definitely think about that within the scope of this PR too, as it may have implications here.

I will work on adding functionality for the multi-command single aliases on midenup, I think while doing that we may want to standardize how midenup communicates between other binaries.

lima-limon-inc · 2025-12-10T15:17:31Z

bin/faucet-operator/src/mint.rs

+    /// Amount to mint (in base units).
+    #[arg(short = 'm', long = "amount", value_name = "U64")]
+    amount: u64,


Extremely minor nit, but what if instead of amount we used the word quantity as a flag? In order to have distinct short form versions of the command.

This would enable the use of -a for Account and -q for Quantity instead of -m for aMount.

"Amount" could be left as an alias as to follow tradition, like so:

Suggested change

/// Amount to mint (in base units).

#[arg(short = 'm', long = "amount", value_name = "U64")]

amount: u64,

/// Quantity to mint (in base units).

#[arg(short = 'q', long = "quantity", value_name = "U64", alias = "amount")]

quantity: u64,

With this, both amount and quantity would both work (although the "amount" alias would be hidden).

Like I said, it's just a small suggestion/nit. Especially if -m is used elsewhere, then by all means ignore this comment.

Yeah I think that's a good idea to avoid using -m, will add this!

lima-limon-inc · 2025-12-10T15:18:43Z

bin/faucet-client/src/mint.rs

+/// Response from the `/pow` endpoint.
+#[derive(Debug, Deserialize, Serialize, Clone)]
+struct PowResponse {
+    challenge: String,
+    target: u64,
+}
+
+/// Response from the `/get_tokens` endpoint.
+#[derive(Debug, Deserialize, Serialize, Clone)]
+struct GetTokensResponse {
+    note_id: String,
+    tx_id: String,
+}


If we follow the path of creating a new separate library, then maybe these structs could go there as well.

lima-limon-inc · 2025-12-10T15:29:16Z

bin/faucet-client/src/mint.rs

+fn parse_account_id(input: &str) -> Result<AccountId, MintClientError> {
+    if input.starts_with("0x") {
+        AccountId::from_hex(input)
+            .map_err(|err| MintClientError::InvalidAccount(input.to_owned(), err.to_string()))
+    } else {
+        Address::decode(input)
+            .map_err(|err| MintClientError::InvalidAccount(input.to_owned(), err.to_string()))
+            .and_then(|(_, address)| match address.id() {
+                AddressId::AccountId(account_id) => Ok(account_id),
+                _ => Err(MintClientError::InvalidAccount(
+                    input.to_owned(),
+                    "address is not account-based".to_owned(),
+                )),
+            })
+    }
+}


I just tried executing the mint command without passing 0x and got the following error:

$~ miden-faucet mint --amount 88 --account 84384f2e124c0490458bf6d899503f Error: invalid account `84384f2e124c0490458bf6d899503f`: failed to decode bech32 string into an address

Having said that, the following patch does work on my machine:

Suggested change

fn parse_account_id(input: &str) -> Result<AccountId, MintClientError> {

if input.starts_with("0x") {

AccountId::from_hex(input)

.map_err(|err| MintClientError::InvalidAccount(input.to_owned(), err.to_string()))

} else {

Address::decode(input)

.map_err(|err| MintClientError::InvalidAccount(input.to_owned(), err.to_string()))

.and_then(|(_, address)| match address.id() {

AddressId::AccountId(account_id) => Ok(account_id),

_ => Err(MintClientError::InvalidAccount(

input.to_owned(),

"address is not account-based".to_owned(),

)),

})

}

}

let account_id = if !input.starts_with("0x") {

format!("0x{input}")

} else {

String::from(input)

};

AccountId::from_hex(&account_id)

.map_err(|err| MintClientError::InvalidAccount(input.to_owned(), err.to_string()))

Does that suffice? This also removes the need to import Address and AddressId I believe.

The exact code you provided will not work anymore for bech32 account IDs. We can combine your proposed check with the current function. The "0x" check exists to differentiate the account ID from a bech32 string and hex format.

I borrowed this logic from the miden-client utils. As I mentioned in the PR description, I think we may want to consider moving it to miden-base, since both this repository and the miden-client use it.

Nevertheless, if we do want to change the function to support hex strings without a "0x" prefix, I think we should also change the logic in the miden-client helper, since it also applies there.

@mmagician Would love to hear your thoughts on this!

implementing TryFrom<String> for AccountId would be a good addition to miden-base

Keinberger · 2025-12-11T16:57:10Z

Hey everyone, I made a commit to address the binary split that was discussed above. Now the repository contains two disticnt binaries:

miden-faucet-operaotr: This one holds the existing miden-client logic.
miden-faucet-client: This one contains the mint logic (and any future logic we may want to add). Not sure if the naming is perfect, let me know if you have any other proposals!

Remaining open questions:

There is a helper function that I implemented here: I borrowed this helper function from the code present at the miden-client repository. Since both miden-client and miden-faucet will now use the same logic, I think it might make sense to include that function in miden-base so that both repositories can import it from there. Let me know about your thoughts! If we want to propose changes to this function and decide to move it to miden-base, I think we should implement the "changed" function there.
Since this is being merged onto next, will this command only be included at v13? I want this command to be included as soon as possible, would a merge against main be the right approach?

mmagician · 2025-12-12T12:59:26Z

Cargo.toml

@@ -1,5 +1,5 @@
 [workspace]
-members = ["bin/faucet", "crates/faucet"]
+members = ["bin/faucet", "bin/faucet-operator", "crates/faucet"]


I'd rename the directories too, to align with operator - client split

Absolutely agree, I implemented that just now!

mmagician · 2025-12-12T13:00:54Z

README.md


 ```bash
-miden-faucet init \
+miden-faucet-client init \


this is for the operator, no?

hmm I see, my idea was the opposite, i.e. keeping the current binary as the operator/admin binary, and adding a new client binary.

cc @lima-limon-inc

Sorry for misreading your guys's comment. I changed the naming to be what you guys proposed.

mmagician · 2025-12-12T13:05:20Z

README.md

+Requesting tokens from a faucet endpoint is handled by the separate `miden-faucet-operator` binary:
+```bash


So this (in and other places) would be reversed

Absolutely agree, I refactored the markdown documentation to adjust for that.

mmagician · 2025-12-12T13:06:35Z

bin/faucet-client/src/mint.rs

@@ -0,0 +1,309 @@
+//! CLI command to mint tokens from a remote faucet by solving its `PoW` challenge.


technically this is not minting, because the faucet only has mint capability exposed to the faucet owner. Rather, I'd say "requesting"

this makes me wonder whether we should update not just the docs, but the name of the command itself

Although I do agree that "requesting" is more technically accurate, I think it would be less intuitive for users, also I think coming up with a good name for that CLI command is harder, i.e. request-asset?

Although I do agree that "requesting" is more technically accurate, I think it would be less intuitive for users, also I think coming up with a good name for that CLI command is harder, i.e. request-asset?

I agree with mint being both more intuitive and nicer in the CLI.
In this case, let's make sure that the accurate description is reflected in the docs, i.e. we write that it's not technically a mint.

mmagician · 2025-12-12T13:20:58Z

bin/faucet-client/src/mint.rs

+fn parse_account_id(input: &str) -> Result<AccountId, MintClientError> {
+    if input.starts_with("0x") {
+        AccountId::from_hex(input)
+            .map_err(|err| MintClientError::InvalidAccount(input.to_owned(), err.to_string()))
+    } else {
+        Address::decode(input)
+            .map_err(|err| MintClientError::InvalidAccount(input.to_owned(), err.to_string()))
+            .and_then(|(_, address)| match address.id() {
+                AddressId::AccountId(account_id) => Ok(account_id),
+                _ => Err(MintClientError::InvalidAccount(
+                    input.to_owned(),
+                    "address is not account-based".to_owned(),
+                )),
+            })
+    }
+}


implementing TryFrom<String> for AccountId would be a good addition to miden-base

Keinberger · 2025-12-12T16:01:50Z

Hey guys, so I did another round of refactoring:

I changed the base of this PR to be main instead of next, as we are planning to get this into a patch release.
I reversed the naming for the miden-faucet-client and miden-faucet-operator libraries, to fit the naming scheme both of you were originally thinking about and mentioned here: feat: implement mint command and rename binaries #196 (comment)

bobbinth

Looks good! Thank you! Not a full review, but I left some comments inline.

CHANGELOG.md

bin/faucet-operator/Cargo.toml

bobbinth · 2025-12-15T08:04:00Z

bin/faucet-operator/README.md

Should we make some minor changes in this file to add the "operator" terminology?

Agreed, I will make it clear in the README that the faucet comes with two distinct binaries, and explain the purpose of each of those.

Makefile

bobbinth · 2025-12-15T08:08:52Z

README.md

+Requesting tokens from a faucet endpoint is handled by the separate `miden-faucet-client` binary:
+```bash
+miden-faucet-client mint --url <FAUCET_API_URL> --account <ACCOUNT_ID> --amount <BASE_UNITS>
+```


It feels like maybe this deserves its own small sub-section.

Agreed! I will implement a sub-section

bobbinth · 2025-12-15T08:10:11Z

docs/src/getting-started/quick-start.md

 ## Step 3: Request Test Tokens

-Once the faucet is running, you can request test tokens through either the web interface or the REST API.
+Once the faucet is running, you can request test tokens through either the web interface, the operator CLI, or the REST API.


nit: should "operator CLI" actually be "client CLI"?

I think these are still leftovers from #196 (comment)

Yes, sorry this is still a leftover from my last refactoring. Will go through the docs files again to make sure that everything is named correctly!

bin/faucet-client/Cargo.toml

docs/src/getting-started/cli.md

bobbinth · 2025-12-15T08:18:34Z

docs/src/getting-started/cli.md

+To request tokens from a remote faucet, use the client mint CLI:
+```bash
+miden-faucet-client mint --url <FAUCET_API_URL> --account <ACCOUNT_ID> --amount <BASE_UNITS>
+```


It feels like this should be in a separate small section. Also, we should mention somewhere closer to the top that there are actually two separate binaries.

Absolutely agreed, will add that and amend that!

mmagician · 2025-12-15T08:53:06Z

bin/faucet-client/src/mint.rs

@@ -0,0 +1,309 @@
+//! CLI command to mint tokens from a remote faucet by solving its `PoW` challenge.


Although I do agree that "requesting" is more technically accurate, I think it would be less intuitive for users, also I think coming up with a good name for that CLI command is harder, i.e. request-asset?

I agree with mint being both more intuitive and nicer in the CLI.
In this case, let's make sure that the accurate description is reflected in the docs, i.e. we write that it's not technically a mint.

docs/src/getting-started/cli.md

bin/faucet-client/src/mint.rs

mmagician

LGTM thanks!

feat: rename existing miden-faucet binary to miden-faucet-client docs: update docs to include information about new miden-faucet-operator binary chore: move tests of miden-faucet-operator binary into dedicated folder docs(README): update README for binary separation chore: update changelog

…ary installation

docs: update instructions to include correct client start command and mint command usage

…client (reverse naming)

fix(Makefile): install faucet instructions target correct binary docs(README): added explainer for binary split chore: removed redundant readme key in bin/faucet-client/Cargo.toml chore: amend description satement in bin/faucet-operator/Cargo.toml

docs: Clarify mint command technical accuracy

…ries feat: implement backwards compatibility for legacy "miden-faucet" CLI command

igamigo

LGTM! I think @sergerad should probably look into this as it changes some things in relation to how the faucet service was being set up before

packaging/faucet/postinst

sergerad

Approved but I think renaming faucet binary to faucet-operator has added work for no value. There will need to be a few small changes in the infrastructure repo following this PR also.

Keinberger · 2026-01-16T10:19:42Z

Approved but I think renaming faucet binary to faucet-operator has added work for no value. There will need to be a few small changes in the infrastructure repo following this PR also.

I'm happy to revert that change so that we keep the original naming the miden-faucet CLI binary, i.e. we would have the two following binaries:

miden-faucet
miden-faucet-client

@mmagician What are your thoughts on that?

@sergerad mentioned to me via Slack that you @igamigo would also be in favour of reverting the naming to the original, correct?

mmagician · 2026-01-16T10:54:57Z

we would have the two following binaries:

miden-faucet

miden-faucet-client

That works, sure 👍🏼 I think the important part is having the user-facing code under a -client prefix binary.

igamigo · 2026-01-16T11:15:23Z

we would have the two following binaries:

miden-faucet

miden-faucet-client

That works, sure 👍🏼 I think the important part is having the user-facing code under a -client prefix binary.

I agree!

…en-faucet

Keinberger · 2026-01-16T11:45:19Z

Alright, I went ahead and reverted the faucet binary name from miden-faucet-operator back to the original miden-faucet. This avoids unnecessary infrastructure changes. miden-faucet-client binary and all mint functionality remains unchanged.

mmagician

LGTM with a few leftover naming changes

CHANGELOG.md

docs/src/getting-started/installation.md

bin/faucet-client/src/main.rs

Co-authored-by: Marti <[email protected]>

igamigo · 2026-01-16T13:49:48Z

@Keinberger, this PR was merged to main, is the plan to patch release it? Could you do a PR to next bringing these commits (I think this PR was not squash & merged so it is probably multiple)? It seems likely that we'll need to change the target of 0xMiden/miden-client#1642 as well

Keinberger · 2026-01-19T12:26:59Z

@Keinberger, this PR was merged to main, is the plan to patch release it? Could you do a PR to next bringing these commits (I think this PR was not squash & merged so it is probably multiple)? It seems likely that we'll need to change the target of 0xMiden/miden-client#1642 as well

Correct, plan would be a patch release. I will do a PR on next to bring those commits onto next.

Sorry about forgetting to squash merge this... Won't happen again!

As for the target of 0xMiden/miden-client#1642 - why would we need to change it? If we do a patch release I suppose it also belongs on main first, or am I missing something?

Keinberger · 2026-01-19T12:28:21Z

FYI I'm also fine with merging everthing onto next and introduce the changes as part of v14, in case we are going to release v14 this week.

igamigo · 2026-01-19T14:21:43Z

As for the target of 0xMiden/miden-client#1642 - why would we need to change it? If we do a patch release I suppose it also belongs on main first, or am I missing something?

FYI I'm also fine with merging everthing onto next and introduce the changes as part of v14, in case we are going to release v14 this week.

No need to merge to main, we can just merge to next and release it on 0.14, and then use it here. Also, the plan is to release 0.14 within today and tomorrow, but it also depends on when the node is released (cc @Dominik1999)

Dominik1999 · 2026-01-19T14:30:39Z

It would be the next relase, v0.13, right?

The plan is to release v0.13 of the client tomorrow or Wednesday. This PR was already merged to main, right?

igamigo · 2026-01-19T14:33:17Z

Yes, I blindly said 0.14 but meant 0.13, sorry. This PR was merged to main but we need it on next for the release.

Brings mint command feature (#196) from main to next. Key changes: - Added new miden-faucet-client binary with mint command - Updated all documentation to use next's parameter conventions (api-bind-port, frontend-bind-port, no-frontend) - Moved mint feature to v0.13.0 in CHANGELOG (not patch release) - Regenerated Cargo.lock for next's dependencies Resolved conflicts: - Cargo.lock: Regenerated from scratch - docs/src/getting-started/quick-start.md: Used next's simplified parameters Note: Build requires miden-client compatibility fixes (separate work)

Keinberger requested a review from mmagician December 10, 2025 11:28

Keinberger self-assigned this Dec 10, 2025

Keinberger mentioned this pull request Dec 10, 2025

feat: add miden mint command 0xMiden/midenup#131

Open

lima-limon-inc reviewed Dec 10, 2025

View reviewed changes

Keinberger force-pushed the kbg/feat/mint-command branch 2 times, most recently from 171e1ee to 4c28193 Compare December 11, 2025 17:10

mmagician reviewed Dec 12, 2025

View reviewed changes

Keinberger force-pushed the kbg/feat/mint-command branch from a09ce2c to 5df3e72 Compare December 12, 2025 15:02

Keinberger changed the base branch from next to main December 12, 2025 15:02

Keinberger changed the title ~~feat: implement mint command~~ feat: implement mint command and rename binaries Dec 12, 2025

Keinberger force-pushed the kbg/feat/mint-command branch from d54a4a0 to 6c20237 Compare December 12, 2025 15:55

bobbinth requested a review from igamigo December 15, 2025 07:55

bobbinth reviewed Dec 15, 2025

View reviewed changes

mmagician reviewed Dec 15, 2025

View reviewed changes

Keinberger mentioned this pull request Dec 15, 2025

Implement from_str(s: &str) helper function for AccountId 0xMiden/miden-base#2180

Closed

mmagician approved these changes Dec 16, 2025

View reviewed changes

Keinberger added 12 commits December 16, 2025 13:21

feat: implement mint command

0e614ba

chore: update changelog

f5ce756

chore(Makefile): update Makefile to include miden-faucet-operator bin…

ede1df1

…ary installation

docs: update README to include correct client start command

06f1dd9

docs: update instructions to include correct client start command and mint command usage

feat: rename faucet to faucet-operator and faucet-operator to faucet-…

b26a008

…client (reverse naming)

chore(CHANGELOG): amend statement

5324f7c

fix(Makefile): install faucet instructions target correct binary docs(README): added explainer for binary split chore: removed redundant readme key in bin/faucet-client/Cargo.toml chore: amend description satement in bin/faucet-operator/Cargo.toml

chore: rename miden-faucet.service file

8b0a2c4

fix(docs): correct naming for miden-faucet binaries

735310e

docs: use correct api bind flag

9d81d0d

docs: Clarify mint command technical accuracy

feat: implement common response types across operator and client bina…

c04b641

…ries feat: implement backwards compatibility for legacy "miden-faucet" CLI command

docs: add README for miden-faucet-client binary

799ce95

mmagician mentioned this pull request Dec 22, 2025

feat: support multiple commands and multiple binaries in aliases 0xMiden/midenup#130

Draft

Keinberger mentioned this pull request Jan 7, 2026

feat: implement CliClient 0xMiden/miden-client#1642

Merged

igamigo approved these changes Jan 12, 2026

View reviewed changes

packaging/faucet/postinst Show resolved Hide resolved

Keinberger requested review from sergerad and removed request for lima-limon-inc January 13, 2026 06:20

sergerad approved these changes Jan 15, 2026

View reviewed changes

chore(faucet): revert binary rename from miden-faucet-operator to mid…

4fee953

…en-faucet

mmagician approved these changes Jan 16, 2026

View reviewed changes

CHANGELOG.md Outdated Show resolved Hide resolved

docs/src/getting-started/installation.md Outdated Show resolved Hide resolved

bin/faucet-client/src/main.rs Outdated Show resolved Hide resolved

Keinberger and others added 3 commits January 16, 2026 13:57

Update CHANGELOG.md

3874b6e

Co-authored-by: Marti <[email protected]>

Update bin/faucet-client/src/main.rs

b5b483c

Co-authored-by: Marti <[email protected]>

Update docs/src/getting-started/installation.md

2c1c2bd

Co-authored-by: Marti <[email protected]>

Keinberger merged commit d65d61d into main Jan 16, 2026
14 checks passed

Keinberger deleted the kbg/feat/mint-command branch January 16, 2026 12:25

Keinberger mentioned this pull request Jan 19, 2026

chore: merge main into next #211

Closed

Keinberger mentioned this pull request Jan 19, 2026

chore: merge main into next #212

Merged

This was referenced Jan 28, 2026

fix: Update "miden mint" alias to use miden-faucet-client 0xMiden/midenup#138

Open

Add mint CLI command #192

Closed

		Requesting tokens from a faucet endpoint is handled by the separate `miden-faucet-operator` binary:
		```bash

		@@ -0,0 +1,309 @@
		//! CLI command to mint tokens from a remote faucet by solving its `PoW` challenge.

feat: implement mint command and rename binaries #196

feat: implement mint command and rename binaries #196

Uh oh!

Conversation

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

Uh oh!

Summary

Usage

Open Questions

EDITS

CI action.yml file changes

Request Struct exports

Binary refactoring

Uh oh!

lima-limon-inc left a comment • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

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

Uh oh!

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Keinberger commented Dec 12, 2025

Uh oh!

bobbinth left a comment

Keinberger commented Dec 10, 2025 •

edited

Loading

CI `action.yml` file changes

lima-limon-inc left a comment •

edited

Loading

Keinberger commented Dec 11, 2025 •

edited

Loading

Keinberger Dec 15, 2025 •

edited

Loading