@aywengo/mercury-fleet 0.0.1-bootstrap → 0.1.0

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (2) hide show
  1. package/CHANGELOG.md +9 -7
  2. package/package.json +6 -1
package/CHANGELOG.md CHANGED
@@ -10,9 +10,10 @@ and this project uses [Semantic Versioning](https://semver.org/).
10
10
 
11
11
  ## [0.1.0] - not yet published
12
12
 
13
- First published Fleet release, **pending**: `@aywengo/mercury-fleet` is still not on the npm
14
- registry, so nothing here is installable yet. Fleet runs from a source checkout with
15
- `npm run fleet`. See [the release notes](../docs/releases/fleet/0.1.0.md) for what publishing
13
+ First published Fleet release, **pending**: `0.1.0` is not on the npm registry, so nothing here is
14
+ installable yet. Fleet runs from a source checkout with `npm run fleet`. The package page exists --
15
+ created by a `0.0.1-bootstrap` placeholder that trusted publishing requires first -- and `latest`
16
+ points at it, so do not read a bare `npm install -g @aywengo/mercury-fleet` as installing a release. See [the release notes](../docs/releases/fleet/0.1.0.md) for what publishing
16
17
  still requires.
17
18
 
18
19
  The one packaging change since `0.1.0-rc1` matters more than it looks: the package now ships
@@ -30,10 +31,11 @@ under `node_modules`, so the package would have installed cleanly and failed on
30
31
 
31
32
  ## [0.1.0-rc1] - 2026-09-06
32
33
 
33
- Recorded here as a version but **never published**: `@aywengo/mercury-fleet`
34
- is not on the npm registry (404), there is no `fleet-v0.1.0-rc1` tag and no GitHub Release for it, so
35
- `npm install -g @aywengo/mercury-fleet` does not work. Fleet can only be run from a source checkout
36
- (`npm run fleet`). See [`../docs/releases/fleet/0.1.0-rc1.md`](../docs/releases/fleet/0.1.0-rc1.md).
34
+ Recorded here as a version but **never published**: `0.1.0-rc1` is not on the
35
+ npm registry, there is no `fleet-v0.1.0-rc1` tag and no GitHub Release for it. A bare
36
+ `npm install -g @aywengo/mercury-fleet` does not install this version either -- it resolves `latest`,
37
+ which currently points at the `0.0.1-bootstrap` placeholder that created the package page, not at any
38
+ Fleet release. Fleet runs from a source checkout (`npm run fleet`). See [`../docs/releases/fleet/0.1.0-rc1.md`](../docs/releases/fleet/0.1.0-rc1.md).
37
39
 
38
40
  ### Added
39
41
 
package/package.json CHANGED
@@ -1,8 +1,13 @@
1
1
  {
2
2
  "name": "@aywengo/mercury-fleet",
3
- "version": "0.0.1-bootstrap",
3
+ "version": "0.1.0",
4
4
  "license": "MIT",
5
5
  "description": "Federation layer for independent Mercury hosts: host registry, probing, Run dispatch and routing, reconciliation, event aggregation and a Prometheus rollup",
6
+ "repository": {
7
+ "type": "git",
8
+ "url": "git+https://github.com/aywengo/mercury.git",
9
+ "directory": "fleet"
10
+ },
6
11
  "type": "module",
7
12
  "engines": {
8
13
  "node": ">=22.18.0"