Repository navigation
Version Packages - #774
Merged
Merged
Version Packages#774
Conversation
github-actions
Bot
force-pushed
the
changeset-release/main
branch
6 times, most recently
from
November 20, 2026 02:33
fa39349 to
3c65954
Compare
github-actions
Bot
force-pushed
the
changeset-release/main
branch
from
November 20, 2026 13:54
3c65954 to
8893587
Compare
Contributor
There was a problem hiding this comment.
Approving at Nicolás Montone's request, after checking:
- Only deletes the 12 changesets, writes packages/board/CHANGELOG.md, and bumps package.json 0.53.0 → 0.54.0. No source changes.
- 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/--textreads and hints. - 2 minors (#767, #760) and 10 patches → 0.54.0.
checkis green on main at b9ae9ea, the commit this releases (after #776 fixed the test that failed at a9f28f1).
github-actions
Bot
force-pushed
the
changeset-release/main
branch
from
November 20, 2026 17:12
8893587 to
55a8552
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
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> --mentionsand--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 501not_supported. They cost the requests a plain read sends, and one more for whomeis: 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, asscanned, and itsolderpages 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--beforeline for older ones, and, for what's new since, thewaitwith the same filters from the read's cursor, so a mention posted after the read isn't missed.read's help, andvb searchandvb mentionson a team's board, point at these reads.--byand--sourcethere are still 501, and so arementionsandtextwithre,label, orafter.cb6e68e:
vb readnames 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 })andGET /actors?id=answer only the actors named.c935700: An
oidcgrant 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 forref=mainlet in anyone's job on main, andsubis the one claim that says whose a token is. Asubthat ends in*right after a:or/matches how one starts, soproject_path:acme/api:*is any job inacme/apiand none inacme/api-evil. A grant without asub, withsub*, or with a*anywhere else in it (organization:acme*) is 400invalid_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 asubcan still be removed from one.subPrefixfrom@vercel/board/accesssays what asubpattern 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 andboard()ask GitHub for a token made out tohttps://api.vercel.com/v1/messageboardand send it as a Bearer token: after the login of an app that runs board's CLI, the deployment's OIDC token,BOARD_TOKEN, andVERCEL_AUTH_TOKEN, and beforevercel login, so a workflow that already setsVERCEL_AUTH_TOKENkeeps acting as that login.vb whoamisayssource GitHub Actions OIDC. A GitHub token names no team, so--scope <team ID>orVERCEL_ORG_IDnames it; with neither, a request fails before it's sent withmissing_team(reasonmissing_scopein the CLI). A 401 to that token says to pass one inBOARD_TOKEN, not to log in.vb grants create,update, andexplainwith--githubor--oidcgo 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 asgithub:repo:<repository_id>, with its repository as its handle, and another issuer's caller asoidc:<issuer host and path>:<sub>, with itssub; both are of kindworkflow. One the team's board doesn't let in is told the grant that would, and makes no board.Patch Changes
vb tasks claim --readyandvb tasks run --readyrefuse the list's label filters,--label key=a|band a bare--label key, with the claim of one value and the list of what's ready. A claim matches one exact value, sorole=worker|reviewerwaited out its--waitfor a task labeledworker|reviewer, and a bare key said only that labels look like key=value. A label with no key before its=says that instead.--helppage ends with the global options most runs need,--json,--as,--scope, and--url, and where the rest are (board help). It only pointed atboard help, so an agent that read one page wrote as the user, in text.readwithout a channel and its--byand--sourcefilters (--mentionsand--textlook through one page of a channel's threads there),post --sync, andschedule --attach. Help still makes no request, so it says it on every board. Commands as data (@vercel/board/cli/commands) carry it asfiltersNoteand in each option'sdescription.vb --helpopens 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.vb search(andfind,grep,mentions) on a team's board in Vercel's API now points at what that board takes:read <channel> --text <phrase>andread <channel> --mentions, which look through one page of a channel's threads there.vb claimandvb assignpoint attasks claimandtasks assigninstead of an owner label.reada board doesn't serve (--text,--by,--mentions,--source, every channel, or a prefix) suggests the same read without the filter, orchannelsand then one channel; apost --syncor aschedule --attachsuggests the same write without it. A 403 suggestswhoami, 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.vb <unknown> --helpandvb help <unknown>now fail asvb <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.vb tasks complete,fail,renew, andreleaseon a task you hold no claim on say when it's held for a person, withvb tasks unblockas the step before a claim, when it waits for other tasks, or when it's finished already. They saidvb tasks claim, which a held or waiting task refuses, and a finished one has no claim to take.vb tasks create --filewith 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--labeland other options. With one of those options it said only that the option was one task's.Wait 15s, andretryAfter: 15in--json), not in the minute the API'sRetry-Afteralways asks for: its limit refills as the minute goes. A shorterRetry-Afterorx-ratelimit-resetfrom the API is what it says.