-
Notifications
You must be signed in to change notification settings - Fork 890
chore: cherry pick PRs for 2.17 #15339
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
Merged
Merged
Conversation
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
Collaborator
stirby
commented
Nov 1, 2024
- https://github.com/coder/coder/pull/15305
- https://github.com/coder/coder/pull/15307
- https://github.com/coder/coder/pull/15270
- https://github.com/coder/coder/pull/15261
- feat: add prometheus metric for tracking user statuses #15281
- feat: add audit logs for dormancy events #15298
- Release Docs:
- docs: add new best practice doc to speed up templates and workspaces #15296
- chore(docs): add documentation on custom roles #15280
- chore(docs): include custom roles examples and mention of password reset #15294
- chore(docs): add info on new build timings in docs #15310
…15307) Related to [https://github.com/coder/coder/issues/15297](https://github.com/coder/coder/issues/15297#issuecomment-2450052538) - Clearly display this as Daily Active Users - Remove the user limit bar at the top for licensed deployments - Explain in the tooltip that this is for measuring user activity and has no connection to license consumption (cherry picked from commit 4849b4d)
…orgs (#15261) The failure condition being fixed is `w1` and `w2` could belong to different users, organizations, and templates and still cause a serializable failure if run concurrently. This is because the old query did a `seq scan` on the `workspace_builds` table. Since that is the table being updated, we really want to prevent that. So before this would fail for any 2 workspaces. Now it only fails if `w1` and `w2` are owned by the same user and organization. (cherry picked from commit 854044e)
(cherry picked from commit 3de98c2)
(cherry picked from commit 088f219)
…15296) closes #14858 - [x] TODO: update `build-timeline.png` - [x] TODO: `Best practices` doesn't show up in the sidebar until you're actually in the doc 🤔 [preview](https://coder.com/docs/@bp-speed-up-templates/tutorials/best-practices/speed-up-templates) --------- Co-authored-by: EdwardAngert <17991901+EdwardAngert@users.noreply.github.com> Co-authored-by: Muhammad Atif Ali <atif@coder.com> Co-authored-by: Ben Potter <ben@coder.com> (cherry picked from commit 18ef954)
These docs were overwritten in the restructure merge. (cherry picked from commit 2573838)
Adds information on workspace build timings in workspace lifecycle and template troubleshooting docs. (cherry picked from commit 399c830)
sreya
approved these changes
Nov 1, 2024
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.