From 48e82d8fc74f3cfb7fad0c2c2d2cacec6f8b26f3 Mon Sep 17 00:00:00 2001 From: Stephan Boyer Date: Wed, 21 Feb 2024 20:22:09 -0800 Subject: [PATCH] Use Tagref file references where applicable --- MAINTAINERS.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/MAINTAINERS.md b/MAINTAINERS.md index f78f4e58..ecfc2073 100644 --- a/MAINTAINERS.md +++ b/MAINTAINERS.md @@ -31,6 +31,6 @@ The GitHub workflow will fail initially because the jobs which test the installe Releasing a new version is a four-step process: 1. Run `(cd integration_tests/typescript-web && npm ci && npm run dev)` to run the browser-based integration tests. This is the only test suite that isn't automated. -2. Bump the version in `Cargo.toml`, run `cargo build` to update `Cargo.lock`, and update `CHANGELOG.md` with information about the new version. Ship those changes as a single commit. -3. Once the GitHub workflow has finished on the `main` branch, update the version in `install.sh` to point to the new release. +2. Bump the version in `[file:Cargo.toml]`, run `cargo build` to update `[file:Cargo.lock]`, and update `[file:CHANGELOG.md]` with information about the new version. Ship those changes as a single commit. +3. Once the GitHub workflow has finished on the `main` branch, update the version in `[file:install.sh]` to point to the new release. 4. Create a pull request in the `Homebrew/homebrew-core` repository on GitHub to bump the version in [this file](https://github.com/Homebrew/homebrew-core/blob/HEAD/Formula/t/typical.rb).