-
Notifications
You must be signed in to change notification settings - Fork 298
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
v1.8.9 #4782
Conversation
This file contains 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
# What this PR does Restructures OnCall documentation 'Configure' section ## Which issue(s) this PR closes Closes issue #4592
# What this PR does Enables free-text search on the alert group page by default (sets the `FEATURE_ALERT_GROUP_SEARCH_ENABLED` feature flag to `True` by default). ## Which issue(s) this PR closes Related to #4263 and grafana/oncall-private#2679 <!-- *Note*: If you want the issue to be auto-closed once the PR is merged, change "Related to" to "Closes" in the line above. If you have more than one GitHub issue that this PR closes, be sure to preface each issue link with a [closing keyword](https://docs.github.com/en/get-started/writing-on-github/working-with-advanced-formatting/using-keywords-in-issues-and-pull-requests#linking-a-pull-request-to-an-issue). This ensures that the issue(s) are auto-closed once the PR has been merged. --> ## Checklist - [x] Unit, integration, and e2e (if applicable) tests updated - [x] Documentation added (or `pr:no public docs` PR label added if not required) - [x] Added the relevant release notes label (see labels prefixed w/ `release:`). These labels dictate how your PR will show up in the autogenerated release notes.
# What this PR does Before: <img width="267" alt="Screenshot 2024-07-25 at 17 35 28" src="https://github.com/user-attachments/assets/b0cdcb9d-f658-41cf-9fbb-b61819364dec"> After: <img width="267" alt="Screenshot 2024-07-25 at 18 11 53" src="https://github.com/user-attachments/assets/f88c574d-ec9b-4e16-a413-62aa00de6c9a"> ## Checklist - [x] Unit, integration, and e2e (if applicable) tests updated - [x] Documentation added (or `pr:no public docs` PR label added if not required) - [x] Added the relevant release notes label (see labels prefixed w/ `release:`). These labels dictate how your PR will show up in the autogenerated release notes.
Related to grafana/irm#25 ## Checklist - [ ] Unit, integration, and e2e (if applicable) tests updated - [x] Documentation added (or `pr:no public docs` PR label added if not required) - [x] Added the relevant release notes label (see labels prefixed w/ `release:`). These labels dictate how your PR will show up in the autogenerated release notes.
…to the AG table sizing (#4744) # What this PR does - Checks for AG timeout before setting a new one - Changed table column sizing on a few columns within AG
# What this PR does - Migrate react-router from v5 to v6 Closes #4031
# What this PR does Fix unit tests from irm run Fix types generator after Node.js upgrade ## Which issue(s) this PR closes Related to grafana/irm#25 <!-- *Note*: If you want the issue to be auto-closed once the PR is merged, change "Related to" to "Closes" in the line above. If you have more than one GitHub issue that this PR closes, be sure to preface each issue link with a [closing keyword](https://docs.github.com/en/get-started/writing-on-github/working-with-advanced-formatting/using-keywords-in-issues-and-pull-requests#linking-a-pull-request-to-an-issue). This ensures that the issue(s) are auto-closed once the PR has been merged. --> ## Checklist - [ ] Unit, integration, and e2e (if applicable) tests updated - [x] Documentation added (or `pr:no public docs` PR label added if not required) - [x] Added the relevant release notes label (see labels prefixed w/ `release:`). These labels dictate how your PR will show up in the autogenerated release notes.
# What this PR does ## Which issue(s) this PR closes Closes [issue link here] <!-- *Note*: if you have more than one GitHub issue that this PR closes, be sure to preface each issue link with a [closing keyword](https://docs.github.com/en/get-started/writing-on-github/working-with-advanced-formatting/using-keywords-in-issues-and-pull-requests#linking-a-pull-request-to-an-issue). This ensures that the issue(s) are auto-closed once the PR has been merged. --> ## Checklist - [ ] Unit, integration, and e2e (if applicable) tests updated - [ ] Documentation added (or `pr:no public docs` PR label added if not required) - [ ] Added the relevant release notes label (see labels prefixed w/ `release:`). These labels dictate how your PR will show up in the autogenerated release notes.
You can use `ref` URIs in admonitions (or any shortcodes) because they are inline and not subject to the issues noted in the [`admonition` shortcode](https://grafana.com/docs/writers-toolkit/write/shortcodes/#code-shortcode:~:text=to%20core%20understanding.-,WARNING,For%20more%20information%2C%20refer%20to%20Markdown%20Reference%20Links%20in%20Shortcodes.,-Examples). The `ref` URIs perform the same pattern matching as `docs/reference` but don't require the use of reference-style links and the destinations are ordinary (full) URLs that can include version substitution. Unlike `docs/reference`, the implementation doesn't use `relref` so you don't have to be careful with omitting trailing slashes and the links will follow redirects. Documentation: https://grafana.com/docs/writers-toolkit/write/links/#link-from-source-content-thats-used-in-multiple-projects To check the links, refer to the deploy preview in grafana/website#19630. Signed-off-by: Jack Baldry <[email protected]> --------- Signed-off-by: Jack Baldry <[email protected]>
# What this PR does Fixes a bug when RBAC permissions are getting erased when Grafana's API returns a 5xx server error on organization sync. ## Which issue(s) this PR closes Closes grafana/oncall-private#2834 ## Checklist - [x] Unit, integration, and e2e (if applicable) tests updated - [x] Documentation added (or `pr:no public docs` PR label added if not required) - [x] Added the relevant release notes label (see labels prefixed w/ `release:`). These labels dictate how your PR will show up in the autogenerated release notes.
# What this PR does allow plugin id customization (for IRM monorepo) ## Which issue(s) this PR closes Related to grafana/irm#9 <!-- *Note*: If you want the issue to be auto-closed once the PR is merged, change "Related to" to "Closes" in the line above. If you have more than one GitHub issue that this PR closes, be sure to preface each issue link with a [closing keyword](https://docs.github.com/en/get-started/writing-on-github/working-with-advanced-formatting/using-keywords-in-issues-and-pull-requests#linking-a-pull-request-to-an-issue). This ensures that the issue(s) are auto-closed once the PR has been merged. --> ## Checklist - [ ] Unit, integration, and e2e (if applicable) tests updated - [x] Documentation added (or `pr:no public docs` PR label added if not required) - [x] Added the relevant release notes label (see labels prefixed w/ `release:`). These labels dictate how your PR will show up in the autogenerated release notes.
# What this PR does Covers the case on getting cached on-call users when cached schedule was deleted ## Which issue(s) this PR closes Related to grafana/oncall-private#2836 ## Checklist - [x] Unit, integration, and e2e (if applicable) tests updated - [x] Documentation added (or `pr:no public docs` PR label added if not required) - [x] Added the relevant release notes label (see labels prefixed w/ `release:`). These labels dictate how your PR will show up in the autogenerated release notes.
Related to grafana/oncall-private#2806 (comment). Prepare engine for the backend plugin enablement/migration: - Refactor sync code - Improve plugin user authentication to set up user on-the-fly (when missing) - Implement v2 endpoints for install, sync and status (to be used via the backend plugin) (most of the changes come from #4657; backport all engine changes that keep backwards compatibility)
# What this PR does Fixes MS Teams product label as reported in Slack - https://raintank-corp.slack.com/archives/C0229FD3CE9/p1722442127606989
# What this PR does Sets feature flag to `True` to enable SMS notification bundling by default ## Which issue(s) this PR closes Related to grafana/oncall-private#2554 Should be merged with #4757 ## Checklist - [ ] Unit, integration, and e2e (if applicable) tests updated - [x] Documentation added (or `pr:no public docs` PR label added if not required) - [x] Added the relevant release notes label (see labels prefixed w/ `release:`). These labels dictate how your PR will show up in the autogenerated release notes.
## What this PR does Updates the public documentation to explain SMS notification bundling behavior
# What this PR does Email tasks are failing and retrying when they use the fallback default notification policy as it does not get saved in the DB. This PR uses the same way as UserNotificationPolicyLogRecord to set that field to null to avoid `ValueError("save() prohibited to prevent data loss due to unsaved related object 'notification_policy'.").` when that is the case. ## Which issue(s) this PR closes Related to [issue link here] <!-- *Note*: If you want the issue to be auto-closed once the PR is merged, change "Related to" to "Closes" in the line above. If you have more than one GitHub issue that this PR closes, be sure to preface each issue link with a [closing keyword](https://docs.github.com/en/get-started/writing-on-github/working-with-advanced-formatting/using-keywords-in-issues-and-pull-requests#linking-a-pull-request-to-an-issue). This ensures that the issue(s) are auto-closed once the PR has been merged. --> ## Checklist - [x] Unit, integration, and e2e (if applicable) tests updated - [x] Documentation added (or `pr:no public docs` PR label added if not required) - [x] Added the relevant release notes label (see labels prefixed w/ `release:`). These labels dictate how your PR will show up in the autogenerated release notes.
This is required to support the install v2 endpoint (to be used by backend plugin) which could be pushing null permissions, teams, or team memberships.
Co-authored-by: grafanabot <[email protected]> Co-authored-by: Jack Baldry <[email protected]>
# What this PR does Don't send request for permalink if slack token has been revoked ## Which issue(s) this PR closes Related to grafana/oncall-private#2843 ## Checklist - [x] Unit, integration, and e2e (if applicable) tests updated - [x] Documentation added (or `pr:no public docs` PR label added if not required) - [x] Added the relevant release notes label (see labels prefixed w/ `release:`). These labels dictate how your PR will show up in the autogenerated release notes.
joeyorlando
had a problem deploying
to
github-pages
August 7, 2024 06:03 — with
GitHub Actions
Failure
joeyorlando
had a problem deploying
to
github-pages
August 7, 2024 06:03 — with
GitHub Actions
Failure
joeyorlando
had a problem deploying
to
github-pages
August 7, 2024 11:21 — with
GitHub Actions
Failure
joeyorlando
had a problem deploying
to
github-pages
August 7, 2024 11:21 — with
GitHub Actions
Failure
joeyorlando
had a problem deploying
to
github-pages
August 7, 2024 12:42 — with
GitHub Actions
Failure
joeyorlando
temporarily deployed
to
github-pages
August 7, 2024 12:42 — with
GitHub Actions
Inactive
joeyorlando
had a problem deploying
to
github-pages
August 7, 2024 13:51 — with
GitHub Actions
Error
joeyorlando
had a problem deploying
to
github-pages
August 7, 2024 13:51 — with
GitHub Actions
Error
joeyorlando
had a problem deploying
to
github-pages
August 7, 2024 14:21 — with
GitHub Actions
Error
joeyorlando
had a problem deploying
to
github-pages
August 7, 2024 14:21 — with
GitHub Actions
Error
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
No description provided.