Skip to content

Releases: kinode-dao/kinode

Beta 0.8.2

05 Jul 19:37
4eae051
Compare
Choose a tag to compare
Screenshot 2024-05-08 at 2 38 11 PM

A patch release. Contains updates to various key dependencies, terminal fixes, app store UI fixes, improvements to terminal scripting, changes to the top script, critical fixes for capabilities management.

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.1...v0.8.2

v0.8.1

11 Jun 22:41
3719ab3
Compare
Choose a tag to compare
Screenshot 2024-05-08 at 2 38 11 PM

A patch release. Contains UI fixes and networking-configuration fixes that allow hosted nodes to upgrade and operate smoothly. Please see the 0.8.0 release notes for more details.

For Developers: Apps that worked on 0.7.x will continue to work on 0.8.x. However, the eth:distro:sys and net:distro:sys APIs have had breaking changes, and the kinode_process_lib library functions to interact with them are outdated. In order to use these APIs with kinode_process_lib, you must upgrade to that library's 0.8.0 release. When you do this, you must update your program to use wit-bindgen = "0.24.0" and, in the metadata.json file for your package, add the field "wit_version": 0 in the properties object. Packages that do not specify a wit_version will default to 0.7. Packages signaling version 0 will use the current wit version, 0.8. This version will be incremented with every future wit change.

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.0...v0.8.1

Beta 0.8.0

10 Jun 00:52
577ca64
Compare
Choose a tag to compare
Screenshot 2024-05-08 at 2 38 11 PM

A new release! Since we are still pre-1.0, this minor release contains breaking changes from 0.7.4. However, nodes that upgrade to 0.8.0 will still be able to safely communicate with older nodes. The networking protocol has been rewritten to operate on multiple protocols, but older nodes that only use the WebSockets version of the protocol will still work.

Upgrading should also be seamless. You can safely boot an older node with this release.

However, in order to take advantage of the new networking TCP implementation, you must reset your Node ID onchain. You can do this by rebooting the node and choosing "reset node" instead of logging in.

For Developers: Apps that worked on 0.7.x will continue to work on 0.8.0. However, the eth:distro:sys and net:distro:sys APIs have had breaking changes, and the kinode_process_lib library functions to interact with them are outdated. In order to use these APIs with kinode_process_lib, you must upgrade to that library's 0.8.0 release. When you do this, you must update your program to use wit-bindgen = "0.24.0" and, in the metadata.json file for your package, add the field "wit_version": 0 in the properties object. Packages that do not specify a wit_version will default to 0.7. Packages signaling version 0 will use the current wit version, 0.8. This version will be incremented with every future wit change.

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

New Contributors

Full Changelog: v0.7.4...v0.8.0

Beta 0.7.4

15 May 03:33
fc63322
Compare
Choose a tag to compare
Screenshot 2024-05-08 at 2 38 11 PM

Contains an important set of fixes for the app store UI.

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

For developers, make sure to follow the instructions for 0.7.0 if upgrading from 0.6.x or earlier: https://github.com/kinode-dao/kinode/releases/tag/v0.7.0

What's Changed

Full Changelog: v0.7.3...v0.7.4

Beta 0.7.3

14 May 17:53
eec1581
Compare
Choose a tag to compare
Screenshot 2024-05-08 at 2 38 11 PM

Contains an important bugfix for the ETH provider runtime module and a number of frontend improvements.

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
For developers, make sure to follow the instructions for 0.7.0 if upgrading from 0.6.x or earlier: https://github.com/kinode-dao/kinode/releases/tag/v0.7.0

What's Changed

Full Changelog: v0.7.2...v0.7.3

Beta 0.7.2

08 May 21:37
4637b1f
Compare
Choose a tag to compare
Screenshot 2024-05-08 at 2 38 11 PM

Contains the usual bugfixes, and a large improvement to the node user interface.

The homepage and app store frontends have been redone, adding the ability to create and use "widgets". We've also added a "system settings" page, still rough around the edges, but useful for debugging in beta.

To showcase widgets, we've added one for the app store and one to display recent news from kinode.org.

Simulation mode (fake nodes) have also been overhauled, including a new networking strategy and the ability to work against a fake local EVM chain. This is quite useful in conjunction with recent updates to kit.

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

For developers, make sure to follow the instructions for 0.7.0 if upgrading from 0.6.x or earlier: https://github.com/kinode-dao/kinode/releases/tag/v0.7.0

What's Changed

Full Changelog: v0.7.1...v0.7.2

v0.7.1

01 May 17:23
5504f2a
Compare
Choose a tag to compare

Contains bugfixes and frontend improvements.

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

For developers, make sure to follow the instructions for 0.7.0 if upgrading from 0.6.x or earlier: https://github.com/kinode-dao/kinode/releases/tag/v0.7.0

What's Changed

Full Changelog: v0.7.0...v0.7.1

Beta 0.7.0

18 Apr 17:10
b699f3f
Compare
Choose a tag to compare

7th major alpha/beta release.

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

For this update, process devs with existing processes are recommended to:

  1. Bump process_lib import:
    process_lib = { git = "https://github.com/kinode-dao/process_lib.git", tag = "v0.6.1" }
    
  2. Bump wit-bindgen:
    wit-bindgen = "0.24.0"
    
  3. Use the newest kit:
    kit update
    
  4. Change the wit_bindgen::generate!() call to remove the exports field:
    wit_bindgen::generate!({
         path: "wit",
         world: "process",
    });
    
  5. If not using call_init!(), add export!() macro call:
    export!(Component);
    

What's Changed

New Contributors

Full Changelog: v0.6.2...v0.7.0

Beta 0.6.2

02 Apr 19:02
1d8c6d5
Compare
Choose a tag to compare

Small fixes related to hostable nodes and registration frontend.

Boot instructions have not changed, but can now use the --ws-routing port to enforce a given port for the websockets-based networking protocol.

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

For most purposes, you should be booting a testnet node on ETH Sepolia:

./kinode home/mynodename --testnet

Testnet nodes must use the --testnet flag on boot.

What's Changed

New Contributors

Full Changelog: v0.6.1...v0.6.2

Beta 0.6.1

18 Mar 14:38
1a3de8d
Compare
Choose a tag to compare
Beta 0.6.1 Pre-release
Pre-release

Bugfix release. Fixes some aspects of process exit behavior (more to be done here) and fixes dev workflow around booting fake nodes (--simulation-mode flag).

Boot instructions have not changed from the previous release:

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

For most purposes, you should be booting a testnet node on ETH Sepolia:

./kinode home/mynodename --testnet

Testnet nodes must use the --testnet flag on boot.

What's Changed

  • fix: kernel: do not reboot persisted processes if their OnExit behavior is None by @dr-frmr in #278
  • hotfix: use kit --features flag to pass simulation-mode and fix kit s by @nick1udwig in #279
  • hotfix: fix a bad merge by @nick1udwig in #280

Full Changelog: v0.6.0...v0.6.1