Skip to content

Releases: kinode-dao/kinode

v0.9.4

26 Sep 18:10
db7a356
Compare
Choose a tag to compare
Kinode

Patch release with fixes and features:

fixes:

  • prompt user to sign password message while registering
  • add new wasi build target to README
  • upgrade kit
  • make globe widget more robust
  • app store UI fixes
  • make terminal logging finite and configurable

features:

  • new homepage design
  • persist user-set app ordering on homepage
  • better kernel errors

Additionally, the docs userspace app has been removed -- you can now find it for download on the App Store! Note that nodes which have already been booted with docs will keep the app, but it will no longer be bootstrapped into newly-created nodes.

Running the Binary

To run the binary, you must indicate where the home folder for the node will be. You may also optionally specify your HTTP port. The default if unspecified is the first free port at or above 8080. Here's an example:

./kinode home/mynodename

What's Changed

Full Changelog: v0.9.3...v0.9.4

v0.9.3

13 Sep 03:30
f7249da
Compare
Choose a tag to compare
Kinode

A patch release with a major improvement on open file handles as handled by the VFS. Also contains improvements to HTTP server path-binding, allowing processes to receive requests on subpaths even if they did not bind that exact path. Also contains terminal driver fixes allowing it to properly handle unicode characters. Lastly, we've updated the docs app to serve data dynamically, reducing node memory usage.

Running the Binary

To run the binary, you must indicate where the home folder for the node will be. You may also optionally specify your HTTP port. The default if unspecified is the first free port at or above 8080. Here's an example:

./kinode home/mynodename

What's Changed

  • http server: fall back to base process HTTP binding if unbound path is requested by @dr-frmr in #521
  • terminal: dont crash if no size by @nick1udwig in #529
  • make docs app serve http dynamically by @dr-frmr in #530
  • app_store: always respond with error; use process_macros by @nick1udwig in #522
  • terminal: refactor to use unicode graphemes properly, fix special character bugs by @dr-frmr in #528
  • vfs: cleanup on max_open_files threshold by @bitful-pannul in #533
  • Develop 0.9.3 by @dr-frmr in #523
  • update kit versions to latest, use crates.io for process_lib (fixes k… by @dr-frmr in #535
  • Release candidate 0.9.3 by @dr-frmr in #534

Full Changelog: v0.9.2...v0.9.3

v0.9.2

02 Sep 16:52
ba79acf
Compare
Choose a tag to compare
Kinode

A patch release. Contains fixes to frontends, fake node networking, and ETH provider.

Running the Binary

To run the binary, you must indicate where the home folder for the node will be. You may also optionally specify your HTTP port. The default if unspecified is the first free port at or above 8080. Here's an example:

./kinode home/mynodename

What's Changed

Full Changelog: v0.9.1...v0.9.2

v0.9.1

22 Aug 22:33
1b47e39
Compare
Choose a tag to compare
Kinode

A patch release. Contains fixes to reduce the number of ETH RPC requests to avoid overwhelming providers.

Running the Binary

To run the binary, you must indicate where the home folder for the node will be. You may also optionally specify your HTTP port. The default if unspecified is the first free port at or above 8080. Here's an example:

./kinode home/mynodename

What's Changed

Full Changelog: v0.9.0...v0.9.1

Beta 0.9.0

21 Aug 10:47
591a124
Compare
Choose a tag to compare
Kinode

Warning: this release spams ETH RPC requests. Please use 0.9.1 instead!

Since we are still pre-1.0, this release contains breaking changes from 0.8.7. Nodes running 0.9.0 will NOT be able to communicate with node running 0.8.?. This is because 0.9.0 uses a different smart contract, Kimap, to back the KNS protocol. The App Store now uses Kimap as well, so applications will need to be republished.

We strongly encourage you to upgrade local nodes to 0.9.0 as soon as possible. Upgrading should also be seamless. You can safely boot an older node with this release.

For Developers

Because we have migrated to a new smart contract, Kimap, you'll need to re-publish your packages. There are two flows that you'll be able to use:

  1. An updated version of the same App Store GUI flow you know and love from 0.8.x
  2. A new and shiny kit publish

Whichever you choose, we'll be hanging out in the Kinode Discord, so drop us a line if you run into issues

Running the Binary

To run the binary, you must indicate where the home folder for the node will be. You may also optionally specify your HTTP port. The default if unspecified is the first free port at or above 8080. Here's an example:

./kinode home/mynodename

What's Changed

Full Changelog: v0.8.7...v0.9.0

Beta 0.8.7

09 Aug 14:03
18f0eec
Compare
Choose a tag to compare
Screenshot 2024-05-08 at 2 38 11 PM

The last 0.8.x release. This fixes some final issues in the in-network ETH RPC provider protocol implementation, and improves the Dockerfile. Next up, 0.9.0!

To run the binary, you must indicate where the home folder for the node will be. You may also optionally specify your HTTP port. The default if unspecified is 8080. Here's an example:

./kinode home/mynodename

What's Changed

Full Changelog: v0.8.6...v0.8.7

Beta 0.8.6

19 Jul 15:11
09f6a34
Compare
Choose a tag to compare
Screenshot 2024-05-08 at 2 38 11 PM

Yet another daily bugfix release! This time, we have resolved a bug in certain SQLite queries and fixed a long-standing issue with node-to-node RPC providers.

To run the binary, you must indicate where the home folder for the node will be. You may also optionally specify your HTTP port. The default if unspecified is 8080. Here's an example:

./kinode home/mynodename

What's Changed

Full Changelog: v0.8.5...v0.8.6

Beta 0.8.5

18 Jul 19:02
66f8dd2
Compare
Choose a tag to compare
Screenshot 2024-05-08 at 2 38 11 PM

This release fixes two important bugs:

  • update kit version to properly build non-sim-mode
  • fix import-from-keyfile functionality on login/register

To run the binary, you must indicate where the home folder for the node will be. You may also optionally specify your HTTP port. The default if unspecified is 8080. Here's an example:

./kinode home/mynodename

What's Changed

Full Changelog: v0.8.4...v0.8.5

Beta 0.8.4

17 Jul 09:32
4123bd1
Compare
Choose a tag to compare
Screenshot 2024-05-08 at 2 38 11 PM

This quick release contains only a few changes, the first of critical importance:

  • Recently, infura RPC endpoints suddenly started rejecting subscriptions with a from_block parameter. We remove those from all subscription requests here
  • Increase the interval between blog-post-fetches in KinoUpdates widget
  • Update build script to be more effective at reloading packages

To run the binary, you must indicate where the home folder for the node will be. You may also optionally specify your HTTP port. The default if unspecified is 8080. Here's an example:

./kinode home/mynodename

What's Changed

Full Changelog: v0.8.3...v0.8.4

Beta 0.8.3

15 Jul 14:05
a155bfc
Compare
Choose a tag to compare
Screenshot 2024-05-08 at 2 38 11 PM

A patch release containing important bug fixes. Corrects login redirect behavior if browser does not have cookie. Fixes a security hole with capabilities. Fixes a booting bug with nodes that registered as indirect and then again as direct. Makes delete key behavior as expected by users.

To run the binary, you must indicate where the home folder for the node will be. You may also optionally specify your HTTP port. The default if unspecified is 8080. Here's an example:

./kinode home/mynodename

What's Changed

Full Changelog: v0.8.2...v0.8.3