@nidvue/teamwork 1.1.0 → 1.1.1

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.
package/CHANGELOG.md CHANGED
@@ -9,7 +9,21 @@ All notable changes to this project are documented in this file.
9
9
  The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.1.0/),
10
10
  and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
11
11
 
12
- ## [Unreleased](https://github.com/Nidvue/Teamwork/compare/v1.0.2...HEAD)
12
+ ## [Unreleased](https://github.com/Nidvue/Teamwork/compare/v1.1.1...HEAD)
13
+
14
+ ## [1.1.1](https://github.com/Nidvue/Teamwork/compare/v1.1.0...v1.1.1) - 2026-10-20
15
+
16
+ ### Fixed
17
+
18
+ - **npm package republished as 1.1.1**: the first `npm publish` of
19
+ `@nidvue/teamwork@1.1.0` exited 0 but only *staged* the version on the registry
20
+ (`dist-tags.latest` stayed at the `0.0.0-stage` placeholder, the packument never
21
+ appeared, and `npm stage list` returned no stage-id to reject). A second publish
22
+ of that version is refused with `E409 Cannot publish over previously staged
23
+ version`. This is the phantom-staged-publish registry bug tracked as
24
+ [npm/cli#9889](https://github.com/npm/cli/issues/9889); the version number cannot
25
+ be reused, so the package ships as 1.1.1. No code, skill or protocol change -
26
+ the tarball is byte-identical to the 1.1.0 build apart from the version field.
13
27
 
14
28
  ## [1.1.0](https://github.com/Nidvue/Teamwork/releases/tag/v1.1.0) - 2026-10-20
15
29
 
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@nidvue/teamwork",
3
- "version": "1.1.0",
3
+ "version": "1.1.1",
4
4
  "description": "Nidvue Teamwork - an autonomous, self-governing agent company for pi: CEO-led decomposition, parallel lanes, two-stage review, hash-chained audit ledger and layered role-owned tests. Python 3.9+, stdlib only.",
5
5
  "keywords": [
6
6
  "pi-package",
@@ -6,7 +6,7 @@ that importing ``teamwork`` stays cheap.
6
6
 
7
7
  from __future__ import annotations
8
8
 
9
- __version__ = "1.1.0"
9
+ __version__ = "1.1.1"
10
10
 
11
11
  #: Distribution name on PyPI. The name ``teamwork`` is already taken there, so
12
12
  #: the project ships as ``teamwork-agents`` while importing as ``teamwork``.