@lacodda/rigger 0.10.0 → 0.11.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.
- package/README.md +1 -1
- package/package.json +2 -2
package/README.md
CHANGED
|
@@ -153,7 +153,7 @@ A project is named after its directory - the name you call it by, not the one it
|
|
|
153
153
|
|
|
154
154
|
## Status
|
|
155
155
|
|
|
156
|
-
v0.
|
|
156
|
+
v0.11.0 makes the week a screen. `week` is the Monday brief - the focus, what ships on Friday, and what waits on you, together rather than assembled by hand. `release-day` reads the shopfront rule the line set for itself: one release a week, on a Friday, and a version ready on a Tuesday waits its turn. It says how far past that a week has gone, folding a busy one into a line a day. And each tier's promise now has a check: a carrying product that missed more than one cycle, a growing one without a turn in six weeks, a second declared product started before the first shipped. Before it: the database, `import`, the context packet, the `mcp` server, facts from git, a chronicle that writes itself, search, the owner's inbox and digest, and the release calendar. The road to 1.0 is twenty-two small releases in seven blocks:
|
|
157
157
|
|
|
158
158
|
| Block | Versions | What it delivers |
|
|
159
159
|
| --- | --- | --- |
|
package/package.json
CHANGED
|
@@ -1,8 +1,8 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "@lacodda/rigger",
|
|
3
|
-
"version": "0.
|
|
3
|
+
"version": "0.11.0",
|
|
4
4
|
"rigger": {
|
|
5
|
-
"binary": "v0.
|
|
5
|
+
"binary": "v0.11.0"
|
|
6
6
|
},
|
|
7
7
|
"description": "One seat for all your projects and tasks: a local record of what is done, what is next and when it ships - read by you and your coding assistant",
|
|
8
8
|
"license": "MIT",
|