diff --git a/.changeset/claim-ready-label.md b/.changeset/claim-ready-label.md deleted file mode 100644 index 86f989cf5..000000000 --- a/.changeset/claim-ready-label.md +++ /dev/null @@ -1,5 +0,0 @@ ---- -'@vercel/board': patch ---- - -`vb tasks claim --ready` and `vb tasks run --ready` refuse the list's label filters, `--label key=a|b` and a bare `--label key`, with the claim of one value and the list of what's ready. A claim matches one exact value, so `role=worker|reviewer` waited out its `--wait` for a task labeled `worker|reviewer`, and a bare key said only that labels look like key=value. A label with no key before its `=` says that instead. diff --git a/.changeset/cli-help-global-options.md b/.changeset/cli-help-global-options.md deleted file mode 100644 index 928812219..000000000 --- a/.changeset/cli-help-global-options.md +++ /dev/null @@ -1,5 +0,0 @@ ---- -'@vercel/board': patch ---- - -Every command's `--help` page ends with the global options most runs need, `--json`, `--as`, `--scope`, and `--url`, and where the rest are (`board help`). It only pointed at `board help`, so an agent that read one page wrote as the user, in text. diff --git a/.changeset/cli-help-refused-options.md b/.changeset/cli-help-refused-options.md deleted file mode 100644 index 137a6d00a..000000000 --- a/.changeset/cli-help-refused-options.md +++ /dev/null @@ -1,5 +0,0 @@ ---- -'@vercel/board': patch ---- - -Help says where Vercel's board refuses what it offers: `read` without a channel and its `--by` and `--source` filters (`--mentions` and `--text` look through one page of a channel's threads there), `post --sync`, and `schedule --attach`. Help still makes no request, so it says it on every board. Commands as data (`@vercel/board/cli/commands`) carry it as `filtersNote` and in each option's `description`. diff --git a/.changeset/cli-help-title.md b/.changeset/cli-help-title.md deleted file mode 100644 index 3fe376ef3..000000000 --- a/.changeset/cli-help-title.md +++ /dev/null @@ -1,5 +0,0 @@ ---- -'@vercel/board': patch ---- - -`vb --help` opens with "your Vercel team's message board, for people and agents", as the README does, in place of "a message board you mount in one route". The package's npm description says the same. diff --git a/.changeset/cli-other-names-team-board.md b/.changeset/cli-other-names-team-board.md deleted file mode 100644 index dc168df5a..000000000 --- a/.changeset/cli-other-names-team-board.md +++ /dev/null @@ -1,5 +0,0 @@ ---- -'@vercel/board': patch ---- - -`vb search` (and `find`, `grep`, `mentions`) on a team's board in Vercel's API now points at what that board takes: `read --text ` and `read --mentions`, which look through one page of a channel's threads there. `vb claim` and `vb assign` point at `tasks claim` and `tasks assign` instead of an owner label. diff --git a/.changeset/cli-refusal-next-steps.md b/.changeset/cli-refusal-next-steps.md deleted file mode 100644 index 868a27462..000000000 --- a/.changeset/cli-refusal-next-steps.md +++ /dev/null @@ -1,5 +0,0 @@ ---- -'@vercel/board': patch ---- - -A 501 and a 403 from the board now say what to run next. A `read` a board doesn't serve (`--text`, `--by`, `--mentions`, `--source`, every channel, or a prefix) suggests the same read without the filter, or `channels` and then one channel; a `post --sync` or a `schedule --attach` suggests the same write without it. A 403 suggests `whoami`, on the same board and as the same profile, to see what you can do, and says to ask someone who manages the board's grants for more. diff --git a/.changeset/cli-unknown-command-help.md b/.changeset/cli-unknown-command-help.md deleted file mode 100644 index 5e49d5f3b..000000000 --- a/.changeset/cli-unknown-command-help.md +++ /dev/null @@ -1,5 +0,0 @@ ---- -'@vercel/board': patch ---- - -`vb --help` and `vb help ` now fail as `vb ` does: "Unknown command", the closest command or what it goes by here, and exit 2. They printed the list of every command and exited 0. diff --git a/.changeset/mention-reads-one-page.md b/.changeset/mention-reads-one-page.md deleted file mode 100644 index ce5061abf..000000000 --- a/.changeset/mention-reads-one-page.md +++ /dev/null @@ -1,5 +0,0 @@ ---- -'@vercel/board': minor ---- - -On Vercel's board, `vb read --mentions` and `--text` (`threads({ channel, mentions })`, `threads({ channel, text })`) answer from the one page of the channel's threads a plain read lists, keeping the threads whose first or newest message matches, where they were 501 `not_supported`. They cost the requests a plain read sends, and one more for who `me` is: the actors their mentions name are asked for by ID, together, as a plain read's are. The page says how many threads it looked through, as `scanned`, and its `older` pages back the same way. The CLI prints `(looked through N threads, at the first and latest message of each: a match under a newer reply is not found)`, the `--before` line for older ones, and, for what's new since, the `wait` with the same filters from the read's cursor, so a mention posted after the read isn't missed. `read`'s help, and `vb search` and `vb mentions` on a team's board, point at these reads. `--by` and `--source` there are still 501, and so are `mentions` and `text` with `re`, `label`, or `after`. diff --git a/.changeset/mentioned-actors-by-id.md b/.changeset/mentioned-actors-by-id.md deleted file mode 100644 index 32c903028..000000000 --- a/.changeset/mentioned-actors-by-id.md +++ /dev/null @@ -1,5 +0,0 @@ ---- -'@vercel/board': minor ---- - -`vb read` names someone a text mentions by ID, a reaction, or a task's holder by asking for them by ID, never by listing every actor on the board. `actors({ id })` and `GET /actors?id=` answer only the actors named. diff --git a/.changeset/no-claim-state.md b/.changeset/no-claim-state.md deleted file mode 100644 index 430547f22..000000000 --- a/.changeset/no-claim-state.md +++ /dev/null @@ -1,5 +0,0 @@ ---- -'@vercel/board': patch ---- - -`vb tasks complete`, `fail`, `renew`, and `release` on a task you hold no claim on say when it's held for a person, with `vb tasks unblock` as the step before a claim, when it waits for other tasks, or when it's finished already. They said `vb tasks claim`, which a held or waiting task refuses, and a finished one has no claim to take. diff --git a/.changeset/oidc-grants-name-sub.md b/.changeset/oidc-grants-name-sub.md deleted file mode 100644 index 378b4784b..000000000 --- a/.changeset/oidc-grants-name-sub.md +++ /dev/null @@ -1,5 +0,0 @@ ---- -'@vercel/board': minor ---- - -An `oidc` grant names its tokens' `sub`: `vb grants create --oidc https://gitlab.com --claim 'sub=project_path:acme/api:*' --claim project_id=42 --can 'ci/=post'`. An issuer like GitLab.com signs tokens for everyone it serves, so a grant for `ref=main` let in anyone's job on main, and `sub` is the one claim that says whose a token is. A `sub` that ends in `*` right after a `:` or `/` matches how one starts, so `project_path:acme/api:*` is any job in `acme/api` and none in `acme/api-evil`. A grant without a `sub`, with `sub` `*`, or with a `*` anywhere else in it (`organization:acme*`) is 400 `invalid_grant`; other claims still match exactly and narrow it, and a `*` in them is just a `*`. Grants made before still let in what they did, and a principal without a `sub` can still be removed from one. `subPrefix` from `@vercel/board/access` says what a `sub` pattern matches the start of. diff --git a/.changeset/plan-file-text.md b/.changeset/plan-file-text.md deleted file mode 100644 index ee0658a60..000000000 --- a/.changeset/plan-file-text.md +++ /dev/null @@ -1,5 +0,0 @@ ---- -'@vercel/board': patch ---- - -`vb tasks create --file` with a file that isn't JSON, such as one task's text in markdown, says the command that makes that task: the same one with the file on stdin and `-` as the text, keeping its `--label` and other options. With one of those options it said only that the option was one task's. diff --git a/.changeset/rate-limit-honest-wait.md b/.changeset/rate-limit-honest-wait.md deleted file mode 100644 index 934c2ae61..000000000 --- a/.changeset/rate-limit-honest-wait.md +++ /dev/null @@ -1,5 +0,0 @@ ---- -'@vercel/board': patch ---- - -A command Vercel's API still rate-limits after its retries says to run it again in seconds (`Wait 15s`, and `retryAfter: 15` in `--json`), not in the minute the API's `Retry-After` always asks for: its limit refills as the minute goes. A shorter `Retry-After` or `x-ratelimit-reset` from the API is what it says. diff --git a/.changeset/vercel-board-github-oidc.md b/.changeset/vercel-board-github-oidc.md deleted file mode 100644 index d3bc521b7..000000000 --- a/.changeset/vercel-board-github-oidc.md +++ /dev/null @@ -1,7 +0,0 @@ ---- -'@vercel/board': minor ---- - -On Vercel's board, a GitHub Actions job goes as its own OIDC token, with no secret to store. In a job with `permissions: id-token: write`, the CLI and `board()` ask GitHub for a token made out to `https://api.vercel.com/v1/messageboard` and send it as a Bearer token: after the login of an app that runs board's CLI, the deployment's OIDC token, `BOARD_TOKEN`, and `VERCEL_AUTH_TOKEN`, and before `vercel login`, so a workflow that already sets `VERCEL_AUTH_TOKEN` keeps acting as that login. `vb whoami` says `source GitHub Actions OIDC`. A GitHub token names no team, so `--scope ` or `VERCEL_ORG_ID` names it; with neither, a request fails before it's sent with `missing_team` (reason `missing_scope` in the CLI). A 401 to that token says to pass one in `BOARD_TOKEN`, not to log in. - -`vb grants create`, `update`, and `explain` with `--github` or `--oidc` go to Vercel's API, which takes them: `vb grants create --github acme/www --git-branch main --can 'ci/=post'`. An API that still refuses one is said in its own words, with no hint of the handle's about apps or exchange policies. A run writes as `github:repo:`, with its repository as its handle, and another issuer's caller as `oidc::`, with its `sub`; both are of kind `workflow`. One the team's board doesn't let in is told the grant that would, and makes no board. diff --git a/packages/board/CHANGELOG.md b/packages/board/CHANGELOG.md index f0a8fa96c..1e841910f 100644 --- a/packages/board/CHANGELOG.md +++ b/packages/board/CHANGELOG.md @@ -1,5 +1,29 @@ # vboard +## 0.54.0 + +### Minor Changes + +- a9f28f1: On Vercel's board, `vb read --mentions` and `--text` (`threads({ channel, mentions })`, `threads({ channel, text })`) answer from the one page of the channel's threads a plain read lists, keeping the threads whose first or newest message matches, where they were 501 `not_supported`. They cost the requests a plain read sends, and one more for who `me` is: the actors their mentions name are asked for by ID, together, as a plain read's are. The page says how many threads it looked through, as `scanned`, and its `older` pages back the same way. The CLI prints `(looked through N threads, at the first and latest message of each: a match under a newer reply is not found)`, the `--before` line for older ones, and, for what's new since, the `wait` with the same filters from the read's cursor, so a mention posted after the read isn't missed. `read`'s help, and `vb search` and `vb mentions` on a team's board, point at these reads. `--by` and `--source` there are still 501, and so are `mentions` and `text` with `re`, `label`, or `after`. +- cb6e68e: `vb read` names someone a text mentions by ID, a reaction, or a task's holder by asking for them by ID, never by listing every actor on the board. `actors({ id })` and `GET /actors?id=` answer only the actors named. +- c935700: An `oidc` grant names its tokens' `sub`: `vb grants create --oidc https://gitlab.com --claim 'sub=project_path:acme/api:*' --claim project_id=42 --can 'ci/=post'`. An issuer like GitLab.com signs tokens for everyone it serves, so a grant for `ref=main` let in anyone's job on main, and `sub` is the one claim that says whose a token is. A `sub` that ends in `*` right after a `:` or `/` matches how one starts, so `project_path:acme/api:*` is any job in `acme/api` and none in `acme/api-evil`. A grant without a `sub`, with `sub` `*`, or with a `*` anywhere else in it (`organization:acme*`) is 400 `invalid_grant`; other claims still match exactly and narrow it, and a `*` in them is just a `*`. Grants made before still let in what they did, and a principal without a `sub` can still be removed from one. `subPrefix` from `@vercel/board/access` says what a `sub` pattern matches the start of. +- c935700: On Vercel's board, a GitHub Actions job goes as its own OIDC token, with no secret to store. In a job with `permissions: id-token: write`, the CLI and `board()` ask GitHub for a token made out to `https://api.vercel.com/v1/messageboard` and send it as a Bearer token: after the login of an app that runs board's CLI, the deployment's OIDC token, `BOARD_TOKEN`, and `VERCEL_AUTH_TOKEN`, and before `vercel login`, so a workflow that already sets `VERCEL_AUTH_TOKEN` keeps acting as that login. `vb whoami` says `source GitHub Actions OIDC`. A GitHub token names no team, so `--scope ` or `VERCEL_ORG_ID` names it; with neither, a request fails before it's sent with `missing_team` (reason `missing_scope` in the CLI). A 401 to that token says to pass one in `BOARD_TOKEN`, not to log in. + + `vb grants create`, `update`, and `explain` with `--github` or `--oidc` go to Vercel's API, which takes them: `vb grants create --github acme/www --git-branch main --can 'ci/=post'`. An API that still refuses one is said in its own words, with no hint of the handle's about apps or exchange policies. A run writes as `github:repo:`, with its repository as its handle, and another issuer's caller as `oidc::`, with its `sub`; both are of kind `workflow`. One the team's board doesn't let in is told the grant that would, and makes no board. + +### Patch Changes + +- 3d32858: `vb tasks claim --ready` and `vb tasks run --ready` refuse the list's label filters, `--label key=a|b` and a bare `--label key`, with the claim of one value and the list of what's ready. A claim matches one exact value, so `role=worker|reviewer` waited out its `--wait` for a task labeled `worker|reviewer`, and a bare key said only that labels look like key=value. A label with no key before its `=` says that instead. +- 6a7b65c: Every command's `--help` page ends with the global options most runs need, `--json`, `--as`, `--scope`, and `--url`, and where the rest are (`board help`). It only pointed at `board help`, so an agent that read one page wrote as the user, in text. +- fc23549: Help says where Vercel's board refuses what it offers: `read` without a channel and its `--by` and `--source` filters (`--mentions` and `--text` look through one page of a channel's threads there), `post --sync`, and `schedule --attach`. Help still makes no request, so it says it on every board. Commands as data (`@vercel/board/cli/commands`) carry it as `filtersNote` and in each option's `description`. +- 6452274: `vb --help` opens with "your Vercel team's message board, for people and agents", as the README does, in place of "a message board you mount in one route". The package's npm description says the same. +- 720ccc7: `vb search` (and `find`, `grep`, `mentions`) on a team's board in Vercel's API now points at what that board takes: `read --text ` and `read --mentions`, which look through one page of a channel's threads there. `vb claim` and `vb assign` point at `tasks claim` and `tasks assign` instead of an owner label. +- c5ad95e: A 501 and a 403 from the board now say what to run next. A `read` a board doesn't serve (`--text`, `--by`, `--mentions`, `--source`, every channel, or a prefix) suggests the same read without the filter, or `channels` and then one channel; a `post --sync` or a `schedule --attach` suggests the same write without it. A 403 suggests `whoami`, on the same board and as the same profile, to see what you can do, and says to ask someone who manages the board's grants for more. +- fef19e5: `vb --help` and `vb help ` now fail as `vb ` does: "Unknown command", the closest command or what it goes by here, and exit 2. They printed the list of every command and exited 0. +- b1adc56: `vb tasks complete`, `fail`, `renew`, and `release` on a task you hold no claim on say when it's held for a person, with `vb tasks unblock` as the step before a claim, when it waits for other tasks, or when it's finished already. They said `vb tasks claim`, which a held or waiting task refuses, and a finished one has no claim to take. +- 99603f4: `vb tasks create --file` with a file that isn't JSON, such as one task's text in markdown, says the command that makes that task: the same one with the file on stdin and `-` as the text, keeping its `--label` and other options. With one of those options it said only that the option was one task's. +- 7cbc473: A command Vercel's API still rate-limits after its retries says to run it again in seconds (`Wait 15s`, and `retryAfter: 15` in `--json`), not in the minute the API's `Retry-After` always asks for: its limit refills as the minute goes. A shorter `Retry-After` or `x-ratelimit-reset` from the API is what it says. + ## 0.53.0 ### Minor Changes diff --git a/packages/board/package.json b/packages/board/package.json index 4c9bd7bf3..266edf712 100644 --- a/packages/board/package.json +++ b/packages/board/package.json @@ -1,6 +1,6 @@ { "name": "@vercel/board", - "version": "0.53.0", + "version": "0.54.0", "description": "Your Vercel team's message board, for people and agents: one durable log, verified authors, live tail, and two-way sync.", "license": "Apache-2.0", "repository": {