Skip to content

chore: update changelog and release - #260

Merged
kodiakhq[bot] merged 1 commit into
mainfrom
changeset-release/main
Oct 20, 2026
Merged

kodiakhq[bot] merged 1 commit into
mainfrom
changeset-release/main

Conversation

@wolfstarbot

Copy link
Copy Markdown
Contributor

This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to main, this PR will be updated.

Releases

@wolfstar/plugin-api@2.2.0

Minor Changes

  • #259 e9c503d - 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.

@wolfstar/plugin-broker@0.7.0

Minor Changes

  • #259 e9c503d - 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]:
    • @wolfstar/plugin-cache@0.8.0

@wolfstar/plugin-cache@0.8.0

Minor Changes

  • #259 e9c503d - 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.

@wolfstar/plugin-gateway@0.16.0

Minor Changes

  • #259 e9c503d - 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]:
    • @wolfstar/plugin-cache@0.8.0

@wolfstar/plugin-i18next@2.3.0

Minor Changes

  • #259 e9c503d - 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.

@wolfstar/plugin-logger@0.5.0

Minor Changes

  • #259 e9c503d - 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.

@wolfstar/plugin-scheduled-tasks@0.3.0

Minor Changes

  • #259 e9c503d - 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.

@wolfstar/plugin-sharder@0.3.0

Minor Changes

  • #259 e9c503d - 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.

@wolfstar/plugin-subcommands-advanced@2.3.0

Minor Changes

  • #259 e9c503d - 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.

@coldtea-pr-lens

Copy link
Copy Markdown

Note

The title starts with chore:, so PR Lens left this pull request undrawn. Comment @pr-lens draw to draw it

github.comment.notice: false in .github/pr-lens.yml turns this note off

@wolfstarbot wolfstarbot added packages:plugin-api Changes in plugin-api packages:plugin-i18next Changes in plugin-i18next packages:plugin-logger Changes in plugin-logger packages:plugin-cache Changes in plugin-cache packages:plugin-gateway Changes in plugin-gateway packages:plugin-sharder Changes in plugin-sharder packages:plugin-broker Changes in plugin-broker packages:plugin-scheduled-tasks Changes in plugin-scheduled-tasks labels Oct 20, 2026
@pkg-pr-new

pkg-pr-new Bot commented Oct 20, 2026

Copy link
Copy Markdown

Open in StackBlitz

@wolfstar/plugin-api

pnpm add https://pkg.pr.new/@wolfstar/plugin-api@260

@wolfstar/plugin-broker

pnpm add https://pkg.pr.new/@wolfstar/plugin-broker@260

@wolfstar/plugin-cache

pnpm add https://pkg.pr.new/@wolfstar/plugin-cache@260

@wolfstar/plugin-gateway

pnpm add https://pkg.pr.new/@wolfstar/plugin-gateway@260

@wolfstar/plugin-i18next

pnpm add https://pkg.pr.new/@wolfstar/plugin-i18next@260

@wolfstar/plugin-logger

pnpm add https://pkg.pr.new/@wolfstar/plugin-logger@260

@wolfstar/plugin-scheduled-tasks

pnpm add https://pkg.pr.new/@wolfstar/plugin-scheduled-tasks@260

@wolfstar/plugin-sharder

pnpm add https://pkg.pr.new/@wolfstar/plugin-sharder@260

@wolfstar/plugin-subcommands-advanced

pnpm add https://pkg.pr.new/@wolfstar/plugin-subcommands-advanced@260

commit: 78299d2

@kodiakhq
kodiakhq Bot merged commit 0628dae into main Oct 20, 2026
23 checks passed
@kodiakhq
kodiakhq Bot deleted the changeset-release/main branch October 20, 2026 18:50
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

packages:plugin-api Changes in plugin-api packages:plugin-broker Changes in plugin-broker packages:plugin-cache Changes in plugin-cache packages:plugin-gateway Changes in plugin-gateway packages:plugin-i18next Changes in plugin-i18next packages:plugin-logger Changes in plugin-logger packages:plugin-scheduled-tasks Changes in plugin-scheduled-tasks packages:plugin-sharder Changes in plugin-sharder

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants