Skip to content

chore: depend on @inkanjs/inkan, the core's new name - #4

Merged
vxnsin merged 1 commit into
mainfrom
rename-inkanjs-scope
Nov 12, 2026
Merged

vxnsin merged 1 commit into
mainfrom
rename-inkanjs-scope

Conversation

@vxnsin

@vxnsin vxnsin commented Nov 12, 2026

Copy link
Copy Markdown
Contributor

The core is now published as @inkanjs/inkan (0.9.2 is on npm); @vxnsin/inkan stays at 0.9.1. See inkanjs/inkan#38.

  • Every package: peer dependency @inkanjs/inkan >=0.8.0 <1.0.0, dev dependency ^0.9.2, imports, READMEs and tests on the new name.
  • A patch release each, with a CHANGELOG entry: auth 0.2.2, circuit-breaker 0.2.1, etag 0.2.1, idempotency 0.2.1, mongo 0.1.1, mysql 0.1.1, otel 0.2.1, postgres 0.1.1, proxy 0.2.1, redis 0.1.1, secure-headers 0.2.1, session 0.2.1.
  • Lockfile resolved against the published @inkanjs/inkan 0.9.2.

Locally: typecheck and all 12 packages' tests pass.

After merging, one release per package (auth-v0.2.2, …) publishes them through publish.yml.

Every package moves its peer and dev dependency from @vxnsin/inkan to @inkanjs/inkan (0.9.2 and later) and gets a patch release for it.
@vxnsin
vxnsin merged commit f7c84fe into main Nov 12, 2026
7 checks passed
@vxnsin
vxnsin deleted the rename-inkanjs-scope branch November 12, 2026 09:16
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant