What changed
v0.0.42 gave the VS Code extension a path to the Marketplace. This release tightens two things in it, after reading what the publishing tool actually supports rather than assuming.
Fixed
- No more parsing error text. Re-running a tag was made harmless by
searching the failure output for the words "already exists". That
works until the Marketplace rewords its message, at which point a
re-run starts failing releases for no reason. The tool has a
--skip-duplicateflag for precisely this case, so it now uses it. - The extension manifest was a release behind. The publish step refuses to run when the manifest and the tag disagree about the version, which is the right check, and it would have caught this at the last possible moment. The version bump now covers the manifest.
The part worth knowing about
Publishing authenticates with an Azure DevOps personal access token, and those tokens are on a clock. Azure retires the "all accessible organizations" kind, which is the kind the Marketplace requires, on 1 December 2026.
There are two successors. Neither is ready:
- Trusted publishing is the good one. The CI system proves its own identity, exchanges that proof for a credential that lives for minutes, and nothing is stored anywhere. It is the destination. But the flag is still hidden in pre-release builds of the publishing tool.
- Entra ID works today, but wants a service principal and a federated credential set up first.
Rather than leave that in a chat log, the release workflow now carries the deadline and both options as a comment at the exact line that has to change.
Upgrading
Bump every noyalib crate you use to 0.0.43. No public API changed
shape, and no library code changed at all.