Cordy/Cairn
2
1
Fork 0
Code Issues 20 Pull requests Projects Releases Packages Wiki Activity Actions

Seat lifecycle: seats never free — rolling activity window + visible seats + manual release #428

New issue
Closed
opened 2026-09-05 02:33:55 +00:00 by Cordy · 3 comments
Cordy commented 2026-09-05 02:33:55 +00:00
Owner
Copy link

Flagged twice this week (Manuel's licensing question; Nikola 2026-09-05): "how would a seat become free again if a person leaves the company and their user either gets deleted from their OIDC or just stays for multiple months?"

Current behaviour: it never does

license.Manager.SeenUsers is append-only. Admit records a username on first sign-in; nothing ever removes one, and the stored timestamp is first-seen — not even refreshed on later sign-ins. A leaver holds their seat forever, whether their IdP account is deleted or just dormant. Cairn cannot observe IdP deletion (no SCIM/webhooks; OIDC only speaks at sign-in). The Overview footnote — "seats are people who have signed in, not accounts" — quietly means ever, which makes it a ratchet.

How the competition does it

Direct competitors (self-hosted file sync/share):

Product Seat = Freeing a seat Pitfall observed
Seafile Pro activated account (ACTIVATE_AFTER_FIRST_LOGIN optionally ties activation to first login) admin deactivates the account account-state model; LDAP sync auto-deactivating users surprised operators; imports can accidentally activate everyone
Nextcloud Enterprise enabled account (disabled users excluded from subscription count) admin disables the account counting provisioned state across user backends breeds bugs — public issues on wrong/negative user counts, disabled-ratio warnings under LDAP
ownCloud Enterprise activity-defined: metrics distinguish registered / active (lastLogin < 2 weeks) / concurrent automatic — inactivity ages the user out 2-week window is aggressively short for a licensing definition; fine for metrics, flappy for billing

Adjacent industry:

  • GitLab self-managed: billable = not blocked/deactivated; deactivating/blocking releases the seat immediately; ships auto-removal of dormant members; bills true-up on max seats used during the period — a known renewal-surprise generator.
  • GitHub Enterprise: bills dormant users too (org membership = billed); ships dormant-user reports so admins can prune by hand. This is Cairn's current model, and it is the widely-resented one.
  • General SaaS: recurring customer complaints wherever deactivated/departed users keep counting; the accepted best practices are a documented seat definition, visibility into seat holders, and a 90-day audit rhythm.

Fit assessment for Cairn: the Seafile/Nextcloud/GitLab model requires the product to own account state — a "disable user" concept. Cairn deliberately has none ("Cairn does not store passwords and cannot create, disable or rename a person"). The only models that fit an IdP-consuming product are ownCloud's activity window (no account state needed, purely observed sign-ins) and a manual release on the seat record (the seat, not the account — Cairn owns the former, never the latter).

Design (completes the existing philosophy instead of replacing it)

  1. Last-seen semantics. Admit refreshes the user's timestamp on every successful sign-in, throttled to once per ~24h per user so it is not a state write per request. Migration is self-healing: existing first-seen values simply act as stale last-seens; active users blink out at worst once and re-record on next sign-in.
  2. Rolling window count. A seat = a distinct user seen in the last 90 days (fixed policy, deliberately not config — a configurable window is a knob for gaming your own invoice). One counting function; the Seats tile, cap enforcement in Admit, and the seatsUsed reported at check-in all use it — displayed, enforced and billed numbers can never disagree (the Nextcloud bug class dies by construction). Dormant leavers age out automatically; IdP-deleted users age out identically since they can never sign in again.
  3. Seats become visible. The admin Seats tab lists current seat holders with "last seen X ago" — the operator sees dormancy instead of inferring it (GitHub's dormant report, minus the resented billing).
  4. Manual release. An audit-logged "release seat" action per row for immediate offboarding. Gaming is self-defeating: a released user who signs in again simply re-occupies a seat, which is only "cheating" if the person did not actually leave — in which case the count was right.
  5. Copy + docs. Overview footnote becomes "seats are people who signed in within the last 90 days"; licensing-faq seat definition updated to match; CHANGELOG note that windowed counting can only ever lower the reported number vs today.

Deliberately rejected: account-state seats (nothing to deactivate in Cairn), SCIM/IdP webhooks (an integration surface far out of scope for the problem), GitLab-style max-seats true-up (renewal surprises; check-in stays a point-in-time honest report), ownCloud's 2-week window (too flappy for a billing definition).

Decisions to bless before building

  • Window length 90 days, fixed (recommended) — or different / configurable?
  • Does the license server side need the window definition beyond docs? (seatsUsed payload shape is unchanged.)
  • Manual release: admin-only action on the Seats tab, audit event seat-release — confirm.
  • Footnote copy: "seats are people who signed in within the last 90 days" ×4 locales.

Verification

  • TDD (witnessed red, house style): window expiry frees a seat; sign-in refreshes last-seen (and is throttled); released seat re-occupies on next sign-in; cap enforcement uses the windowed count; check-in reports the windowed count; migration treats legacy first-seen values as last-seen.
  • Live: after deploy, Seats tab lists both admins with last-seen; releasing one drops the tile count; their next sign-in restores it.

Related: #426 (admins now occupy seats — this issue governs how any seat is ever released), the licensing dress rehearsal planned for v0.7.

Flagged twice this week (Manuel's licensing question; Nikola 2026-09-05): *"how would a seat become free again if a person leaves the company and their user either gets deleted from their OIDC or just stays for multiple months?"* ## Current behaviour: it never does `license.Manager.SeenUsers` is append-only. `Admit` records a username on first sign-in; nothing ever removes one, and the stored timestamp is **first-seen** — not even refreshed on later sign-ins. A leaver holds their seat forever, whether their IdP account is deleted or just dormant. Cairn cannot observe IdP deletion (no SCIM/webhooks; OIDC only speaks at sign-in). The Overview footnote — "seats are people who have signed in, not accounts" — quietly means *ever*, which makes it a ratchet. ## How the competition does it **Direct competitors (self-hosted file sync/share):** | Product | Seat = | Freeing a seat | Pitfall observed | |---|---|---|---| | Seafile Pro | activated account (`ACTIVATE_AFTER_FIRST_LOGIN` optionally ties activation to first login) | admin deactivates the account | account-state model; LDAP sync auto-deactivating users surprised operators; imports can accidentally activate everyone | | Nextcloud Enterprise | enabled account (disabled users excluded from subscription count) | admin disables the account | counting provisioned state across user backends breeds bugs — public issues on wrong/negative user counts, disabled-ratio warnings under LDAP | | ownCloud Enterprise | **activity-defined**: metrics distinguish registered / active (lastLogin < 2 weeks) / concurrent | automatic — inactivity ages the user out | 2-week window is aggressively short for a licensing definition; fine for metrics, flappy for billing | **Adjacent industry:** - **GitLab self-managed**: billable = not blocked/deactivated; deactivating/blocking releases the seat immediately; ships *auto-removal of dormant members*; bills true-up on **max seats used** during the period — a known renewal-surprise generator. - **GitHub Enterprise**: bills **dormant users too** (org membership = billed); ships dormant-user reports so admins can prune by hand. This is Cairn's current model, and it is the widely-resented one. - General SaaS: recurring customer complaints wherever deactivated/departed users keep counting; the accepted best practices are a documented seat definition, visibility into seat holders, and a 90-day audit rhythm. **Fit assessment for Cairn:** the Seafile/Nextcloud/GitLab model requires the product to *own account state* — a "disable user" concept. Cairn deliberately has none ("Cairn does not store passwords and cannot create, disable or rename a person"). The only models that fit an IdP-consuming product are ownCloud's **activity window** (no account state needed, purely observed sign-ins) and a **manual release on the seat record** (the seat, not the account — Cairn owns the former, never the latter). ## Design (completes the existing philosophy instead of replacing it) 1. **Last-seen semantics.** `Admit` refreshes the user's timestamp on every successful sign-in, throttled to once per ~24h per user so it is not a state write per request. Migration is self-healing: existing first-seen values simply act as stale last-seens; active users blink out at worst once and re-record on next sign-in. 2. **Rolling window count.** A seat = a distinct user seen in the last **90 days** (fixed policy, deliberately not config — a configurable window is a knob for gaming your own invoice). One counting function; the Seats tile, cap enforcement in `Admit`, and the `seatsUsed` reported at check-in all use it — displayed, enforced and billed numbers can never disagree (the Nextcloud bug class dies by construction). Dormant leavers age out automatically; IdP-deleted users age out identically since they can never sign in again. 3. **Seats become visible.** The admin Seats tab lists current seat holders with "last seen X ago" — the operator sees dormancy instead of inferring it (GitHub's dormant report, minus the resented billing). 4. **Manual release.** An audit-logged "release seat" action per row for immediate offboarding. Gaming is self-defeating: a released user who signs in again simply re-occupies a seat, which is only "cheating" if the person did not actually leave — in which case the count was right. 5. **Copy + docs.** Overview footnote becomes "seats are people who signed in within the last 90 days"; licensing-faq seat definition updated to match; CHANGELOG note that windowed counting can only ever *lower* the reported number vs today. **Deliberately rejected:** account-state seats (nothing to deactivate in Cairn), SCIM/IdP webhooks (an integration surface far out of scope for the problem), GitLab-style max-seats true-up (renewal surprises; check-in stays a point-in-time honest report), ownCloud's 2-week window (too flappy for a billing definition). ## Decisions to bless before building - [ ] Window length 90 days, fixed (recommended) — or different / configurable? - [ ] Does the license *server* side need the window definition beyond docs? (`seatsUsed` payload shape is unchanged.) - [ ] Manual release: admin-only action on the Seats tab, audit event `seat-release` — confirm. - [ ] Footnote copy: "seats are people who signed in within the last 90 days" ×4 locales. ## Verification - TDD (witnessed red, house style): window expiry frees a seat; sign-in refreshes last-seen (and is throttled); released seat re-occupies on next sign-in; cap enforcement uses the windowed count; check-in reports the windowed count; migration treats legacy first-seen values as last-seen. - Live: after deploy, Seats tab lists both admins with last-seen; releasing one drops the tile count; their next sign-in restores it. Related: #426 (admins now occupy seats — this issue governs how any seat is ever released), the licensing dress rehearsal planned for v0.7.
Cordy commented 2026-09-05 02:52:22 +00:00
Author
Owner
Copy link

Decisions blessed (Nikola, 2026-09-05):

  • Window: 90 days, fixed. Hard-coded policy, not config.
  • Server side: A — docs only. Deliberate, with reasoning recorded: the seatWindowDays metadata field provides nothing to the customer and creates a visible "sends usage data" surface in a product sold on sovereignty and privacy. Seafile and ownCloud send nothing back to their vendors; purchased seat counts are already known on our side from the sale. "Technically no one gains anything, but on the human level we might lose trust before even landing." The upgrade-cliff cost (seatsUsed dropping unexplained at the version boundary, incomparable history) is accepted knowingly.
  • Manual release: yes — admin-only action on the Seats tab, audit event seat-release; released users re-occupy on next sign-in.
  • Footnote copy: "seats are people who signed in within the last 90 days, not accounts" ×4 locales.

Open question surfaced by the same reasoning (not blocking this issue): the existing check-in already reports seatsUsed (#89). The sovereignty argument applies to it identically — dropping it would place Cairn fully in the Seafile/ownCloud no-usage-telemetry camp, leaving check-in as pure licence validation (renewals informed by the customer's own Seats tab instead). Nikola to decide separately.

Next: Seats tab UI mockup (house rule: mockup before build), then TDD implementation.

**Decisions blessed (Nikola, 2026-09-05):** - [x] **Window: 90 days, fixed.** Hard-coded policy, not config. - [x] **Server side: A — docs only.** Deliberate, with reasoning recorded: the `seatWindowDays` metadata field provides nothing to the customer and creates a visible "sends usage data" surface in a product sold on sovereignty and privacy. Seafile and ownCloud send nothing back to their vendors; purchased seat counts are already known on our side from the sale. *"Technically no one gains anything, but on the human level we might lose trust before even landing."* The upgrade-cliff cost (seatsUsed dropping unexplained at the version boundary, incomparable history) is accepted knowingly. - [x] **Manual release: yes** — admin-only action on the Seats tab, audit event `seat-release`; released users re-occupy on next sign-in. - [x] **Footnote copy:** "seats are people who signed in within the last 90 days, not accounts" ×4 locales. **Open question surfaced by the same reasoning (not blocking this issue):** the existing check-in already reports `seatsUsed` (#89). The sovereignty argument applies to it identically — dropping it would place Cairn fully in the Seafile/ownCloud no-usage-telemetry camp, leaving check-in as pure licence validation (renewals informed by the customer's own Seats tab instead). Nikola to decide separately. Next: Seats tab UI mockup (house rule: mockup before build), then TDD implementation.
Cordy commented 2026-09-05 04:40:01 +00:00
Author
Owner
Copy link

Shipped and live-verified. v0.6.129 (PR #429, TDD run tdd-428 — red evidence in the run log: window-aging assertions, api compile-red, Seats/ReleaseSeat compile-red, all watched before their implementations landed in the same run), plus two layout patches v0.6.130/v0.6.131 (the admin shell's #adminview .uarow two-column grid wrapped the kebab; fixed with a two-id three-column rule, verified by live style injection before tagging). Both dogfoods run v0.6.131.

What went in:

  • Last-seen semantics: Admit refreshes the holder's timestamp (throttled to one write per day); windowed 90-day counting feeds the Seats tile, the admission cap and both check-in paths. Legacy first-seen entries count as last-seen — the migration is doing nothing (verified live: manu-admin holds no seat because his last sign-in predates v0.6.128's admin recording; he claims one at next sign-in).
  • GET /api/v1/license/seats + POST /api/v1/license/seats/release; release appends audit action seat-release (actor = admin, path = freed holder).
  • Users & access → tabs Access | Seats per the approved mockup; deep link #admin/users/seats; licence meter footer restates the 90-day definition ×4 locales and links to the tab.
  • Docs: licensing-faq "What counts as a seat?" updated; CHANGELOG entries.

Live verification on the enc dogfood (nikola-test session):

  • Access tab byte-identical to the old page under the new tab bar ✓
  • Seats tab: "2 of 60 seats in use" + window sentence; nikola-test Active (last-seen throttling visible: "2 hours ago" despite fresh sign-ins), nikola-test2 Idle (23 days) ✓
  • Kebab → "Release seat…" → confirm dialog (copy per mockup) → released nikola-test2 (user-approved): count dropped to 1 of 60, row gone, list refreshed ✓
  • Audit log: 04:39 · nikola-test · seat-release · nikola-test2 ✓
  • Licence page footer + "manage seats in Users & access" link lands on the Seats tab ✓

Follow-up nit: the audit query page's Action dropdown doesn't list seat-release (events appear under "Any action"; the dropdown is a hardcoded list).

Still open on this issue: the parked question of dropping seatsUsed from the check-in payload entirely (Nikola's call), and Nikola's own look at the live tab before closing.

Shipped and live-verified. **v0.6.129** (PR #429, TDD run `tdd-428` — red evidence in the run log: window-aging assertions, api compile-red, Seats/ReleaseSeat compile-red, all watched before their implementations landed in the same run), plus two layout patches **v0.6.130/v0.6.131** (the admin shell's `#adminview .uarow` two-column grid wrapped the kebab; fixed with a two-id three-column rule, verified by live style injection before tagging). Both dogfoods run v0.6.131. What went in: - Last-seen semantics: `Admit` refreshes the holder's timestamp (throttled to one write per day); windowed 90-day counting feeds the Seats tile, the admission cap and both check-in paths. Legacy first-seen entries count as last-seen — the migration is doing nothing (verified live: manu-admin holds no seat because his last sign-in predates v0.6.128's admin recording; he claims one at next sign-in). - `GET /api/v1/license/seats` + `POST /api/v1/license/seats/release`; release appends audit action `seat-release` (actor = admin, path = freed holder). - Users & access → tabs **Access | Seats** per the approved mockup; deep link `#admin/users/seats`; licence meter footer restates the 90-day definition ×4 locales and links to the tab. - Docs: licensing-faq "What counts as a seat?" updated; CHANGELOG entries. Live verification on the enc dogfood (nikola-test session): - Access tab byte-identical to the old page under the new tab bar ✓ - Seats tab: "2 of 60 seats in use" + window sentence; nikola-test Active (last-seen throttling visible: "2 hours ago" despite fresh sign-ins), nikola-test2 Idle (23 days) ✓ - Kebab → "Release seat…" → confirm dialog (copy per mockup) → released nikola-test2 (user-approved): count dropped to **1 of 60**, row gone, list refreshed ✓ - Audit log: `04:39 · nikola-test · seat-release · nikola-test2` ✓ - Licence page footer + "manage seats in Users & access" link lands on the Seats tab ✓ Follow-up nit: the audit query page's Action dropdown doesn't list `seat-release` (events appear under "Any action"; the dropdown is a hardcoded list). Still open on this issue: the parked question of dropping `seatsUsed` from the check-in payload entirely (Nikola's call), and Nikola's own look at the live tab before closing.
Cordy commented 2026-09-05 05:37:56 +00:00
Author
Owner
Copy link

Closing — every thread resolved:

  • Parked question decided (Nikola, 2026-09-05): seatsUsed dropped from the check-in payload. v0.6.132 (PR #434, TDD with the red watched on the runner) posts {licenseId} alone; seat usage never leaves the instance. The licence server was verified beforehand to require only licenseId. Live-verified: Refresh licence on the enc dogfood at 05:32 — check-in OK against license.swisscairn.ch with the slimmed payload, key intact.
  • Wording precision pass (customer trust): the phone-home promise is keyed to the licence, not the seat count — "no licence installed ⇒ never phones home; any installed licence, above or below 50 seats ⇒ monthly check-in, licence id and nothing else" (per #89, Nikola's recorded decision from v0.3.23). Fixed everywhere it was coupled to "≤50 users": Cairn README, ARCHITECTURE §8.1, licensing-faq, PUBLIC-SECTOR (which still claimed an "anonymous seat count" is sent), the FreeSeats comment (PR #436) — and on cairn-site, including the factually false pricing bullet "at or under 50 users never contact us — not even with a key installed" (cairn-site PR #20). Historical CHANGELOG entries (v0.3.2) carry supersession notes rather than rewrites (PR #435).
  • Follow-up tracked separately: #433 (audit Action dropdown).

Full arc: v0.6.129 seat lifecycle (90-day window, last-seen refresh, Seats tab, audited release), v0.6.130/131 layout fixes, v0.6.132 payload slim — all live on both dogfoods, docs coherent across handbook, ARCHITECTURE, site, and wikis.

Closing — every thread resolved: - **Parked question decided (Nikola, 2026-09-05): `seatsUsed` dropped from the check-in payload.** v0.6.132 (PR #434, TDD with the red watched on the runner) posts `{licenseId}` alone; seat usage never leaves the instance. The licence server was verified beforehand to require only `licenseId`. **Live-verified**: Refresh licence on the enc dogfood at 05:32 — check-in OK against license.swisscairn.ch with the slimmed payload, key intact. - **Wording precision pass (customer trust)**: the phone-home promise is keyed to the licence, not the seat count — "no licence installed ⇒ never phones home; any installed licence, above or below 50 seats ⇒ monthly check-in, licence id and nothing else" (per #89, Nikola's recorded decision from v0.3.23). Fixed everywhere it was coupled to "≤50 users": Cairn README, ARCHITECTURE §8.1, licensing-faq, PUBLIC-SECTOR (which still claimed an "anonymous seat count" is sent), the `FreeSeats` comment (PR #436) — and on **cairn-site**, including the factually false pricing bullet "at or under 50 users never contact us — not even with a key installed" (cairn-site PR #20). Historical CHANGELOG entries (v0.3.2) carry supersession notes rather than rewrites (PR #435). - Follow-up tracked separately: #433 (audit Action dropdown). Full arc: v0.6.129 seat lifecycle (90-day window, last-seen refresh, Seats tab, audited release), v0.6.130/131 layout fixes, v0.6.132 payload slim — all live on both dogfoods, docs coherent across handbook, ARCHITECTURE, site, and wikis.
Cordy closed this issue 2026-09-05 05:38:01 +00:00
Sign in to join this conversation.
No Branch/Tag specified
Branches Tags
main
fix-escguard
fix-vard
fix-middot
fix-552d
fix-552c
fix-543
scout-tf
v0.6.265
v0.6.264
v0.6.263
v0.6.262
v0.6.261
v0.6.260
v0.6.259
v0.6.258
v0.6.257
v0.6.256
v0.6.255
v0.6.254
v0.6.253
v0.6.252
v0.6.251
v0.6.250
v0.6.249
v0.6.248
v0.6.247
v0.6.246
v0.6.245
v0.6.244
v0.6.243
v0.6.242
v0.6.241
v0.6.240
v0.6.239
v0.6.238
v0.6.237
v0.6.236
v0.6.235
v0.6.234
v0.6.233
v0.6.232
v0.6.231
v0.6.230
v0.6.229
v0.6.228
v0.6.227
v0.6.226
v0.6.225
v0.6.224
v0.6.223
v0.6.222
v0.6.221
v0.6.220
v0.6.219
v0.6.218
v0.6.217
v0.6.216
v0.6.215
v0.6.214
v0.6.213
v0.6.212
v0.6.211
v0.6.210
v0.6.209
v0.6.208
v0.6.207
v0.6.206
v0.6.205
v0.6.204
v0.6.203
v0.6.202
v0.6.201
v0.6.200
v0.6.199
v0.6.198
v0.6.197
v0.6.196
v0.6.195
v0.6.194
v0.6.193
v0.6.192
v0.6.191
v0.6.190
v0.6.189
v0.6.188
v0.6.187
v0.6.186
v0.6.185
v0.6.184
v0.6.183
v0.6.182
v0.6.181
v0.6.180
v0.6.179
v0.6.178
v0.6.177
v0.6.176
v0.6.175
v0.6.174
v0.6.173
v0.6.172
v0.6.171
v0.6.170
v0.6.169
v0.6.168
v0.6.167
v0.6.166
v0.6.165
v0.6.164
v0.6.163
v0.6.162
v0.6.161
v0.6.160
v0.6.159
v0.6.158
v0.6.157
v0.6.156
v0.6.155
v0.6.154
v0.6.153
v0.6.152
v0.6.151
v0.6.150
v0.6.149
v0.6.148
v0.6.147
v0.6.146
v0.6.145
v0.6.144
v0.6.143
v0.6.142
v0.6.141
v0.6.140
v0.6.139
v0.6.138
v0.6.137
v0.6.136
v0.6.135
v0.6.134
v0.6.133
v0.6.132
v0.6.131
v0.6.130
v0.6.129
v0.6.128
v0.6.127
v0.6.126
v0.6.125
v0.6.124
v0.6.123
v0.6.122
v0.6.121
v0.6.120
v0.6.119
v0.6.118
v0.6.117
v0.6.116
v0.6.115
v0.6.114
v0.6.113
v0.6.112
v0.6.111
v0.6.110
v0.6.109
v0.6.108
v0.6.107
v0.6.106
v0.6.105
v0.6.104
v0.6.103
v0.6.102
v0.6.101
v0.6.100
v0.6.99
v0.6.98
v0.6.97
v0.6.96
v0.6.95
v0.6.94
v0.6.93
v0.6.92
v0.6.91
v0.6.90
v0.6.89
v0.6.88
v0.6.87
v0.6.86
v0.6.85
v0.6.84
v0.6.83
v0.6.82
v0.6.81
v0.6.80
v0.6.79
v0.6.78
v0.6.77
v0.6.76
v0.6.75
v0.6.74
v0.6.73
v0.6.72
v0.6.71
v0.6.70
v0.6.69
v0.6.68
v0.6.67
v0.6.66
v0.6.65
v0.6.64
v0.6.63
v0.6.62
v0.6.61
v0.6.60
v0.6.59
v0.6.58
v0.6.57
v0.6.56
v0.6.55
v0.6.54
v0.6.53
v0.6.52
v0.6.51
v0.6.50
v0.6.49
v0.6.48
v0.6.47
v0.6.46
v0.6.45
v0.6.44
v0.6.43
v0.6.42
v0.6.41
v0.6.40
v0.6.39
v0.6.38
v0.6.37
v0.6.36
v0.6.35
v0.6.34
v0.6.33
v0.6.32
v0.6.31
v0.6.30
v0.6.29
v0.6.28
v0.6.25
v0.6.24
v0.6.23
v0.6.22
v0.6.21
v0.6.20
v0.6.19
v0.6.18
v0.6.17
v0.6.16
v0.6.15
v0.6.14
v0.6.12
v0.6.11
v0.6.10
v0.6.9
v0.6.8
v0.6.7
v0.6.6
v0.6.5
v0.6.4
v0.6.3
v0.6.2
v0.6.1
v0.6.0
v0.5.7
v0.5.6
v0.5.5
v0.5.4
v0.5.3
v0.5.2
v0.5.1
v0.5.0
v0.4.12
v0.4.11
v0.4.10
v0.4.9
v0.4.8
v0.4.7
v0.4.6
v0.4.5
v0.4.4
v0.4.3
v0.4.2
v0.4.1
v0.3.30
v0.3.29
v0.3.28
v0.3.27
v0.3.26
v0.3.25
v0.3.24
v0.3.23
v0.3.22
v0.3.21
v0.3.20
v0.3.19
v0.3.18
v0.3.17
v0.3.16
v0.3.15
v0.3.14
v0.3.13
v0.3.12
v0.3.11
v0.3.10
v0.3.9
v0.3.8
v0.3.7
v0.3.6
v0.3.5
v0.3.4
v0.3.3
v0.3.2
v0.3.1
v0.3.0
v0.2.7
v0.2.6
v0.2.5
v0.2.4
v0.2.3
v0.2.2
v0.2.1
v0.2.0
v0.0.3
v0.0.2
Labels
Clear labels
No items
No labels
Milestone
Clear milestone
No items
No milestone
v0.7 — Closed beta (dogfood + hardening)
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: Cordy/Cairn#428
No description provided.
Delete branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?