Skip to content

chore: modernize CI and add npm install option to README#28

Open
dsherret wants to merge 7 commits into
mainfrom
chore/modernize-ci-and-readme
Open

chore: modernize CI and add npm install option to README#28
dsherret wants to merge 7 commits into
mainfrom
chore/modernize-ci-and-readme

Conversation

@dsherret

Copy link
Copy Markdown
Member

Summary

  • Replace deprecated ::set-output with $GITHUB_OUTPUT in ci.yml.
  • Bump release.yml to use jsr:@dprint/automation@0.10.3/tasks/publish-release (from the older raw.githubusercontent.com/dprint/automation/0.10.0/... URL).
  • Add dprint add npm:@dprint/biome to the README install instructions alongside the existing dprint add biome.

Test plan

  • CI passes on this branch.

dsherret added 7 commits May 23, 2026 16:12
- Replace deprecated `::set-output` with `$GITHUB_OUTPUT` in ci.yml
- Bump release.yml to use jsr:@dprint/automation@0.10.3/tasks/publish-release
- Add `dprint add npm:@dprint/biome` install option in README
Previously update.ts only updated the biome tag in Cargo.toml. When
biome bumps its declared rust-toolchain (e.g. across 2.x), CI would
silently end up trying to compile newer biome on the old toolchain.
Match what dprint-plugin-ruff already does: fetch biome's
rust-toolchain.toml at the new tag and bump our local channel to match
(only ever upgrading; never downgrading).
rust-toolchain.toml channels may be just "1.84" (no patch); pad to
MAJOR.MINOR.PATCH so @std/semver can parse it.
Aligns with how dprint-plugin-ruff's update.ts already calls
raw.githubusercontent.com. The 404 branch here uses `.noThrow()` so the
404 still falls through to "upstream has no rust-toolchain.toml" rather
than throwing.
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