Python
/
ruff
mirror of https://github.com/astral-sh/ruff
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Clarify release workflow steps in CONTRIB guide (#9232) 

We always recommend providing the SHA and since
https://github.com/astral-sh/ruff/pull/7279 it does not need to be the
latest commit on `main`.
This commit is contained in:
Zanie Blue 2023-12-21 12:25:18 -06:00 committed by GitHub
parent 0263f2715e
commit 3c2b800d26
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 3 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

5
CONTRIBUTING.md
View File

@ -328,8 +328,9 @@ We use an experimental in-house tool for managing releases.
1. Highlight any breaking changes in `BREAKING_CHANGES.md` 1. Highlight any breaking changes in `BREAKING_CHANGES.md`
1. Create a pull request with the changelog and version updates 1. Create a pull request with the changelog and version updates
1. Merge the PR 1. Merge the PR
1. Run the release workflow with the version number (without starting `v`) as input. Make sure 1. Run the [release workflow](https://github.com/astral-sh/ruff/actions/workflows/release.yaml) with:
main has your merged PR as last commit - The new version number (without starting `v`)
- The commit hash of the merged release pull request on `main`
1. The release workflow will do the following: 1. The release workflow will do the following:
1. Build all the assets. If this fails (even though we tested in step 4), we haven't tagged or 1. Build all the assets. If this fails (even though we tested in step 4), we haven't tagged or
uploaded anything, you can restart after pushing a fix. uploaded anything, you can restart after pushing a fix.