Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

chore: publish some crates and add add workflow for publish crates #444

Merged
merged 7 commits into from
Oct 2, 2023
Merged
Show file tree
Hide file tree
Changes from 5 commits
Commits
File filter

Filter by extension

Filter by extension


Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
21 changes: 21 additions & 0 deletions .github/workflows/release_crates.yml
Original file line number Diff line number Diff line change
@@ -0,0 +1,21 @@
name: Release crates
on:
workflow_dispatch:
schedule:
- cron: '0 0 * * 2-6'
push:
branches:
- main

jobs:
environment: carte-publish
nissy-dev marked this conversation as resolved.
Show resolved Hide resolved
release:
name: Publish
runs-on: ubuntu-latest
steps:
- name: Checkout repository
uses: actions/checkout@v4
- name: Login to crate.io
run: cargo login ${{ secrets.CRATES_IO_TOKEN }}
nissy-dev marked this conversation as resolved.
Show resolved Hide resolved
- name: Publish crates to crates.io
run: ./scripts/publish-crates.sh --execute
2 changes: 2 additions & 0 deletions CONTRIBUTING.md
Original file line number Diff line number Diff line change
Expand Up @@ -401,6 +401,8 @@ When releasing a new version of a Biome, follow these steps:
1. [ ] Update `version` in [Biome's LSP package.json](./editors/vscode/package.json) if applicable.
Note that the LSP follows a [distinct versioning scheme](https://biomejs.dev/internals/versioning/#visual-studio-code-extension).

1. [ ] Update `version` in each published crates if applicable. (`Cargo.toml` and `crates/**/Cargo.toml`)

1. [ ] Linter rules have a `version` metadata directly defined in their implementation.
This field is set to `next` for newly created rules.
This field must be updated to the new version.
Expand Down
Loading
Loading