teleport 15.0.2

[BrewTestBot]

Created by brew bump

---

Created with brew bump-formula-pr.

release notes

## Description

Fixed a potential panic in the tsh status command. #38305
Fixed SSO user locking in the setup access step of the RDS auto discover flow in the web UI. #38283
Optionally permit the auth server to terminate client connections from unsupported versions. #38182
Fixed Assist obstructing the user dropdown menu when in docked mode. #38156
Improved the stability of Teleport during graceful upgrades. #38145
Added the ability to view and manage Machine ID bots from the UI. #38122
Fixed a bug that prevented desktop clipboard sharing from working when large amounts of text are placed on the clipboard. #38120
Added option to validate hardware key serial numbers with hardware key support. #38068
Removed access tokens from URL parameters, preventing them from being leaked to intermediary systems that may log them in plaintext. #38032
Forced agents to terminate Auth connections if joining fails. #38005
Added a tsh sessions ls command to list active sessions. #37969
Improved error handling when idle desktop connections are terminated. #37955
Updated Go to 1.21.7. #37846
Discover flow now starts two instances of DatabaseServices when setting up access to Amazon RDS. #37805

Download
Download the current and previous releases of Teleport at https://goteleport.com/download.

[timsutton]

#161522 (comment)

[SMillerDev]

Anyone have an idea how we would do that?

[timsutton]

Anyone have an idea how we would do that?

I'm able to get their CI's build process on macos to work if I have a Rustup-based toolchain, it has conveniences to download and install the wasm32-unknown-unknown target as needed.

They also currently target Rust 1.71.1. Do you think it's preferable to:

1. Honor the toolchain used in their build by depending on rustup-init for :build and doing something similar to signal-cli here? Or
2. If it builds with current Rust 1.76.0, then try and get the standard rust formula to work with the build?

It seems like both are doable, but I'm wondering whether there is a strong preference to stick with the same Rust toolchain version as the upstream project? If there is then I would try the first option.

[SMillerDev]

Honor the toolchain used in their build by depending on rustup-init for :build and doing something similar to signal-cli here? Or

That's not an option. It would essentially break https://docs.brew.sh/Acceptable-Formulae#we-dont-like-install-scripts-that-download-unversioned-things and https://docs.brew.sh/Acceptable-Formulae#stuff-that-requires-vendored-versions-of-homebrew-formulae.

If it builds with current Rust 1.76.0, then try and get the standard rust formula to work with the build?

This is the only way really.

[github-actions]

This pull request has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. To keep this pull request open, add a help wanted or in progress label.