This repository was archived by the owner on Feb 5, 2026. It is now read-only.
Rename docs/community.md to docscommunity.md#1480
Closed
Tsukimarf wants to merge 288 commits intoastral-sh:feature/uv-in-versionfrom
Closed
Rename docs/community.md to docscommunity.md#1480Tsukimarf wants to merge 288 commits intoastral-sh:feature/uv-in-versionfrom
Tsukimarf wants to merge 288 commits intoastral-sh:feature/uv-in-versionfrom
Conversation
* Makefile: fix path for generated python code * workflows: add workflow to automatically generate uv downloads
Co-authored-by: mitsuhiko <7396+mitsuhiko@users.noreply.github.com>
This PR edits the copy in `workspaces.md` adding small improvements in use of prepositions, punctuation, etc. Addresses astral-sh#1396
- Synced latest Python releases <sup>Auto-generated by [sync-python-releases.yml](https://github.com/astral-sh/rye/blob/main/.github/workflows/sync-python-releases.yml)</sup> Co-authored-by: mitsuhiko <7396+mitsuhiko@users.noreply.github.com> Co-authored-by: zanieb <contact@zanie.dev>
Resolves: astral-sh#1426 This pull request includes an update to the compatibility range for the supported Python versions in the `is_self_compatible_toolchain` function. * [`rye/src/bootstrap.rs`](diffhunk://#diff-5e3b4dd9c9d72709e7551b50ad0bb8933e251e3f7ea71370a13637900c1b349cL285-R287): Updated the supported Python versions to include cpython 3.13.
Fixes astral-sh#1436 This seemed like the simplest fix to ignore freethreaded builds. Couple other thoughts/things that could happen later: * this won't help with folks who already downloaded a 3.13.0 CPython (they'll need to `rye toolchain remove cpython@3.13.0` first, and then `fetch` it again) * `PlatformTriple#flavor` should probably be a `set[str]`; so `freethreaded+pgo+lto-full` would become `{'freethreaded', 'pgo', 'lto'}` (tbd what to do with `full`)
## Summary The `macos-12` runners are deprecated: https://github.com/astral-sh/rye/actions/runs/12244443745
CI checks fail for an unrelated reason, see astral-sh#1458 --------- Co-authored-by: Charlie Marsh <charlie.r.marsh@gmail.com>
## Summary Use a consistent Rust version so tests and lint errors, etc., don't start failing sporadically with each release.
- Synced latest UV releases <sup>Auto-generated by [sync-uv-releases.yml](https://github.com/astral-sh/rye/blob/main/.github/workflows/sync-uv-releases.yml)</sup> --------- Co-authored-by: charliermarsh <1309177+charliermarsh@users.noreply.github.com> Co-authored-by: Charlie Marsh <charlie.r.marsh@gmail.com>
- Synced latest Python releases <sup>Auto-generated by [sync-python-releases.yml](https://github.com/astral-sh/rye/blob/main/.github/workflows/sync-python-releases.yml)</sup> --------- Co-authored-by: mitsuhiko <7396+mitsuhiko@users.noreply.github.com> Co-authored-by: Charlie Marsh <charlie.r.marsh@gmail.com>
- Synced latest UV releases <sup>Auto-generated by [sync-uv-releases.yml](https://github.com/astral-sh/rye/blob/main/.github/workflows/sync-uv-releases.yml)</sup> Co-authored-by: mitsuhiko <7396+mitsuhiko@users.noreply.github.com>
## Summary It seems like Cross doesn't yet support 1.85.
https://lucumr.pocoo.org/2024/8/21/harvest-season/ > Domination is a goal because it means that most investment will go > into one stack. I can only re-iterate my wish and desire that Rye (and > with it a lot of other tools in the space) should cease to exist once > the dominating tool has been established. For me uv is poised to be > that tool. It's not quite there today yet for all cases, but it will > be in no time, and now is the moment to step up as a community and > start to start to rally around it. That doesn't mean that this tool > will be the tool forever. Things come and go and maybe there is a > future for some other tool. > > But today I'm looking forward to the moment when there will be a final > release of Rye that is no remaining functionality other than to just > largely alias to uv, that retires Rye specific functionality and > migrates you over to uv. This does not do a final release - adding a compatibility layer for uv and an automatic migration is likely to be buggy and incomplete, and users are better served by changing the command they type to `uv`. Instead, it adds a migration guide based on the discussion thread (astral-sh#1342), documenting things that are not immediately obvious to a user swapping out `rye` for `uv`.
Add initial devcontainer configuration - Add devcontainer.json with Ubuntu base image - Include Node.js LTS, Git, Docker-in-Docker, and Zsh with Oh My Zsh - Configure VS Code extensions: ESLint, Prettier, GitLens, Docker, Copilot - Set up automatic port forwarding for ports 3000 and 8080 - Enable format on save with Prettier - Add Dockerfile for custom system packages - Include README.md with setup and usage instructions
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
20 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Add initial devcontainer configuration