# S9pk updated, registry still shows old version after 2+ days

**URL:** <https://community.start9.com/t/s9pk-updated-registry-still-shows-old-version-after-2-days/5644>\
**Category:** Services Support\
**Created:** [August 25, 2026, 3:02pm UTC](https://community.start9.com/t/s9pk-updated-registry-still-shows-old-version-after-2-days/5644 "2026-08-25T15:02:23Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![jos](https://community.start9.com/letter_avatar_proxy/v4/letter/j/2bfe46/32.png) [@jos](https://community.start9.com/u/jos)\
**Post date:** [August 25, 2026, 3:02pm UTC](https://community.start9.com/t/s9pk-updated-registry-still-shows-old-version-after-2-days/5644/1 "2026-08-25T15:02:24Z")

</div>

Right now for Bisq, StartOS package quickly updated to the Upstream version 1.10.6:0 over 2 days ago. Community Registry still shows previous version 1.10.5:0

StartOS package [https://github.com/Start9-Community/bisq-startos](https://github.com/Start9-Community/bisq-startos)

Any way to refresh/force the update on the Registry? Want to avoid having to download the .s9pk file?

StartOS 0.4.0 has been fantastic. Thank you!

---

<div class="post-metadata">

**Author:** ![Rexter](https://community.start9.com/user_avatar/community.start9.com/rexter/32/371_2.png) [@Rexter](https://community.start9.com/u/Rexter)\
**Post date:** [August 25, 2026, 10:35pm UTC](https://community.start9.com/t/s9pk-updated-registry-still-shows-old-version-after-2-days/5644/2 "2026-08-25T22:35:32Z")

</div>

Bisq 1.10.6 is in the community beta registry. It will get released to the Community registry when the package maintainer feels it’s been tested adequately. There is no real downside to side-loading, if you want to participate in testing.