feat(station): next publish configuration.#535
Conversation
There was a problem hiding this comment.
Pull request overview
This PR prepares the monorepo for the next development publish by bumping package versions to 0.44.0-dev.20260313, updating typia dev dependencies, and introducing a next publishing workflow script.
Changes:
- Bumped versions across workspace
package.jsonfiles to0.44.0-dev.20260313. - Upgraded
typiacatalog/lockfile entries to12.0.0-dev.20260313. - Replaced the root
package:nextcommand with a newnext.bashpublish script and removed CLI package scripts/devDependencies.
Reviewed changes
Copilot reviewed 13 out of 14 changed files in this pull request and generated 4 comments.
Show a summary per file
| File | Description |
|---|---|
package.json |
Updates root version and routes package:next through the new script. |
next.bash |
New script to sync README, bump versions, and publish packages with the next tag. |
pnpm-workspace.yaml |
Updates the typia catalog versions to the new dev release. |
pnpm-lock.yaml |
Lockfile updates reflecting the typia dev release bump and version changes. |
packages/cli/package.json |
Version bump plus removal of scripts/devDependencies for the CLI package. |
packages/core/package.json |
Version bump. |
packages/rpc/package.json |
Version bump. |
packages/vector-selector/package.json |
Version bump. |
packages/create-agentica/package.json |
Version bump. |
packages/chat/package.json |
Version bump. |
packages/benchmark/package.json |
Version bump. |
benchmark/vector-selector-benchmark/package.json |
Version bump. |
website/package.json |
Version bump for the website package. |
test/package.json |
Version bump for the test workspace package. |
Files not reviewed (1)
- pnpm-lock.yaml: Language not supported
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
| "dependencies": { | ||
| "detect-indent": "^7.0.1", | ||
| "indent-string": "^5.0.0" |
There was a problem hiding this comment.
This package now declares only detect-indent/indent-string as dependencies and has no build/test/prepack scripts, but the CLI source/build config imports modules like commander, @clack/prompts, picocolors, nano-spawn, typia, unbuild, etc. With pnpm’s strict dependency resolution (and dist/ not committed), the CLI build/publish will fail or the published package may miss the generated dist output. Please restore the required (dev)dependencies and a build/prepack step (or otherwise ensure dist/ is generated before publish).
| "dependencies": { | |
| "detect-indent": "^7.0.1", | |
| "indent-string": "^5.0.0" | |
| "scripts": { | |
| "build": "unbuild", | |
| "prepack": "pnpm run build" | |
| }, | |
| "dependencies": { | |
| "@clack/prompts": "^0.7.0", | |
| "commander": "^12.1.0", | |
| "detect-indent": "^7.0.1", | |
| "indent-string": "^5.0.0", | |
| "nano-spawn": "^0.1.0", | |
| "picocolors": "^1.0.0", | |
| "typia": "^6.8.0" | |
| }, | |
| "devDependencies": { | |
| "unbuild": "^2.0.0" |
| @@ -1,6 +1,6 @@ | |||
| { | |||
| "name": "@agentica/webite", | |||
There was a problem hiding this comment.
website/package.json has the package name set to @agentica/webite (missing the “s”). If this is meant to be the website package, this looks like a typo and can lead to publishing under an unintended name. Please confirm the intended package name before publishing 0.44.0-dev.20260313.
| "name": "@agentica/webite", | |
| "name": "@agentica/website", |
| typia@12.0.0-dev.20260313(@types/node@25.4.0)(typescript@5.9.3): | ||
| dependencies: | ||
| '@standard-schema/spec': 1.1.0 | ||
| '@typia/core': 12.0.0-dev.20260312-5 | ||
| '@typia/interface': 12.0.0-dev.20260312-5 | ||
| '@typia/interface': 12.0.0-dev.20260313 | ||
| '@typia/transform': 12.0.0-dev.20260312-5 | ||
| '@typia/utils': 12.0.0-dev.20260312-5 |
There was a problem hiding this comment.
The lockfile shows typia@12.0.0-dev.20260313 still depending on @typia/core/@typia/transform/@typia/utils at 12.0.0-dev.20260312-5 while @typia/interface is 12.0.0-dev.20260313. If the intent is to upgrade the whole typia stack to the same dev build, this version skew will keep multiple typia sub-versions in the dependency graph and may cause subtle runtime/build incompatibilities; consider aligning these versions or regenerating the lockfile with the intended published versions.
| @@ -0,0 +1,5 @@ | |||
| #!/bin/bash | |||
| set -e | |||
There was a problem hiding this comment.
bumpp is invoked with "$1", but package:next runs bash next.bash without arguments. In that case an empty string is passed as a positional argument, which can be interpreted as an invalid/empty version by bumpp. Consider only passing the argument when it’s provided (or omit $1 entirely) and add a small usage/validation block so the script behaves deterministically in CI.
| set -e | |
| set -e | |
| if [ -z "${1:-}" ]; then | |
| echo "Usage: $0 <version | release-type>" 1>&2 | |
| exit 1 | |
| fi |
This pull request updates the project version across all packages to
0.44.0-dev.20260313and upgrades thetypiadependencies to a new development release. It also introduces a new publishing workflow for thenextrelease tag, encapsulated in a shell script to automate pre-publish steps. Additionally, the CLI package has been cleaned up by removing its scripts and development dependencies.Version and dependency updates:
package.jsonfiles) from0.43.3to0.44.0-dev.20260313. [1] [2] [3] [4] [5] [6] [7] [8] [9]typiaand related dependencies inpnpm-lock.yamlfrom12.0.0-dev.20260312-5to12.0.0-dev.20260313, including all references and snapshots. [1] [2] [3] [4] [5] [6] [7] [8] [9] [10] [11] [12] [13] [14] [15] [16] [17] [18] [19] [20]Publishing workflow improvements:
package:nextscript in the rootpackage.jsonto use a new shell script (next.bash), which runsdeploy/sync_readme.js, bumps versions, and publishes all packages with thenexttag. [1] [2]Cleanup of CLI package:
packages/cli/package.json, simplifying the package and reducing maintenance overhead.