Skip to content

v0.13.0

Choose a tag to compare

@github-actions github-actions released this 01 Oct 13:26
· 2 commits to main since this release
bafff31

Upgrade notes

Schema 17. Back up the database before upgrading. This release migrates the schema from 16 to 17 (escalation decision policy: answerers_json, expires_at, delegated_by on task_escalations). The change is additive and existing escalations keep no answerer restriction or expiry, but v0.12.x and older binaries refuse schema 17: rolling back requires restoring the pre-upgrade backup together with the previous binary or image. Any complete schema from 1 through 16 upgrades directly.

New settings, all off or empty by default, so behaviour is unchanged until configured:

  • TASKBOARD_DEFAULT_REQUIREMENTS: requirement tokens (for example runner:k8s-job) given to agent-lane tasks created or moved into the agent lane without any. Agents that do not advertise them stop seeing that untagged pickup work.
  • TASKBOARD_AGENT_POLICIES_JSON allowed_requirements: requirement tokens an agent may set in task_create.
  • TASKBOARD_ANSWER_DELEGATION_PRINCIPALS: service principals allowed to forward a person's escalation answer with the new task_escalation_answer tool.

Behaviour changes that apply without configuration:

  • Recurring tasks now keep their requirements on the next occurrence.
  • In OIDC mode, Taskboard requests the groups scope whenever TASKBOARD_OWNER_GROUPS, ADMIN_GROUPS, MEMBER_GROUPS or VIEWER_GROUPS is set. Previously those mappings never matched unless TASKBOARD_OIDC_ALLOWED_GROUPS was also set, so everyone received TASKBOARD_DEFAULT_ROLE. People sign in again to pick up their role; check that the mapped groups are the ones you intend before upgrading.
  • Escalation answers may omit the text when a listed choice is selected; the choice becomes the answer.

Helm: the chart adds taskboard.defaultRequirements and taskboard.agentPolicy.answerDelegationPrincipals.

What's Changed

  • Adopt shared libraries at go.michaelspost.com by @kilo666mj in #52
  • docs: propose a dispatcher contract for execution backends by @kilo666mj in #53
  • feat: route agent-lane work with default and policy-allowed requirements by @kilo666mj in #54
  • feat: approval-grade escalations with answerers, expiry, and delegated answers by @kilo666mj in #55
  • fix: request the OIDC groups claim when groups decide roles by @kilo666mj in #56
  • feat: accept a selected escalation choice as the whole answer by @kilo666mj in #57

Full Changelog: v0.12.0...v0.13.0