From 356d3c9b9636da696618285e15b234c5015f05eb Mon Sep 17 00:00:00 2001 From: zaniebot Date: Thu, 22 Oct 2026 14:54:33 -0500 Subject: [PATCH] Document manual maintenance of the release workflow (#27853) --- .github/workflows/release.yml | 3 ++- .prettierignore | 2 +- AGENTS.md | 4 ---- 3 files changed, 3 insertions(+), 6 deletions(-) diff --git a/.github/workflows/release.yml b/.github/workflows/release.yml index 16158e28a7..98ccb4e213 100644 --- a/.github/workflows/release.yml +++ b/.github/workflows/release.yml @@ -1,4 +1,5 @@ -# This file was autogenerated by dist: https://axodotdev.github.io/cargo-dist +# Originally generated by `cargo-dist`. This workflow is now maintained manually. +# https://axodotdev.github.io/cargo-dist # # Copyright 2022-2024, axodotdev # SPDX-License-Identifier: MIT or Apache-2.0 diff --git a/.prettierignore b/.prettierignore index 0e8c9be149..28608bc120 100644 --- a/.prettierignore +++ b/.prettierignore @@ -1,2 +1,2 @@ -# Auto-generated by `cargo-dist`. +# Preserve the existing formatting of the manually maintained release workflow. .github/workflows/release.yml diff --git a/AGENTS.md b/AGENTS.md index 9cc6860312..695d9483c9 100644 --- a/AGENTS.md +++ b/AGENTS.md @@ -205,10 +205,6 @@ For Salsa-cached values, avoid retaining excess collection capacity. Prefer boxe Salsa caching can occur due to a function/method having `#[salsa::tracked]` on it, or due to a struct with `#[salsa::interned]` being constructed. -## Generated Release Workflow - -Parts of `.github/workflows/release.yml` are generated by cargo-dist from `dist-workspace.toml`. Before editing the release workflow, check whether the relevant section is generated. Prefer changing `dist-workspace.toml` or the referenced reusable workflow instead of editing generated YAML. After modifying cargo-dist configuration, regenerate the workflow with the cargo-dist version pinned in `dist-workspace.toml` and inspect the resulting diff to ensure the change will survive future regenerations. - ## Development Guidelines - All significant changes must be tested. Add or update focused tests for semantic changes when existing coverage does not already establish the intended behavior.