Skip to content

docs(distribution): record the extension's first trusted publishing release - #2115

Merged
cevheri merged 2 commits into
mainfrom
docs/vscode-extension-trusted-publishing
Oct 30, 2026
Merged

cevheri merged 2 commits into
mainfrom
docs/vscode-extension-trusted-publishing

Conversation

@cevheri

@cevheri cevheri commented Oct 30, 2026 •

Copy link
Copy Markdown
Member

0.4.1 was published by the release workflow's publish job (run https://github.com/libredb/libredb-studio/actions/runs/41137115534), with trusted publishing and no stored Marketplace token. This brings the docs in line, and records that the publish no longer waits for an approval:

  • distribution/channels.yaml: the vscode-marketplace row goes from manual_ui to ci_publish, still on_demand, since the extension's tags are cut separately from product releases.
  • docs/CHANNELS.md: regenerated with bun run distribution:matrix; the row now reads "Automated, on demand".
  • docs/DISTRIBUTION.md: records the first run, and the removal of the environment's required reviewers on 31 October 2026. The reviewers were the same members who can push a tag, and no other automated channel has an approval step.
  • The environment itself stays: the trusted publishing policy names it, and it still admits only vscode-extension-* tags. The workflow header comment and the publish test's title drop "requires a reviewer"; the test's assertions are unchanged.

Verified locally: the distribution, channel and workflow unit tests, channels:showcase:check, the matrix check, format and readme:check.

…elease

0.4.1 went up from the vscode-extension-0.4.1 tag through the release
workflow's publish job (run 41137115534), so the vscode-marketplace channel
row moves from manual_ui to ci_publish, still on demand, and the matrix in
CHANNELS.md is regenerated. DISTRIBUTION.md records that first run among the
decisions and in the channel row paragraph.
…her channels

The vscode-marketplace environment's required reviewers were removed after
0.4.1: they were the same members who can push a tag, so the approval added
a second click, not a second person, and no other automated channel has one.
The environment stays, since the trusted publishing policy names it and its
deployment rule still admits only vscode-extension-* tags. The workflow
header, the publish test's title, the channel row and DISTRIBUTION.md now
say so.
@sonarqubecloud

Copy link
Copy Markdown

@cevheri
cevheri merged commit 0c1cfc3 into main Oct 30, 2026
30 checks passed
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