Prepare release v0.6.0 (#421)

Author: mlange-42

CHANGELOG.md

@@ -1,6 +1,6 @@
 # Changelog
 
-## [[unpublished]](https://github.com/mlange-42/ark/compare/v0.5.2...main)
+## [[v0.6.0]](https://github.com/mlange-42/ark/compare/v0.5.2...v0.6.0)
 
 ### Breaking changed
 

README.md

@@ -24,6 +24,7 @@ Ark is an archetype-based [Entity Component System](https://en.wikipedia.org/wik
 - Designed for performance and highly optimized. See the [Benchmarks](https://mlange-42.github.io/ark/benchmarks/).
 - Well-documented, type-safe [API](https://pkg.go.dev/github.com/mlange-42/ark), and a comprehensive [User guide](https://mlange-42.github.io/ark/).
 - [Entity relationships](https://mlange-42.github.io/ark/relations/) as a first-class feature.
+- Extensible [event system](https://mlange-42.github.io/ark/events/) with filtering and custom event types.
 - Fast [batch operations](https://mlange-42.github.io/ark/batch/) for mass manipulation.
 - No systems. Just queries. Use your own structure (or the [Tools](https://github.com/mlange-42/ark#tools)).
 - World serialization and deserialization with [ark-serde](https://github.com/mlange-42/ark-serde).

benchmark/table/main.go

@@ -10,7 +10,7 @@ import (
 	"github.com/mlange-42/ark/benchmark"
 )
 
-const version = "v0.5.3-dev"
+const version = "v0.6.0"
 const goVersion = "1.25.1"
 
 func main() {

docs/content/_index.md

@@ -50,6 +50,7 @@ Ark is an archetype-based [Entity Component System](https://en.wikipedia.org/wik
 - Designed for performance and highly optimized. See the [Benchmarks](https://mlange-42.github.io/ark/benchmarks/).
 - Well-documented, type-safe [API](https://pkg.go.dev/github.com/mlange-42/ark), and a comprehensive [User guide](https://mlange-42.github.io/ark/).
 - [Entity relationships](https://mlange-42.github.io/ark/relations/) as a first-class feature.
+- Extensible [event system](https://mlange-42.github.io/ark/events/) with filtering and custom event types.
 - Fast [batch operations](https://mlange-42.github.io/ark/batch/) for mass manipulation.
 - No systems. Just queries. Use your own structure (or the [Tools](https://github.com/mlange-42/ark#tools)).
 - World serialization and deserialization with [ark-serde](https://github.com/mlange-42/ark-serde).

docs/content/cheatsheet/index.md

@@ -212,10 +212,6 @@ API: {{< api ecs Resource >}}, {{< api ecs Resource.Get >}}
 
 {{< details-buttons group="events" >}}
 
-> [!NOTE]
-> This feature is not yet released and is planned for Ark v0.6.0.
-> You can try it out on the `main` branch.
-
 Observers allow to react to ECS lifecycle events, like entity creation or component addition.
 
 {{% details closed="true" group="events" title="👀 **Create and register** observers for ECS lifecycle events" %}}

docs/content/design/index.md

@@ -69,10 +69,6 @@ The **number of entities** alive at any one time is limited to just under 5 bill
 
 Ark is **not thread-safe**. This design choice avoids internal locking mechanisms, which would introduce overhead and complexity. In scientific modeling, where large numbers of simulations are often executed in parallel, this approach is more efficient and scalable.
 
-> [!NOTE]
-> The following feature is not yet released and is planned for Ark v0.6.0.
-> You can try it out on the `main` branch.
-
 **Concurrent query execution** is yet possible if the queries don't access the same entities concurrently.
 For example, [entity relationships](../relations/) can be used to split up entities
 of the same archetype to process them in parallel.

docs/content/events/index.md

@@ -4,10 +4,6 @@ type = "docs"
 weight = 80
 description = "Ark's event system and observers."
 +++
-> [!NOTE]
-> This feature is not yet released and is planned for Ark v0.6.0.
-> You can try it out on the `main` branch.
-
 Ark provides an event system with observers that allow an application to react on events,
 such as adding and removing components and entities.
 

docs/content/queries/index.md

@@ -108,10 +108,6 @@ However, this is rarely required as (registered) filters are usually used over a
 
 ## Parallel queries
 
-> [!NOTE]
-> This feature is not yet released and is planned for Ark v0.6.0.
-> You can try it out on the `main` branch.
-
 Ark in general is not thread-safe (see chapter [Design](../design/), section [Limitations](../design#limitations)).
 However, it is possible to execute queries in parallel.
 This is especially useful for two scenarios: