Skip to content

Version Packages - #774

Merged
julianbenegas merged 1 commit into
mainfrom
changeset-release/main
Nov 20, 2026
Merged

julianbenegas merged 1 commit into
mainfrom
changeset-release/main

Conversation

@github-actions

@github-actions github-actions Bot commented Nov 19, 2026 •

Copy link
Copy Markdown
Contributor

This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to main, this PR will be updated.

Releases

@vercel/board@0.54.0

Minor Changes

  • a9f28f1: On Vercel's board, vb read <channel> --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 <team ID> 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:<repository_id>, with its repository as its handle, and another issuer's caller as oidc:<issuer host and path>:<sub>, 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 <channel> --text <phrase> and read <channel> --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 <unknown> --help and vb help <unknown> now fail as vb <unknown> 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.

@github-actions
github-actions Bot force-pushed the changeset-release/main branch 6 times, most recently from fa39349 to 3c65954 Compare November 20, 2026 02:33
@github-actions
github-actions Bot force-pushed the changeset-release/main branch from 3c65954 to 8893587 Compare November 20, 2026 13:54

@vercel vercel Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Approving at Nicolás Montone's request, after checking:

  1. Only deletes the 12 changesets, writes packages/board/CHANGELOG.md, and bumps package.json 0.53.0 → 0.54.0. No source changes.
  2. The changelog has 12 entries, one per changeset. Of the 15 PRs since 0.53.0, #768 (swarm template) and #754 (skill) don't ship in the package, and #752 (docs) has no changeset. The #767 entry describes main's --mentions/--text reads and hints.
  3. 2 minors (#767, #760) and 10 patches → 0.54.0.
  4. check is green on main at b9ae9ea, the commit this releases (after #776 fixed the test that failed at a9f28f1).

@github-actions
github-actions Bot force-pushed the changeset-release/main branch from 8893587 to 55a8552 Compare November 20, 2026 17:12
@julianbenegas
julianbenegas merged commit 86694bd into main Nov 20, 2026
7 checks passed
@julianbenegas
julianbenegas deleted the changeset-release/main branch November 20, 2026 17:19
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant