Use postfixed formatter release tags - #2
Conversation
|
Important Review skippedAuto reviews are limited based on label configuration. 🏷️ Required labels (at least one) (1)
🚫 Excluded labels (none allowed) (2)
Please check the settings in the CodeRabbit UI or the ⚙️ Run configurationConfiguration used: Organization UI Review profile: ASSERTIVE Plan: Pro Run ID: You can disable this status message by setting the Use the checkbox below for a quick retry:
Comment |
cdfd9e4 to
c50b8bd
Compare
|
Got https://github.com/kjanat/powershell-formatter now.... |
|
Superseded by the migration to Generated by Claude Code |
Coordinate both formatter packages at version 0.1.1 while keeping their GitHub releases namespaced as
0.1.1-dprintand0.1.1-npm.The dprint plugin continues to use
plugins.dprint.dev. Its schema URL now contains the actual postfixed release tag, while the proxy reports the embedded formatter version as0.1.1. The npm package metadata and installation documentation are updated to 0.1.1.The corresponding proxy support is proposed in dprint/plugins#76. Do not publish the formatter tags until that proxy change is deployed.
Validation:
mise exec -- Formatter/Dprint/scripts/e2e.shmise exec -- dotnet publish Formatter/Wasm/Formatter.Wasm.csproj --configuration Release --source https://api.nuget.org/v3/index.jsonmise exec -- pwsh Formatter/Wasm/scripts/Test-Package.ps1 -PackageDirectory Formatter/Wasm/bin/Release/net8.0/browser-wasm/AppBundleactionlintactup checkdprint check