# 1.38.0 pre-release is ready for testing

**URL:** <https://internals.rust-lang.org/t/1-38-0-pre-release-is-ready-for-testing/10992>\
**Category:** announcements\
**Created:** [September 24, 2019, 11:44am UTC](https://internals.rust-lang.org/t/1-38-0-pre-release-is-ready-for-testing/10992 "2019-09-24T11:44:14Z")\
**Posts on this page:** 8\
**Page:** 1

<div class="post-metadata">

**Author:** ![Mark\_Simulacrum](https://sea2.discourse-cdn.com/flex002/user_avatar/internals.rust-lang.org/mark_simulacrum/32/2853_2.png) [@Mark\_Simulacrum](https://internals.rust-lang.org/u/Mark_Simulacrum)\
**Post date:** [September 24, 2019, 11:44am UTC](https://internals.rust-lang.org/t/1-38-0-pre-release-is-ready-for-testing/10992/1 "2019-09-24T11:44:14Z")

</div>

The 1.38.0 pre-release is ready for testing. Rust 1.38.0 is scheduled to be released on Thursday September 26th. Release notes can be found here: [https://github.com/rust-lang/rust/blob/master/RELEASES.md](https://github.com/rust-lang/rust/blob/stable/RELEASES.md#version-1380-2019-09-26).

You can try it out locally with:

```bash
RUSTUP_DIST_SERVER=https://dev-static.rust-lang.org rustup update stable

```

The index is at [https://dev-static.rust-lang.org/dist/2019-09-24/index.html](https://dev-static.rust-lang.org/dist/2019-09-24/index.html).

---

<div class="post-metadata">

**Author:** ![djc](https://sea2.discourse-cdn.com/flex002/user_avatar/internals.rust-lang.org/djc/32/1592_2.png) [@djc](https://internals.rust-lang.org/u/djc)\
**Post date:** [September 24, 2019, 1:54pm UTC](https://internals.rust-lang.org/t/1-38-0-pre-release-is-ready-for-testing/10992/2 "2019-09-24T13:54:14Z")

</div>

Under Compatibility Notes, the release notes mention:

> Unfortunately the [`x86_64-unknown-uefi` platform can not be built](https://github.com/rust-lang/rust/issues/62785/) with rustc 1.39.0.

Should that be 1.38.0?

---

<div class="post-metadata">

**Author:** ![Tom-Phinney](https://sea2.discourse-cdn.com/flex002/user_avatar/internals.rust-lang.org/tom-phinney/32/3299_2.png) [@Tom-Phinney](https://internals.rust-lang.org/u/Tom-Phinney)\
**Post date:** [September 24, 2019, 2:06pm UTC](https://internals.rust-lang.org/t/1-38-0-pre-release-is-ready-for-testing/10992/3 "2019-09-24T14:06:31Z")

</div>

The link for **Stabilized APIs** `any::type_name` is incorrect.

---

<div class="post-metadata">

**Author:** ![Nemo157](https://sea2.discourse-cdn.com/flex002/user_avatar/internals.rust-lang.org/nemo157/32/11585_2.png) [@Nemo157](https://internals.rust-lang.org/u/Nemo157)\
**Post date:** [September 24, 2019, 2:11pm UTC](https://internals.rust-lang.org/t/1-38-0-pre-release-is-ready-for-testing/10992/4 "2019-09-24T14:11:39Z")

</div>

`std::any::type_name` was created and stabilized within the same version, so the link won't work until 1.38.0 goes live. You can see that redirecting to the beta docs the equivalent link works: [https://doc.rust-lang.org/beta/std/any/fn.type\_name.html](https://doc.rust-lang.org/beta/std/any/fn.type_name.html).

---

<div class="post-metadata">

**Author:** ![Aloso](https://sea2.discourse-cdn.com/flex002/user_avatar/internals.rust-lang.org/aloso/32/5039_2.png) [@Aloso](https://internals.rust-lang.org/u/Aloso)\
**Post date:** [September 24, 2019, 4:18pm UTC](https://internals.rust-lang.org/t/1-38-0-pre-release-is-ready-for-testing/10992/5 "2019-09-24T16:18:50Z")

</div>

I believe this is usually also posted on Reddit. cc @pietroalbini

---

<div class="post-metadata">

**Author:** ![pietroalbini](https://sea2.discourse-cdn.com/flex002/user_avatar/internals.rust-lang.org/pietroalbini/32/10694_2.png) [@pietroalbini](https://internals.rust-lang.org/u/pietroalbini)\
**Post date:** [September 24, 2019, 4:38pm UTC](https://internals.rust-lang.org/t/1-38-0-pre-release-is-ready-for-testing/10992/6 "2019-09-24T16:38:27Z")

</div>

Uh, yeah, got busy with other stuff today and I forgot 😅. [Posted it](https://www.reddit.com/r/rust/comments/d8pn0t/rust_1380_prerelease_testing/).

Also [opened a PR to fix the wrong rustc version](https://github.com/rust-lang/rust/pull/64742) in the compatibility section.

---

<div class="post-metadata">

**Author:** ![semarie](https://sea2.discourse-cdn.com/flex002/user_avatar/internals.rust-lang.org/semarie/32/2012_2.png) [@semarie](https://internals.rust-lang.org/u/semarie)\
**Post date:** [September 25, 2019, 6:46am UTC](https://internals.rust-lang.org/t/1-38-0-pre-release-is-ready-for-testing/10992/7 "2019-09-25T06:46:24Z")

</div>

I would like signal to downstream that with this version, cargo uses libgit2-sys crate which broke the compatibility with libgit2-0.28 branch and depend on unreleased libgit2 version.

- [rust-lang/git2-rs/issues/458](https://github.com/rust-lang/git2-rs/issues/458)
- [rust-lang/rust/issues/63476](https://github.com/rust-lang/rust/issues/63476)

Running cargo break at runtime with such error:

```rust
$ cargo install test
    Updating crates.io index
error: failed to fetch `https://github.com/rust-lang/crates.io-index`

Caused by:
  invalid version 3 on git_proxy_options; class=Invalid (3)

```

FreeBSD already have a local patch to restore the compatibility at [lang/rust-nightly/files/patch-vendor\_libgit2-sys\_lib.rs](https://svnweb.freebsd.org/ports/head/lang/rust-nightly/files/patch-vendor_libgit2-sys_lib.rs) , and I intent to use it too for OpenBSD too.

---

<div class="post-metadata">

**Author:** ![Mark\_Simulacrum](https://sea2.discourse-cdn.com/flex002/user_avatar/internals.rust-lang.org/mark_simulacrum/32/2853_2.png) [@Mark\_Simulacrum](https://internals.rust-lang.org/u/Mark_Simulacrum)\
**Post date:** [December 24, 2019, 6:46am UTC](https://internals.rust-lang.org/t/1-38-0-pre-release-is-ready-for-testing/10992/8 "2019-12-24T06:46:28Z")

</div>

Closed on December 24, 2019, 6:46am UTC

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.
