You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Mark @intent-framework/server as a private workspace package so it is
excluded from npm publishing during the first alpha release.
- Set private: true in packages/server/package.json
- Removed publishConfig from server package
- Updated pack:check to filter only 4 publishable packages (core, dom,
router, testing) instead of all packages/*
- Updated Release-Readiness.md to reflect that server is private and
not a first-alpha publishing blocker
- Server continues to build and test as part of the workspace
Copy file name to clipboardExpand all lines: docs/Release-Readiness.md
+19-9Lines changed: 19 additions & 9 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -6,17 +6,20 @@ Intent is in early experimental development. No packages have been published to
6
6
7
7
The repository has five workspace packages under `packages/*`, all at version `0.1.0`, all using `workspace:*` dependency references. The codebase is functional and validated by CI, but several metadata and workflow steps are missing before a first alpha release.
8
8
9
+
Four packages are intended for first-alpha publishing. `packages/server` is a private workspace package for now.
10
+
9
11
## Intended publishable packages
10
12
11
-
All five packages under `packages/*` are intended to be published:
13
+
The first alpha will publish four packages:
12
14
13
15
| Package | npm name | Purpose |
14
16
|---|---|---|
15
17
|`packages/core`|`@intent-framework/core`| Platformless semantic graph and runtime |
16
18
|`packages/dom`|`@intent-framework/dom`| DOM materializer for screens and router |
17
19
|`packages/router`|`@intent-framework/router`| Typed route definitions and navigation |
18
20
|`packages/testing`|`@intent-framework/testing`| Semantic test harness |
19
-
|`packages/server`|`@intent-framework/server`| Early server-side package |
21
+
22
+
`packages/server` remains a private workspace package until the server API matures.
20
23
21
24
Packages under `examples/` (e.g., `web-basic`) are private and must not be published.
22
25
@@ -103,19 +106,20 @@ Packages under `examples/` (e.g., `web-basic`) are private and must not be publi
103
106
|`repository`| Present | Points to `intent-framework/intent` (`packages/server`) |
@@ -238,7 +243,12 @@ Do not manually create GitHub Releases.
238
243
239
244
- repository fields are present
240
245
- GitHub repository home is https://github.com/intent-framework/intent
241
-
- remaining blockers are release workflow, server maturity, alpha prerelease versioning, and human confirmation of MIT license if still listed
246
+
- remaining first-alpha blockers: release workflow not yet added, alpha prerelease versioning not configured, and human confirmation that MIT is the intended public license
247
+
248
+
## Future server-package decisions
249
+
250
+
- Server maturity is no longer a first-alpha publishing blocker because server is private
251
+
- When the server API matures, the package can be made public and published as a separate decision
242
252
243
253
## Do not do yet
244
254
@@ -251,10 +261,10 @@ Do not manually create GitHub Releases.
251
261
252
262
## Pack check command
253
263
254
-
This PR adds a root pack-check command:
264
+
The root `pack:check` command:
255
265
256
266
```sh
257
267
pnpm pack:check
258
268
```
259
269
260
-
It dry-runs `npm pack` for all five workspace packages after build. It does not publish, does not require network access, and does not create committed tarballs.
270
+
dry-runs `npm pack` for the four publishable workspace packages (core, dom, router, testing). It excludes the private `@intent-framework/server` package. It does not publish, does not require network access, and does not create committed tarballs.
0 commit comments