officerdev/platform
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

0 Releases 28 Tags

RSS Feed
  • deploy/2026.08.30.03 c97da0292a
    Compare

    release 2026.08.30.03

    pastilhas released this 2026-08-30 10:38:06 +00:00

    One commit — 537cc29c, fixing what the 2026.08.30.01 rollout found on fofos: a plugin declaring
    @tiptap/pm was reported as a failed install. Nothing was broken on disk. That package has no root
    entry point by design — it is tiptap's single pinned copy of ProseMirror and you import
    @tiptap/pm/state, never the bare name — so the checker asked a question it could not answer.

    Worth its own release rather than waiting: bun run plugins:update exits 1 on fofos every time until
    this lands, so the plugin step of every future deploy fails there and reads as a new problem each time.

    No schema change and no dependency change, with the two commands that prove it in the plan. docs:check
    green. Only fofos has fofos-admin installed, so everywhere else this is a no-op in behaviour.

    ── Why .03 ──

    2026.08.30.02 was tagged against a commit that was not on master: the rollout's own report had just been
    pushed and the release was cut without pulling first. The branch push was rejected and the tag was not,
    so a tag pointing off-branch existed for about ten seconds. The watcher claimed the version inside that
    window, and a claim is permanent by design — so .02 is spent and carries a claim with no .done, which is
    what "attempted and did not succeed" should look like.

    No host moved. Every one stayed on 816f8695 throughout.

    The lesson is in the ordering, and it is now the practice: pull, then push the branch, then tag only
    once the branch has landed. Pushing both in one command means a rejected branch still publishes a tag.

    Co-Authored-By: Claude Opus 5 (1M context) noreply@anthropic.com

    Downloads