Commit Graph
14 Commits
Author SHA1 Message Date
Ee Durbin c3813a501f add a workflow for preparing releases (#28486)
this is primarily useful for testing the sts token exchange in a
non-load bearing environment ahead of merging #28484
, but may be useful for maintainers :)

`automations` environment has been created and `STS_API_URL` secret set
2026-09-10 10:44:26 -04:00
zaniebotandZanie Blue 1047cc20a2 Use centralized crates.io publishing policies (#28285)
Release preparation still directs new crates to the local bootstrap
utility, which requires a crates.io owner token and tracks configured
crates in `.known-crates`. Use `astral-sh/crates-policies` as the source
of truth instead, matching
[astral-sh/uv#20449](https://github.com/astral-sh/uv/pull/20449).
`scripts/release.sh` now runs the shared workspace checker, the
contribution guide points to the central registration process, and the
duplicate setup utility and local crate list are removed.

Co-authored-by: Zanie Blue <contact@zanie.dev>
2026-09-03 11:50:54 -05:00
Brent Westbrook cab001e5de Disable uv preview for releases and pre-commit hooks (#27939)
Summary
--

This partially reverts https://github.com/astral-sh/ruff/pull/27935 as
an alternative to enabling
preview everywhere. Preview was initially enabled ~2 years ago (#11496),
and we probably want to be
more selective about preview features now.

Test Plan
--

Today's release, previous errors:

-
https://github.com/astral-sh/ruff/actions/runs/32390111175/job/96493893174?pr=27937
-
https://github.com/astral-sh/ruff/actions/runs/32390111175/job/96493998150?pr=27937
2026-08-20 12:41:40 -04:00
Brent Westbrook 4827bf7cb4 Export UV_DEFAULT_INDEX in release.sh (#27934)
Summary
--

Before this, running `./scripts/release.sh` produced this error on my
machine:

```console
❯ ./scripts/release.sh
Updating metadata with rooster...
warning: `VIRTUAL_ENV=/Users/brw/.virtualenvs/openai` does not match the project environment path `.venv` and will be ig
nored; use `--active` to target the active environment instead
error: The lockfile at `uv.lock` needs to be updated, but `--locked` was provided.

hint: To update the lockfile, run `uv lock`.
```

Passing an additional `--default-index` flag to the initial `uv run`
also works, but it seems easier
to export the environment variable for the whole workflow.

Test Plan
--

Manual testing in today's release
2026-08-20 11:54:39 -04:00
zaniebotandzaniebot 19b8990691 Use an explicit PyPI index during release preparation (#27901)
`scripts/release.sh` uses `--no-config` to avoid recording Socket's
registry URLs, but this also discards `exclude-newer` and other
configuration. Set `--default-index` to PyPI for the lockfile update and
crates.io publishing check so these commands use the public default
index while retaining the remaining settings.

Co-authored-by: zaniebot <242828183+zaniebot@users.noreply.github.com>
2026-08-19 19:01:25 +00:00
Shaan Majid c5ee52a357 chore: lock rooster release dependency (#26509)
## Summary

Adds `rooster` to a new `release` dependency group, locks its full
dependency tree via `uv.lock`, and updates the release script to use the
locked installation for deterministic transitive dependency resolution.

Discussed in
https://github.com/astral-sh/ruff/pull/26463#discussion_r3504248600;
mirrored from astral-sh/uv#19923

## Test Plan

- `uv lock --check`
- `./scripts/release.sh` in a temporary worktree
2026-07-02 01:27:26 -07:00
Shaan Majid c360a05e9a chore: run prek from a locked uv dev group (#26463)
## Summary

Add a locked `uv` workflow for running `prek` in CI and local
development.

This pins `prek` via a new `dev` PEP 735 dependency group, introduces a
committed `uv.lock` file, and updates CI to run `prek` through `uv run
--only-group dev --locked`. It also adds a frozen `uv-lock` pre-commit
hook to ensure future changes keep the lockfile in sync. Lastly, I
noticed that some pre-commit priority blocks did not match the comment
sections, so this does some opportunistic cleanup to move these around.

Atop #26461. Closes #26386.

## Test Plan

```bash
uv run --only-dev prek --all-files
```
2026-07-01 01:09:42 -07:00
Charlie Marsh dff016b7a4 Publish Ruff crates to crates.io (#26271)
## Summary

Publish Ruff's production Rust crates to crates.io as part of the
existing release workflow. This follows uv's setup: workspace
dependencies carry registry-compatible version pins, internal crates
receive generated READMEs and an explicit versioning policy, CI dry-runs
the full workspace publish, and release jobs publish missing crate
versions idempotently through crates.io trusted publishing.

The publishing set contains 32 packages: Ruff's CLI, WASM package,
server, linter, formatter, parser, and the internal Ruff component
crates required by them. It also includes `ty_module_resolver`,
`ty_site_packages`, and `ty_static`, because those three crates are part
of Ruff's normal dependency closure.

The publishing set deliberately excludes:

- Test-only crates: `mdtest`, `ruff_mdtest`,
`ruff_python_ast_integration_tests`, and
`ruff_python_trivia_integration_tests`.
- Benchmark and development crates: `ruff_benchmark` and `ruff_dev`.
- All remaining `ty_*` crates.

These packages retain `publish = false`, so bootstrap, version bumping,
README generation, CI dry-runs, and release publishing skip them through
Cargo metadata instead of a separate hard-coded allowlist.

The crates.io job is intentionally independent of release announcement,
so a crates.io outage cannot block the existing binary, PyPI, npm, or
GitHub release outputs. A bootstrap script reserves new crate names,
configures the release workflow as each crate's trusted publisher,
enables trusted-publishing-only releases, and records configured crates
for idempotent reruns.

The full workspace publish dry-run packages and verifies all 32 selected
crates.

Closes https://github.com/astral-sh/ruff/issues/43.
2026-06-23 12:49:23 -04:00
Charlie Marsh 818da49490 Revert accidental release preview change (#25159)
This was an accidental change for testing in
[astral-sh/ruff#25154](https://github.com/astral-sh/ruff/pull/25154).
2026-05-14 13:35:48 +00:00
Charlie Marsh 2522549901 Remove shellcheck from prek (#25154)
## Summary

`shellcheck-py` requires a build-time binary download from GitHub, which
is rejected by some firewalls. There's also
[`shellcheck-precommit`](https://github.com/koalaman/shellcheck-precommit),
but that uses a Docker-based hook, and would introduce a Docker
requirement to our `prek` setup that doesn't currently exist.

So this PR just removes it from our pre-commit setup, and uses
`actions/setup-go` instead with a dedicated CI job.
2026-05-14 12:34:07 +01:00
Amethyst Reese 8737a2d5f5 Bump v0.14.3 (#21152)
- **Upgrade to rooster==0.1.1**
- **Changelog for v0.14.3**
- **Bump v0.14.3**
2025-10-30 17:06:29 -07:00
Brent Westbrook 7331d393c5 Update rooster to 0.1.0 (#20575)
Summary
--

This reduces the page size of GraphQL queries
(https://github.com/zanieb/rooster/pull/85), hopefully helping with some
of the 502s we've been hitting.

Test Plan
--

I ran the release script, and it succeeded after failing several times
on the old rooster version.
2025-09-25 10:11:21 -04:00
Dylan b9b5755368 Upgrade to the latest rooster version and include contributors in CHANGELOG (#20472)
What it says on the tin!

Manually tested the release script and it appears to produce the right
thing.
2025-09-18 13:43:39 -05:00
Zanie BlueandT-256 c13c60bc47 Update release script to match uv (#11496)
See https://github.com/astral-sh/uv/pull/3764

---------

Co-authored-by: T-256 <132141463+T-256@users.noreply.github.com>
2024-07-03 07:35:28 -05:00