chore: update changelog and release

packages/plugin-api/CHANGELOG.md

@@ -1,5 +1,13 @@
 # @wolfstar/plugin-api
 
+## 2.2.0
+
+### Minor Changes
+
+- [#259](https://github.com/wolfstar-project/plugins/pull/259) [`e9c503d`](https://github.com/wolfstar-project/plugins/commit/e9c503da60e60a732bc916250c0d875919a9714c) - Every module sets `meta.configKey`, so an application writes a module's options under its own top-level key of `stars.config` (`api`, `broker`, `cache`, `gateway`, `i18n`, `logger`, `scheduledTasks`, `sharder`, `subcommandsAdvanced`) instead of the `[specifier, options]` tuple of `modules`. The tuple still works and is merged over the key. The key is typed in `defineConfig` once the module is imported in `stars.config.ts`; `cache`, `gateway`, `sharder` and `subcommandsAdvanced` take no options yet and only reserve their name.
+
+  The `@wolfstar/kit` peer range moves from `^0.1.0` to `^0.2.0`, the first version that reads `configKey`, and `@wolfstar/schema` (`^0.9.0`) is a new optional peer that carries the `StarsConfig` type the keys extend. A project on `@wolfstar/kit` 0.1 has to update it.
+
 ## 2.1.1
 
 ### Patch Changes

packages/plugin-api/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@wolfstar/plugin-api",
-  "version": "2.1.1",
+  "version": "2.2.0",
   "description": "Plugin for @wolfstar/http-framework exposing a standalone REST API server (routes, middlewares, router)",
   "keywords": [
     "api",

packages/plugin-broker/CHANGELOG.md

@@ -1,5 +1,18 @@
 # @wolfstar/plugin-broker
 
+## 0.7.0
+
+### Minor Changes
+
+- [#259](https://github.com/wolfstar-project/plugins/pull/259) [`e9c503d`](https://github.com/wolfstar-project/plugins/commit/e9c503da60e60a732bc916250c0d875919a9714c) - Every module sets `meta.configKey`, so an application writes a module's options under its own top-level key of `stars.config` (`api`, `broker`, `cache`, `gateway`, `i18n`, `logger`, `scheduledTasks`, `sharder`, `subcommandsAdvanced`) instead of the `[specifier, options]` tuple of `modules`. The tuple still works and is merged over the key. The key is typed in `defineConfig` once the module is imported in `stars.config.ts`; `cache`, `gateway`, `sharder` and `subcommandsAdvanced` take no options yet and only reserve their name.
+
+  The `@wolfstar/kit` peer range moves from `^0.1.0` to `^0.2.0`, the first version that reads `configKey`, and `@wolfstar/schema` (`^0.9.0`) is a new optional peer that carries the `StarsConfig` type the keys extend. A project on `@wolfstar/kit` 0.1 has to update it.
+
+### Patch Changes
+
+- Updated dependencies [[`e9c503d`](https://github.com/wolfstar-project/plugins/commit/e9c503da60e60a732bc916250c0d875919a9714c)]:
+  - @wolfstar/plugin-cache@0.8.0
+
 ## 0.6.0
 
 ### Minor Changes

packages/plugin-broker/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@wolfstar/plugin-broker",
-  "version": "0.6.0",
+  "version": "0.7.0",
   "description": "Plugin for @wolfstar/http-framework distributing gateway events across processes over Redis Streams, with at-least-once delivery",
   "keywords": [
     "broker",

packages/plugin-cache/CHANGELOG.md

@@ -1,5 +1,13 @@
 # @wolfstar/plugin-cache
 
+## 0.8.0
+
+### Minor Changes
+
+- [#259](https://github.com/wolfstar-project/plugins/pull/259) [`e9c503d`](https://github.com/wolfstar-project/plugins/commit/e9c503da60e60a732bc916250c0d875919a9714c) - Every module sets `meta.configKey`, so an application writes a module's options under its own top-level key of `stars.config` (`api`, `broker`, `cache`, `gateway`, `i18n`, `logger`, `scheduledTasks`, `sharder`, `subcommandsAdvanced`) instead of the `[specifier, options]` tuple of `modules`. The tuple still works and is merged over the key. The key is typed in `defineConfig` once the module is imported in `stars.config.ts`; `cache`, `gateway`, `sharder` and `subcommandsAdvanced` take no options yet and only reserve their name.
+
+  The `@wolfstar/kit` peer range moves from `^0.1.0` to `^0.2.0`, the first version that reads `configKey`, and `@wolfstar/schema` (`^0.9.0`) is a new optional peer that carries the `StarsConfig` type the keys extend. A project on `@wolfstar/kit` 0.1 has to update it.
+
 ## 0.7.0
 
 ### Minor Changes

packages/plugin-cache/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@wolfstar/plugin-cache",
-  "version": "0.7.0",
+  "version": "0.8.0",
   "description": "Pluggable, storage-agnostic Discord entity cache (in-memory and Redis, with optional compression) for @wolfstar/plugin-gateway",
   "keywords": [
     "cache",

packages/plugin-gateway/CHANGELOG.md

@@ -1,5 +1,18 @@
 # @wolfstar/plugin-gateway
 
+## 0.16.0
+
+### Minor Changes
+
+- [#259](https://github.com/wolfstar-project/plugins/pull/259) [`e9c503d`](https://github.com/wolfstar-project/plugins/commit/e9c503da60e60a732bc916250c0d875919a9714c) - Every module sets `meta.configKey`, so an application writes a module's options under its own top-level key of `stars.config` (`api`, `broker`, `cache`, `gateway`, `i18n`, `logger`, `scheduledTasks`, `sharder`, `subcommandsAdvanced`) instead of the `[specifier, options]` tuple of `modules`. The tuple still works and is merged over the key. The key is typed in `defineConfig` once the module is imported in `stars.config.ts`; `cache`, `gateway`, `sharder` and `subcommandsAdvanced` take no options yet and only reserve their name.
+
+  The `@wolfstar/kit` peer range moves from `^0.1.0` to `^0.2.0`, the first version that reads `configKey`, and `@wolfstar/schema` (`^0.9.0`) is a new optional peer that carries the `StarsConfig` type the keys extend. A project on `@wolfstar/kit` 0.1 has to update it.
+
+### Patch Changes
+
+- Updated dependencies [[`e9c503d`](https://github.com/wolfstar-project/plugins/commit/e9c503da60e60a732bc916250c0d875919a9714c)]:
+  - @wolfstar/plugin-cache@0.8.0
+
 ## 0.15.0
 
 ### Minor Changes

packages/plugin-gateway/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@wolfstar/plugin-gateway",
-  "version": "0.15.0",
+  "version": "0.16.0",
   "description": "Gateway (WebSocket) support for @wolfstar/http-framework: a GatewayClient emitting Structures, backed by a pluggable cache",
   "keywords": [
     "discord",

packages/plugin-i18next/CHANGELOG.md

@@ -1,5 +1,13 @@
 # @wolfstar/plugin-i18next
 
+## 2.3.0
+
+### Minor Changes
+
+- [#259](https://github.com/wolfstar-project/plugins/pull/259) [`e9c503d`](https://github.com/wolfstar-project/plugins/commit/e9c503da60e60a732bc916250c0d875919a9714c) - Every module sets `meta.configKey`, so an application writes a module's options under its own top-level key of `stars.config` (`api`, `broker`, `cache`, `gateway`, `i18n`, `logger`, `scheduledTasks`, `sharder`, `subcommandsAdvanced`) instead of the `[specifier, options]` tuple of `modules`. The tuple still works and is merged over the key. The key is typed in `defineConfig` once the module is imported in `stars.config.ts`; `cache`, `gateway`, `sharder` and `subcommandsAdvanced` take no options yet and only reserve their name.
+
+  The `@wolfstar/kit` peer range moves from `^0.1.0` to `^0.2.0`, the first version that reads `configKey`, and `@wolfstar/schema` (`^0.9.0`) is a new optional peer that carries the `StarsConfig` type the keys extend. A project on `@wolfstar/kit` 0.1 has to update it.
+
 ## 2.2.0
 
 ### Minor Changes

packages/plugin-i18next/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@wolfstar/plugin-i18next",
-  "version": "2.2.0",
+  "version": "2.3.0",
   "description": "Plugin for @wolfstar/http-framework adding i18next-powered internationalization for HTTP interactions",
   "keywords": [
     "discord",

packages/plugin-logger/CHANGELOG.md

@@ -1,5 +1,13 @@
 # @wolfstar/plugin-logger
 
+## 0.5.0
+
+### Minor Changes
+
+- [#259](https://github.com/wolfstar-project/plugins/pull/259) [`e9c503d`](https://github.com/wolfstar-project/plugins/commit/e9c503da60e60a732bc916250c0d875919a9714c) - Every module sets `meta.configKey`, so an application writes a module's options under its own top-level key of `stars.config` (`api`, `broker`, `cache`, `gateway`, `i18n`, `logger`, `scheduledTasks`, `sharder`, `subcommandsAdvanced`) instead of the `[specifier, options]` tuple of `modules`. The tuple still works and is merged over the key. The key is typed in `defineConfig` once the module is imported in `stars.config.ts`; `cache`, `gateway`, `sharder` and `subcommandsAdvanced` take no options yet and only reserve their name.
+
+  The `@wolfstar/kit` peer range moves from `^0.1.0` to `^0.2.0`, the first version that reads `configKey`, and `@wolfstar/schema` (`^0.9.0`) is a new optional peer that carries the `StarsConfig` type the keys extend. A project on `@wolfstar/kit` 0.1 has to update it.
+
 ## 0.4.0
 
 ### Minor Changes

packages/plugin-logger/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@wolfstar/plugin-logger",
-  "version": "0.4.0",
+  "version": "0.5.0",
   "description": "Plugin for @wolfstar/http-framework providing a pluggable logger with swappable transports (console, Sentry, consola, evlog, winston)",
   "keywords": [
     "consola",

packages/plugin-scheduled-tasks/CHANGELOG.md

@@ -1,5 +1,13 @@
 # @wolfstar/plugin-scheduled-tasks
 
+## 0.3.0
+
+### Minor Changes
+
+- [#259](https://github.com/wolfstar-project/plugins/pull/259) [`e9c503d`](https://github.com/wolfstar-project/plugins/commit/e9c503da60e60a732bc916250c0d875919a9714c) - Every module sets `meta.configKey`, so an application writes a module's options under its own top-level key of `stars.config` (`api`, `broker`, `cache`, `gateway`, `i18n`, `logger`, `scheduledTasks`, `sharder`, `subcommandsAdvanced`) instead of the `[specifier, options]` tuple of `modules`. The tuple still works and is merged over the key. The key is typed in `defineConfig` once the module is imported in `stars.config.ts`; `cache`, `gateway`, `sharder` and `subcommandsAdvanced` take no options yet and only reserve their name.
+
+  The `@wolfstar/kit` peer range moves from `^0.1.0` to `^0.2.0`, the first version that reads `configKey`, and `@wolfstar/schema` (`^0.9.0`) is a new optional peer that carries the `StarsConfig` type the keys extend. A project on `@wolfstar/kit` 0.1 has to update it.
+
 ## 0.2.0
 
 ### Minor Changes

packages/plugin-scheduled-tasks/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@wolfstar/plugin-scheduled-tasks",
-  "version": "0.2.0",
+  "version": "0.3.0",
   "description": "Plugin for @wolfstar/http-framework to schedule one-off and repeated tasks, backed by BullMQ",
   "keywords": [
     "bullmq",

packages/plugin-sharder/CHANGELOG.md

@@ -1,5 +1,13 @@
 # @wolfstar/plugin-sharder
 
+## 0.3.0
+
+### Minor Changes
+
+- [#259](https://github.com/wolfstar-project/plugins/pull/259) [`e9c503d`](https://github.com/wolfstar-project/plugins/commit/e9c503da60e60a732bc916250c0d875919a9714c) - Every module sets `meta.configKey`, so an application writes a module's options under its own top-level key of `stars.config` (`api`, `broker`, `cache`, `gateway`, `i18n`, `logger`, `scheduledTasks`, `sharder`, `subcommandsAdvanced`) instead of the `[specifier, options]` tuple of `modules`. The tuple still works and is merged over the key. The key is typed in `defineConfig` once the module is imported in `stars.config.ts`; `cache`, `gateway`, `sharder` and `subcommandsAdvanced` take no options yet and only reserve their name.
+
+  The `@wolfstar/kit` peer range moves from `^0.1.0` to `^0.2.0`, the first version that reads `configKey`, and `@wolfstar/schema` (`^0.9.0`) is a new optional peer that carries the `StarsConfig` type the keys extend. A project on `@wolfstar/kit` 0.1 has to update it.
+
 ## 0.2.1
 
 ### Patch Changes

packages/plugin-sharder/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@wolfstar/plugin-sharder",
-  "version": "0.2.1",
+  "version": "0.3.0",
   "description": "Multi-process sharding for @wolfstar/plugin-gateway: spawn shards as processes, cluster workers, or worker threads, and message between them",
   "keywords": [
     "cluster",

packages/plugin-subcommands-advanced/CHANGELOG.md

@@ -1,5 +1,13 @@
 # @wolfstar/plugin-subcommands-advanced
 
+## 2.3.0
+
+### Minor Changes
+
+- [#259](https://github.com/wolfstar-project/plugins/pull/259) [`e9c503d`](https://github.com/wolfstar-project/plugins/commit/e9c503da60e60a732bc916250c0d875919a9714c) - Every module sets `meta.configKey`, so an application writes a module's options under its own top-level key of `stars.config` (`api`, `broker`, `cache`, `gateway`, `i18n`, `logger`, `scheduledTasks`, `sharder`, `subcommandsAdvanced`) instead of the `[specifier, options]` tuple of `modules`. The tuple still works and is merged over the key. The key is typed in `defineConfig` once the module is imported in `stars.config.ts`; `cache`, `gateway`, `sharder` and `subcommandsAdvanced` take no options yet and only reserve their name.
+
+  The `@wolfstar/kit` peer range moves from `^0.1.0` to `^0.2.0`, the first version that reads `configKey`, and `@wolfstar/schema` (`^0.9.0`) is a new optional peer that carries the `StarsConfig` type the keys extend. A project on `@wolfstar/kit` 0.1 has to update it.
+
 ## 2.2.1
 
 ### Patch Changes

packages/plugin-subcommands-advanced/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@wolfstar/plugin-subcommands-advanced",
-  "version": "2.2.1",
+  "version": "2.3.0",
   "description": "Plugin for @wolfstar/http-framework to modularize slash subcommands into separate command classes",
   "keywords": [
     "discord",