Releases: MostroP2P/mostro-cli
Release v0.14.4
Verifying the Release
In order to verify the release, you'll need to have gpg or gpg2 installed on your system. Once you've obtained a copy (and hopefully verified that as well), you'll first need to import the keys that have signed this release if you haven't done so already:
curl https://raw.githubusercontent.com/MostroP2P/mostro/main/keys/negrunch.asc | gpg --import
curl https://raw.githubusercontent.com/MostroP2P/mostro/main/keys/arkanoider.asc | gpg --importOnce you have the required PGP keys, you can verify the release (assuming manifest.txt.sig.negrunch, manifest.txt.sig.arkanoider and manifest.txt are in the current directory) with:
gpg --verify manifest.txt.sig.negrunch manifest.txt
gpg --verify manifest.txt.sig.arkanoider manifest.txt
gpg: Signature made fri 10 oct 2025 11:28:03 -03
gpg: using RSA key 1E41631D137BA2ADE55344F73852B843679AD6F0
gpg: Good signature from "Francisco Calderón <fjcalderon@gmail.com>" [ultimate]
gpg: Signature made fri 10 oct 2025 11:28:03 -03
gpg: using RSA key 2E986CA1C5E7EA1635CD059C4989CC7415A43AEC
gpg: Good signature from "Arkanoider <github.913zc@simplelogin.com>" [ultimate]
That will verify the signature of the manifest file, which ensures integrity and authenticity of the archive you've downloaded locally containing the binaries. Next, depending on your operating system, you should then re-compute the sha256 hash of the archive with shasum -a 256 <filename>, compare it with the corresponding one in the manifest file, and ensure they match exactly.
What's Changed in v0.14.4
🚀 Features
- feat: used helper to get admin key ( if needed ) in all requested functions by @arkanoider
- add admin key display in execute_admin_add_solver command by @AndreaDiazCorreia
- update admin key display message in take_dispute command by @AndreaDiazCorreia
- rename NSEC_PRIVKEY to ADMIN_NSEC for clarity by @AndreaDiazCorreia
- make NSEC_PRIVKEY optional, only required for admin commands by @AndreaDiazCorreia
💼 Other
- Update CHANGELOG for version 0.14.4 by @arkanoider
- refactor: Make ADMIN_NSEC optional and rename from NSEC_PRIVKEY by @arkanoider in #149
🚜 Refactor
- extract admin keys validation into helper function by @AndreaDiazCorreia
⚙️ Miscellaneous Tasks
- Release mostro-cli version 0.14.4 by @arkanoider
Contributors
- @arkanoider made their contribution
- @AndreaDiazCorreia made their contribution
Full Changelog: v0.14.3...v0.14.4
Release v0.14.3
Verifying the Release
In order to verify the release, you'll need to have gpg or gpg2 installed on your system. Once you've obtained a copy (and hopefully verified that as well), you'll first need to import the keys that have signed this release if you haven't done so already:
curl https://raw.githubusercontent.com/MostroP2P/mostro/main/keys/negrunch.asc | gpg --import
curl https://raw.githubusercontent.com/MostroP2P/mostro/main/keys/arkanoider.asc | gpg --importOnce you have the required PGP keys, you can verify the release (assuming manifest.txt.sig.negrunch, manifest.txt.sig.arkanoider and manifest.txt are in the current directory) with:
gpg --verify manifest.txt.sig.negrunch manifest.txt
gpg --verify manifest.txt.sig.arkanoider manifest.txt
gpg: Signature made fri 10 oct 2025 11:28:03 -03
gpg: using RSA key 1E41631D137BA2ADE55344F73852B843679AD6F0
gpg: Good signature from "Francisco Calderón <fjcalderon@gmail.com>" [ultimate]
gpg: Signature made fri 10 oct 2025 11:28:03 -03
gpg: using RSA key 2E986CA1C5E7EA1635CD059C4989CC7415A43AEC
gpg: Good signature from "Arkanoider <github.913zc@simplelogin.com>" [ultimate]
That will verify the signature of the manifest file, which ensures integrity and authenticity of the archive you've downloaded locally containing the binaries. Next, depending on your operating system, you should then re-compute the sha256 hash of the archive with shasum -a 256 <filename>, compare it with the corresponding one in the manifest file, and ensure they match exactly.
What's Changed in v0.14.3
🚀 Features
- committed cargo.toml with changelog.md by @arkanoider
- added local changelog.md file creation with cargo release by @arkanoider
🐛 Bug Fixes
- correct receiver of restore session message by @arkanoider
Contributors
- @arkanoider made their contribution
Full Changelog: v0.14.2...v0.14.3
Release v0.14.2
Verifying the Release
In order to verify the release, you'll need to have gpg or gpg2 installed on your system. Once you've obtained a copy (and hopefully verified that as well), you'll first need to import the keys that have signed this release if you haven't done so already:
curl https://raw.githubusercontent.com/MostroP2P/mostro/main/keys/negrunch.asc | gpg --import
curl https://raw.githubusercontent.com/MostroP2P/mostro/main/keys/arkanoider.asc | gpg --importOnce you have the required PGP keys, you can verify the release (assuming manifest.txt.sig.negrunch, manifest.txt.sig.arkanoider and manifest.txt are in the current directory) with:
gpg --verify manifest.txt.sig.negrunch manifest.txt
gpg --verify manifest.txt.sig.arkanoider manifest.txt
gpg: Signature made fri 10 oct 2025 11:28:03 -03
gpg: using RSA key 1E41631D137BA2ADE55344F73852B843679AD6F0
gpg: Good signature from "Francisco Calderón <fjcalderon@gmail.com>" [ultimate]
gpg: Signature made fri 10 oct 2025 11:28:03 -03
gpg: using RSA key 2E986CA1C5E7EA1635CD059C4989CC7415A43AEC
gpg: Good signature from "Arkanoider <github.913zc@simplelogin.com>" [ultimate]
That will verify the signature of the manifest file, which ensures integrity and authenticity of the archive you've downloaded locally containing the binaries. Next, depending on your operating system, you should then re-compute the sha256 hash of the archive with shasum -a 256 <filename>, compare it with the corresponding one in the manifest file, and ensure they match exactly.
What's Changed in v0.14.2
🚀 Features
- automatic update of child order in database when a range sale order is completed, no more errors on next flow. Still a bit trickier the buy range order thing by @arkanoider
- big refactor in all the cosmetics of mostro-cli interface with user by @arkanoider
- feat: beautified lot of terminal output (thanks cursor!) by @arkanoider
🐛 Bug Fixes
- fixed from field in getdm command by @arkanoider
- removed one test related to HOME folder by @arkanoider
- clippy in gh actions fixes by @arkanoider
- tests now are ok fixed docs of code coverage by @arkanoider
- fix test for gh actions by @arkanoider
💼 Other
- Beautified lot of terminal output by @arkanoider in #146
- Merge commit 'a0aaaad2041709b1784cddb1b92b0e90450ad903' into terminal-beautify by @arkanoider
- Fix clippy errors by @grunch
- Merge commit '2a6d88f82ad5ebf59a2414be81cd8e819c5c3e6f' into terminal-beautify by @arkanoider
- Fix race condition by @grunch
- Adjust text to fir smaller screens by @grunch
- CodeRabbit Generated Unit Tests: Add 78 unit tests and comprehensive test documentation by @arkanoider in #147
- CodeRabbit Generated Unit Tests: Add 78 unit tests and comprehensive test documentation by @coderabbitai[bot]
⚙️ Miscellaneous Tasks
- Release mostro-cli version 0.14.2 by @arkanoider
- added arkanoide signature in manifest of releases by @arkanoider
- removed typo by @arkanoider
- fix fmt by @arkanoider
- some fixes on logs and added a check on take dispute to verify sender of the answer is mostro by @arkanoider
- fixed typo by @arkanoider
- typo on test number by @arkanoider
- fix fmt checks by @arkanoider
- fix in cargo.toml to remove openssl by @arkanoider
Contributors
- @arkanoider made their contribution
- @grunch made their contribution
- @coderabbitai[bot] made their contribution
Full Changelog: v0.14.1...v0.14.2
Release v0.14.1
Verifying the Release
In order to verify the release, you'll need to have gpg or gpg2 installed on your system. Once you've obtained a copy (and hopefully verified that as well), you'll first need to import the keys that have signed this release if you haven't done so already:
curl https://raw.githubusercontent.com/MostroP2P/mostro/main/keys/negrunch.asc | gpg --importOnce you have the required PGP keys, you can verify the release (assuming manifest.txt.sig and manifest.txt are in the current directory) with:
gpg --verify manifest.txt.sig manifest.txt
gpg: Firmado el jue 03 ago 2023 15:07:05 -03
gpg: usando RSA clave 1E41631D137BA2ADE55344F73852B843679AD6F0
gpg: Firma correcta de "Francisco Calderón <fjcalderon@gmail.com>" [absoluta]
That will verify the signature of the manifest file, which ensures integrity and authenticity of the archive you've downloaded locally containing the binaries. Next, depending on your operating system, you should then re-compute the sha256 hash of the archive with shasum -a 256 <filename>, compare it with the corresponding one in the manifest file, and ensure they match exactly.
What's Changed in v0.14.1
🐛 Bug Fixes
- reverted a rabbit fix for the moment to avoid breaking change by @arkanoider
⚙️ Miscellaneous Tasks
- Release mostro-cli version 0.14.1 by @arkanoider
Contributors
- @arkanoider made their contribution
Full Changelog: v0.14.0...v0.14.1
Release v0.14.0
Verifying the Release
In order to verify the release, you'll need to have gpg or gpg2 installed on your system. Once you've obtained a copy (and hopefully verified that as well), you'll first need to import the keys that have signed this release if you haven't done so already:
curl https://raw.githubusercontent.com/MostroP2P/mostro/main/keys/negrunch.asc | gpg --importOnce you have the required PGP keys, you can verify the release (assuming manifest.txt.sig and manifest.txt are in the current directory) with:
gpg --verify manifest.txt.sig manifest.txt
gpg: Firmado el jue 03 ago 2023 15:07:05 -03
gpg: usando RSA clave 1E41631D137BA2ADE55344F73852B843679AD6F0
gpg: Firma correcta de "Francisco Calderón <fjcalderon@gmail.com>" [absoluta]
That will verify the signature of the manifest file, which ensures integrity and authenticity of the archive you've downloaded locally containing the binaries. Next, depending on your operating system, you should then re-compute the sha256 hash of the archive with shasum -a 256 <filename>, compare it with the corresponding one in the manifest file, and ensure they match exactly.
What's Changed in v0.14.0
🚀 Features
- add rabbit fixes and improved other parts by @arkanoider
- improve error logging for gift wrap decryption and use admin pubkey for DM filtering by @AndreaDiazCorreia
- fixed some wrong key in decryption by @arkanoider
- improved reception logic and small fix for last trade index by @arkanoider
- feat: first testable mostro cli version with last_trade_index command to be tested by @arkanoider
- added correct since time calculation for get dm command - improved code readability for new order management in db.rs by @arkanoider
- add invalid fiat currency managed by @arkanoider
- improving parsing functions by @arkanoider
- update order status to disputed after initiating dispute by @AndreaDiazCorreia
- add handling for user-initiated dispute actions in message handler by @AndreaDiazCorreia
- created ci.yml also in mostro-cli by @arkanoider
🐛 Bug Fixes
- completed merge of pr and fixed conflicts by @arkanoider
- moved some logic parts in wait dm function to avoid issues with unresponsive relays by @arkanoider
- added a check to avoid UNIQUE constraint error - now if an order is yet present in db we do an UPDATE sql and not INSERT by @arkanoider
- some fixes on message management by @arkanoider
- use Status enum instead of hardcoded string for dispute status by @AndreaDiazCorreia
💼 Other
- refactor: Split big utils.rs file in a module for being more usable by @arkanoider in #145
- Fix timeout error when initiating disputes by @arkanoider in #142
- Merge branch 'main' into fix/issue-141 by @arkanoider
- fix: improve error messages in getadmindm gift wrap decryption by @arkanoider in #143
- Aligning message management by @arkanoider in #144
🚜 Refactor
- Split big utils.rs file in a module for being more usable by @arkanoider
⚙️ Miscellaneous Tasks
- fix typo by @arkanoider
- Release mostro-cli version 0.14.0 by @arkanoider
- typo removed by @arkanoider
- fix by rabbit by @arkanoider
- cargo fmt fix by @arkanoider
- small fix on README.md in command list by @arkanoider
- fix in README.md by @arkanoider
- fix for clippy gh actions by @arkanoider
- fix by rabbit by @arkanoider
- updateded README.md by @arkanoider
- fix on rabbit improvements by @arkanoider
- rabbit improvement by @arkanoider
- rabbit improvement by @arkanoider
- added trade index number printout in new order and take order commands by @arkanoider
- rabbit fixes by @arkanoider
- rabbit fixes by @arkanoider
- testing all patterns with new code by @arkanoider
- almost remove wait for dm function with fetch event by @arkanoider
- almost remove wait for dm function with fetch event by @arkanoider
- going on to uniform message fetching calls by @arkanoider
Contributors
- @arkanoider made their contribution
- @AndreaDiazCorreia made their contribution
Full Changelog: v0.13.6...v0.14.0
Release v0.13.6
Verifying the Release
In order to verify the release, you'll need to have gpg or gpg2 installed on your system. Once you've obtained a copy (and hopefully verified that as well), you'll first need to import the keys that have signed this release if you haven't done so already:
curl https://raw.githubusercontent.com/MostroP2P/mostro/main/keys/negrunch.asc | gpg --importOnce you have the required PGP keys, you can verify the release (assuming manifest.txt.sig and manifest.txt are in the current directory) with:
gpg --verify manifest.txt.sig manifest.txt
gpg: Firmado el jue 03 ago 2023 15:07:05 -03
gpg: usando RSA clave 1E41631D137BA2ADE55344F73852B843679AD6F0
gpg: Firma correcta de "Francisco Calderón <fjcalderon@gmail.com>" [absoluta]
That will verify the signature of the manifest file, which ensures integrity and authenticity of the archive you've downloaded locally containing the binaries. Next, depending on your operating system, you should then re-compute the sha256 hash of the archive with shasum -a 256 <filename>, compare it with the corresponding one in the manifest file, and ensure they match exactly.
What's Changed in v0.13.6
🚀 Features
- removed android build by @arkanoider
- remove deps of sqlx of openssl to avoid using it as dep in github actions by @arkanoider
🐛 Bug Fixes
- strict tag check on cliff.toml and tag fetch before git cliff by @arkanoider
- restored latest in git cliff by @arkanoider
- removed deps in rust.yml of protobuf and openssl by @arkanoider
- add openssl deps in gh actions by @arkanoider
- improved changelo to have correct file on release by @arkanoider
💼 Other
- Changelog fix by @arkanoider in #139
⚙️ Miscellaneous Tasks
- bumped release version by @arkanoider
- update changelog for v0.13.5 by @github-actions[bot]
Contributors
- @arkanoider made their contribution
- @github-actions[bot] made their contribution
Full Changelog: v0.13.5...v0.13.6
Release v0.13.5
Verifying the Release
In order to verify the release, you'll need to have gpg or gpg2 installed on your system. Once you've obtained a copy (and hopefully verified that as well), you'll first need to import the keys that have signed this release if you haven't done so already:
curl https://raw.githubusercontent.com/MostroP2P/mostro/main/keys/negrunch.asc | gpg --importOnce you have the required PGP keys, you can verify the release (assuming manifest.txt.sig and manifest.txt are in the current directory) with:
gpg --verify manifest.txt.sig manifest.txt
gpg: Firmado el jue 03 ago 2023 15:07:05 -03
gpg: usando RSA clave 1E41631D137BA2ADE55344F73852B843679AD6F0
gpg: Firma correcta de "Francisco Calderón <fjcalderon@gmail.com>" [absoluta]
That will verify the signature of the manifest file, which ensures integrity and authenticity of the archive you've downloaded locally containing the binaries. Next, depending on your operating system, you should then re-compute the sha256 hash of the archive with shasum -a 256 <filename>, compare it with the corresponding one in the manifest file, and ensure they match exactly.
What's Changed in v0.13.5
🚀 Features
- added a specific merge emoticons for PR merge to avoid confusion using the fallback to feat by @arkanoider
⚙️ Miscellaneous Tasks
- bump version to v.0.13.5 by @arkanoider
- update changelog for v0.13.4 by @github-actions[bot]
Contributors
- @arkanoider made their contribution
- @github-actions[bot] made their contribution
Full Changelog: v0.13.4...v0.13.5
Release v0.13.4
Verifying the Release
In order to verify the release, you'll need to have gpg or gpg2 installed on your system. Once you've obtained a copy (and hopefully verified that as well), you'll first need to import the keys that have signed this release if you haven't done so already:
curl https://raw.githubusercontent.com/MostroP2P/mostro/main/keys/negrunch.asc | gpg --importOnce you have the required PGP keys, you can verify the release (assuming manifest.txt.sig and manifest.txt are in the current directory) with:
gpg --verify manifest.txt.sig manifest.txt
gpg: Firmado el jue 03 ago 2023 15:07:05 -03
gpg: usando RSA clave 1E41631D137BA2ADE55344F73852B843679AD6F0
gpg: Firma correcta de "Francisco Calderón <fjcalderon@gmail.com>" [absoluta]
That will verify the signature of the manifest file, which ensures integrity and authenticity of the archive you've downloaded locally containing the binaries. Next, depending on your operating system, you should then re-compute the sha256 hash of the archive with shasum -a 256 <filename>, compare it with the corresponding one in the manifest file, and ensure they match exactly.
What's Changed in v0.13.4
🚀 Features
- fix: now users in changelog are links by @arkanoider in #138
🐛 Bug Fixes
- now users in changelog are links by @arkanoider
⚙️ Miscellaneous Tasks
- Release mostro-cli version 0.13.4 by @arkanoider
- update changelog for v0.13.3 by @github-actions[bot]
Contributors
- @arkanoider made their contribution
- @github-actions[bot] made their contribution
Full Changelog: v0.13.3...v0.13.4
Release v0.13.3
Verifying the Release
In order to verify the release, you'll need to have gpg or gpg2 installed on your system. Once you've obtained a copy (and hopefully verified that as well), you'll first need to import the keys that have signed this release if you haven't done so already:
curl https://raw.githubusercontent.com/MostroP2P/mostro/main/keys/negrunch.asc | gpg --importOnce you have the required PGP keys, you can verify the release (assuming manifest.txt.sig and manifest.txt are in the current directory) with:
gpg --verify manifest.txt.sig manifest.txt
gpg: Firmado el jue 03 ago 2023 15:07:05 -03
gpg: usando RSA clave 1E41631D137BA2ADE55344F73852B843679AD6F0
gpg: Firma correcta de "Francisco Calderón <fjcalderon@gmail.com>" [absoluta]
That will verify the signature of the manifest file, which ensures integrity and authenticity of the archive you've downloaded locally containing the binaries. Next, depending on your operating system, you should then re-compute the sha256 hash of the archive with shasum -a 256 <filename>, compare it with the corresponding one in the manifest file, and ensure they match exactly.
What's Changed in v0.13.3
🚀 Features
- Fixed wrong key in execute_admin_add_solver function by @arkanoider in #137
- improved changelog.md by @arkanoider
🐛 Bug Fixes
- cargo.toml version fixed by @arkanoider
- fixed wrong key in execute_admin_add_solver function by @arkanoider
🚜 Refactor
- added helper for all admin disputes commands by @arkanoider
⚙️ Miscellaneous Tasks
- Release mostro-cli version 0.13.3 by @arkanoider
- update changelog for v0.13.2 by @github-actions[bot]
Contributors
- @arkanoider made their contribution
- @github-actions[bot] made their contribution
Full Changelog: v0.13.2...v0.13.3
Release v0.13.2
Verifying the Release
In order to verify the release, you'll need to have gpg or gpg2 installed on your system. Once you've obtained a copy (and hopefully verified that as well), you'll first need to import the keys that have signed this release if you haven't done so already:
curl https://raw.githubusercontent.com/MostroP2P/mostro/main/keys/negrunch.asc | gpg --importOnce you have the required PGP keys, you can verify the release (assuming manifest.txt.sig and manifest.txt are in the current directory) with:
gpg --verify manifest.txt.sig manifest.txt
gpg: Firmado el jue 03 ago 2023 15:07:05 -03
gpg: usando RSA clave 1E41631D137BA2ADE55344F73852B843679AD6F0
gpg: Firma correcta de "Francisco Calderón <fjcalderon@gmail.com>" [absoluta]
That will verify the signature of the manifest file, which ensures integrity and authenticity of the archive you've downloaded locally containing the binaries. Next, depending on your operating system, you should then re-compute the sha256 hash of the archive with shasum -a 256 <filename>, compare it with the corresponding one in the manifest file, and ensure they match exactly.
What's Changed in v0.13.2
- Improving context by @arkanoider in #136
- small improvement on commands to try a merge by @arkanoider
- add username link parsing to changelog by @arkanoider
- update changelog for v0.13.1 by @github-actions[bot]
Full Changelog: v0.13.1...v0.13.2