p-backlog 0.5.1 → 0.6.0

package/CHANGELOG.md

@@ -1,5 +1,18 @@
 # Changelog
 
+## 0.6.0
+
+- Statistics on the server read only what was appended to project journals and the CLI run log, keep parsed task
+  histories between requests, and rescan git only for new commits (a new day no longer rescans the 90-day window, and
+  if reading the main branch's log fails, the repository is shown as unavailable for that refresh instead of silently
+  showing no changes); a change in one project no longer drops the cached reports of the others.
+- The Code tab's commit counts now also include commits of merged branches that git history simplification used to
+  skip (a merge tree-same with a parent: a change and its revert, `merge -s ours`, a change already cherry-picked) —
+  on ordinary histories nothing changes.
+- The code cache file format changed, so the first run after this update rescans git once.
+- An event appended to a project journal or the CLI run log no longer merges with the last line when that line lacks
+  a trailing newline (a hand edit, an interrupted write): both events stay readable.
+
 ## 0.5.1
 
 - Every statistics chart (debt, created, check precision, effect, usage) has its own "week / day" toggle: 12 weeks or

package/README.md

@@ -309,3 +309,7 @@ To try a build the way a published package would install, without publishing it:
 ```bash
 npm pack && npm i -g ./p-backlog-0.2.0.tgz
 ```
+
+Releases are published to npm by the `Release` GitHub Actions workflow through npm Trusted Publishing: bump the
+version and the CHANGELOG, run `npm run plugins`, commit, push, then push the tag `v<version>` — the workflow checks that
+the tag matches `package.json`, runs the checks and publishes with provenance. No npm token is stored anywhere.

package/README.ru.md

@@ -303,3 +303,8 @@ npm run screenshots               # скриншоты для README на дем
 ```bash
 npm pack && npm i -g ./p-backlog-0.2.0.tgz
 ```
+
+Версии публикует в npm workflow GitHub Actions `Release` через Trusted Publishing: поднимите версию и CHANGELOG,
+выполните `npm run plugins`, закоммитьте, запушьте и запушьте тег `v<версия>` — workflow проверит, что тег совпадает
+с `package.json`, прогонит проверки и опубликует пакет с подтверждением происхождения (provenance). Токен npm нигде не
+хранится.