# Возвращаемся к теме: поддержание актуальной среды разработки

**URL:** <https://meta.discourse.org/t/reprise-maintaining-an-up-to-date-dev-environment/262544>\
**Category:** Development\
**Created:** [21.Апрель.2023 18:06:51 UTC](https://meta.discourse.org/t/reprise-maintaining-an-up-to-date-dev-environment/262544 "2023-04-21T18:06:51Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![sam](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/sam/32/102149_2.png) [@sam](https://meta.discourse.org/u/sam)\
**Post date:** [24.Апрель.2023 00:04:01 UTC](https://meta.discourse.org/t/reprise-maintaining-an-up-to-date-dev-environment/262544/2 "2023-04-24T00:04:01Z")

</div>

> [@Jay Pfaffman](#):
>
> Но теперь Discourse требует версию 3.2.1, а `asdf`, похоже, не знает о ней.

Что-то нужно обновить на вашей стороне, потому что ruby-build точно содержит версию 3.2.1

> <https://github.com/asdf-vm/asdf-ruby/issues/217>
>
> It seems a frequent issue (notably #207, #204 but I think quite a few others) i…s that ruby-build in this plugin can be quite outdated.
> 
> For instance the current release is \`ruby-build 20210611\` but this plugins default to:
> https://github.com/asdf-vm/asdf-ruby/blob/f134c2df390bd8b32c33de5330d61e77b70ae739/lib/utils.sh#L1
> 
> The README also says:
> \> By default asdf-ruby uses the latest release of ruby-build, but you can choose your own branch/tag through the ASDF\_RUBY\_BUILD\_VERSION variable:
> 
> But this is misleading, asdf-ruby will often not use the latest release.
> Unless maybe there is already some mechanism to auto-update ruby-build?
> 
> It would also avoid the need for many PRs like https://github.com/asdf-vm/asdf-ruby/pull/208
> 
> Some ideas:
> \* \`ruby-build\` \`master\` is fairly stable, it should be fine to just use that. This is what is recommended to update ruby-build in rbenv: https://github.com/rbenv/ruby-build#upgrading. Releases are mostly made IIRC for Homebrew.
> \* Find out the latest release using the GitHub API, i.e., the API equivalent of https://github.com/rbenv/ruby-build/releases/latest, and then I would think \`asdf plugin update ruby\` would be enough to get the latest release (it would always download the latest ruby-build release, unless it's already using it).
> \* Get some notification here or automated PR whenever there is a ruby-build release. Seems significantly more complicated but still a possible way.
> 
> Apologies if I missed something, I'm a ruby-build maintainer, and I am currently not using asdf, but would like to help keep the version of ruby-build in asdf-ruby always updated so users can get the latest Rubies/fixes.

---

_[View the full topic](https://meta.discourse.org/t/reprise-maintaining-an-up-to-date-dev-environment/262544)._