Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Release 17.2.1 #51385

Merged
merged 2 commits into from
Jan 23, 2025
Merged

Release 17.2.1 #51385

merged 2 commits into from
Jan 23, 2025

Conversation

camscale
Copy link
Contributor

@camscale camscale commented Jan 22, 2025

17.2.1 (01/22/2025)

Security Fixes

  • Improve Azure join validation by verifying subscription ID. #51328

Other Improvements and Fixes

  • Added support for multiple active CAs in tctl auth export. #51375
  • Teleport Connect now shows a resource name in the status bar. #51374
  • Role presets now include default values for github_permissions and the git_server resource kind. github_permissions now supports traits. #51369
  • Fix backwards compatibility error where users were unable to login with Teleport Connect if Connect version is below v17.2.0 with Teleport cluster version v17.2.0. #51368
  • Added wildcard-workload-identity-issuer preset role to improve Day 0 experience with configuring Teleport Workload Identity. #51341
  • Added more granular audit logging surrounding SSH port forwarding. #51325
  • FIxes a bug causing the terraform-provider preset role to not automatically allow newly supported resources. #51320
  • GitHub server resource now shows in Web UI. #51303

@camscale camscale added the no-changelog Indicates that a PR does not require a changelog entry label Jan 22, 2025
@github-actions github-actions bot requested review from avatus and creack January 22, 2025 23:30
@@ -1,5 +1,17 @@
# Changelog

## 17.2.1 (01/22/2025)
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Let's call out #51085 as a security fix.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Done. Is that fine as a separate section like that, just listing the changelog entry, or is there some more wording to add around this?

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yeah this is fine. And let's mark the Github release a security release.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Will do. I've already updated the release checklist for the step where the release is created to add a reminder and how-to for security releases.

@@ -1,5 +1,17 @@
# Changelog

## 17.2.1 (01/22/2025)
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yeah this is fine. And let's mark the Github release a security release.

@camscale camscale added this pull request to the merge queue Jan 23, 2025
Merged via the queue into branch/v17 with commit 1d267b0 Jan 23, 2025
43 checks passed
@camscale camscale deleted the release/17.2.1 branch January 23, 2025 00:22
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
backport helm no-changelog Indicates that a PR does not require a changelog entry size/sm
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants