Tags: PerpetualSoftware/pad
Tags
chore(nix): bump package version to 0.15.0 ahead of the v0.15.0-rc.1 tag Claude-Session: https://claude.ai/code/session_01HvAuiZ7JaWyCqqyV99LyWt
chore(nix): bump package version to 0.14.0 ahead of the release tag Claude-Session: https://claude.ai/code/session_01BhQoeaWXxJbvw86ezzK8dt
chore(nix): bump version to 0.12.0 Pre-tag version sync required by PLAYB-1160 step 1 — the flake builds from source at whatever ref the user names, so the tag snapshot must self-report the version being tagged. Without this, binaries from 'nix run github:PerpetualSoftware/pad/release' report 0.11.0 forever. Refs TASK-2445.
chore(nix): bump version to 0.12.0 Pre-tag version sync required by PLAYB-1160 step 1 — the flake builds from source at whatever ref the user names, so the tag snapshot must self-report the version being tagged. Without this, binaries from 'nix run github:PerpetualSoftware/pad/release' report 0.11.0 forever. Refs TASK-2445.
feat(web): default new collections to Board — schema-aware (IDEA-2274… …, IDEA-2287) (#1015) * feat(web): default new collections to Board view (IDEA-2274) Board becomes the baseline default view for new collections; existing collections keep their stored default_view (no migration). - Frontend fallback (settingsDefaults, collection-page defaultMode, shareView coerce, initial viewMode) -> board - Create/Edit collection modals default -> board - Backend template seeds (defaults.go, templates*.go) list -> board for ideas/plans/docs/hiring/interviewing collections (tasks was already board) - CLI `pad collection create` and MCP mapCollectionCreate defaults -> board - Curated create-modal presets with deliberate list curation (Meeting Notes, Decisions, OKRs) intentionally left as list - Pin the three list-keyboard-nav pane E2E tests to ?view=list Claude-Session: https://claude.ai/code/session_01EZ6yr6pAUFb1uffan912ra * fix(web): board default reaches public share page + ItemDetail fallback (Codex round 1) Codex review found the public share route (s/[token]) derives its owner default view via a separate `?? 'list'` fallback that bypassed the coerceSettings change, so settings-less/legacy collections rendered List on public share pages. Align it (and the pre-init selectedBase) to board. Also align ItemDetail's inline CollectionSettings fallback (default_view is unused there, but keep it consistent with settingsDefaults). Claude-Session: https://claude.ai/code/session_01EZ6yr6pAUFb1uffan912ra * fix(collections): group Contacts board by relationship, not status (Codex round 2) Contacts has no `status` field, so defaulting it to Board grouped by the default `status` rendered every card in a single Uncategorized lane. Set BoardGroupBy=relationship so the board shows real lanes. All other board-defaulted seed collections have a status field or an explicit board_group_by (verified: Companies/Conventions/Playbooks/Docs have status). Claude-Session: https://claude.ai/code/session_01EZ6yr6pAUFb1uffan912ra * fix(web): always serialize ?view= so a List URL survives a board default (Codex round 3) buildCollectionUrlParams treated List as the implicit URL view and omitted it. With Board now a possible collection default (IDEA-2274), a List selection on a board-default collection produced a URL that, when copied or opened without the sender's localStorage, resolved back to Board. Always serialize the view mode; add a covering unit test. Verified the pane E2E suite (URL-equality assertions) stays green. Claude-Session: https://claude.ai/code/session_01EZ6yr6pAUFb1uffan912ra
fix(release): migrate cosign signing to v3 bundle format (BUG-2091) (#… …925) The cosign-installer action bump (v3.10.1 → v4.1.2) pulled the cosign binary from v2.x to v3.0.6. cosign v3 defaults --new-bundle-format=true for sign-blob and drops the separate --output-certificate/--output-signature outputs, breaking GoReleaser's signs block: Error: signing dist/checksums.txt: create bundle file: open : no such file or directory Caught by the v0.10.0-rc.1 release run. Migrate to the official cosign-v3 path (https://goreleaser.com/blog/cosign-v3/): emit a single Sigstore bundle checksums.txt.sigstore.json via --bundle, replacing the .pem/.sig pair. Verify with `cosign verify-blob --bundle checksums.txt.sigstore.json`. Also refreshes the stale verify comment (was checksums.txt.cosign.bundle). Claude-Session: https://claude.ai/code/session_015yuBJQYfDj95cgX3DaD8SF
fix(release): migrate cosign signing to v3 bundle format (BUG-2091) (#… …925) The cosign-installer action bump (v3.10.1 → v4.1.2) pulled the cosign binary from v2.x to v3.0.6. cosign v3 defaults --new-bundle-format=true for sign-blob and drops the separate --output-certificate/--output-signature outputs, breaking GoReleaser's signs block: Error: signing dist/checksums.txt: create bundle file: open : no such file or directory Caught by the v0.10.0-rc.1 release run. Migrate to the official cosign-v3 path (https://goreleaser.com/blog/cosign-v3/): emit a single Sigstore bundle checksums.txt.sigstore.json via --bundle, replacing the .pem/.sig pair. Verify with `cosign verify-blob --bundle checksums.txt.sigstore.json`. Also refreshes the stale verify comment (was checksums.txt.cosign.bundle). Claude-Session: https://claude.ai/code/session_015yuBJQYfDj95cgX3DaD8SF
PreviousNext