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.

Sign up for GitHub

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

Jump to bottom

grafana 10.1.0 #140321

Merged
merged 2 commits into from
Aug 24, 2023
Merged

grafana 10.1.0 #140321

merged 2 commits into from
Aug 24, 2023

Conversation

chenrui333
Copy link
Member

Created by brew bump

Created with brew bump-formula-pr.

release notes 
[Download page](https://grafana.com/grafana/download/10.1.0)
[What's new highlights](https://grafana.com/docs/grafana/latest/whatsnew/)

Features and enhancements



Bug fixes



Breaking changes


This change impacts all instances that use external authentication providers to manage users and organization role assignments.


From Grafana 10.1, it will no longer be possible to manually update organization roles (Viewer, Editor and Admin) that are managed by an external auth provider. We are making this change to clearly separate between roles managed by an external auth provider and manually assigned roles, which increases security and clarity around role management.


If you prefer to manually set user organization roles, use skip_org_role_sync option in the Grafana configuration file of your OAuth provider.


Refer to the release notes of Grafana 9.5 for context on the previous work done to build up to this change. Issue #72204


This change impacts GitHub OAuth, Gitlab OAuth, Okta OAuth and Generic OAuth


Currently if no organization role mapping is found for a user when connecting via OAuth, Grafana doesn’t update the user’s organization role.


With Grafana 10.1, on every login, if the role_attribute_path property does not return a role, then the user is assigned the role specified by the auto_assign_org_role option.


To avoid overriding manually set roles, enable the skip_org_role_sync option in the Grafana configuration for your OAuth provider. Issue #70766


InfluxDB backend parser returns incompatible data with frontend. The data was being parsed by frontend and we moving towards migrating InfluxDB fully backend. One caveat is Frontend is generating data frames with fields Time and Value. The backend parser, however, generates time and value. This is causing issues and inconsistencies for the features (i.e. transformations) relying on those. In order to have a unique approach we choose to support what most of the users already have. Existing Transformations that depend on time fields have to be updated to use Time fields. Issue #69865


For accessibility reasons tooltip or aria-label are now required properties for IconButton. In order to continue to use IconButton, you must ensure all IconButton components have a corresponding tooltip or aria-label text. The tooltip text will also be used as the aria-label if you didn't set one separately. In case you add an aria-label the IconButton will not show a tooltip. Issue #69699


The implementation for template macro ${__series.name} was not always correct, resulting in an interpolation that was very different from the series name displayed in the visualization. We have now fixed this issue so that it does show the same name. Depending on how ${__series.name} is used this could result in a minor breaking change. Issue #69621


The data source template variable type has changed the way it represents its options. The text field still represents the data source name, but the value has been changed to the uid of the data source. This allows dashboards to declare the currently selected option by uid, however it changes how a datasource template variable value will be rendered by default. If the name of the data source is expected, the variable syntax will have to be changed to specify the text format.


For example, given a data source variable (datasourceVariable), the following string:


${datasourceVariable}<br/>
Name: ${datasourceVariable:text}<br/>
UID: ${datasourceVariable:raw}



was previously interpolated as:


grafanacloud-k8smonitoring-prom
Name: grafanacloud-k8smonitoring-prom
UID: grafanacloud-k8smonitoring-prom



After these changes, it's interpolated as:


d7bbe725-9e48-4af8-a0cb-6cb255d873a3
Name: grafanacloud-k8smonitoring-prom
UID: d7bbe725-9e48-4af8-a0cb-6cb255d873a3



Any dashboards that are relying on the data source name being returned by ${datasourceVariable} will have to update all their usages to ${datasourceVariable:text} in order to get the previous behavior.


Affected use cases:


    

  • Using ${datasourceVariable} to display the data source name in text panel or in the panel title.
    • 

  • Using ${datasourceVariable} to use the data source name as part of the query content.
    • 



Unaffected use cases:


    

  • Using the ${datasourceVariable} to choose which data source to use for a query (through its data source picker) will not be affected since it can use both the name and the uid Issue #69259
    • 



We are changing the logic that creates uid in LogRowModel. Previously, for uid we used id field from log's data frame. Unfortunately, when users run multiple queries that returned duplicate logs data, uid was not unique which was causing bugs. To make uid unique across multiple queries that return duplicate logs data, we are now prepending uid with refId of query that produced the log line. We recommend not to rely on LogRowModel uid and instead use dataFrame id field. Issue #68569


The deprecated support for monitoring Grafana frontend using Sentry javascript agent has been removed in this release. If you have frontend logging enabled and are sending telemetry to Sentry by setting sentry_dsn configuration property, this will no longer work. Otherwise, if frontend logging is enabled, it will now automatically use Grafana Faro agent. Issue #67493


Deprecations


The query parameter of Explore's SplitOpen function is deprecated (passed in mapInternalLinkToExplore). Please use the queries parameter instead, which allows passing multiple queries to SplitOpen function. To pass a single query to SplitOpen function, set the queries parameter to an array containing that single query.


Fixes: grafana/grafana#62567 Issue #71484


Starting with 10.0, changing the folder UID is deprecated. It will be removed in a future release. Please avoid using it because it can result in folder losing its permissions. Issue #68543


Plugin development fixes & changes


    

  • GrafanaUI: Define tooltip or aria-label as required for IconButton. #69699, @L-M-K-B
    • 

  • Select: Performance improvements when opening menu and when hovering over options. #69230, @JoaoSilvaGrafana
    • 

  • ConfirmModal: Ignore case for confirmation text. #69000, @ashharrison90
    • 

  • Grafana/ui: Fix margin in RadioButtonGroup option when only icon is present. #68899, @aocenas

@github-actions github-actions bot added go Go use is a significant feature of the PR or issue nodejs Node or npm use is a significant feature of the PR or issue bump-formula-pr PR was created using `brew bump-formula-pr` labels Aug 24, 2023
@github-actions
Copy link
Contributor

🤖 An automated task has requested bottles to be published to this PR.

@github-actions github-actions bot added the CI-published-bottle-commits The commits for the built bottles have been pushed to the PR branch. label Aug 24, 2023
@BrewTestBot BrewTestBot added this pull request to the merge queue Aug 24, 2023
Merged via the queue into Homebrew:master with commit f42f196 Aug 24, 2023
12 checks passed
@chenrui333 chenrui333 deleted the bump-grafana-10.1.0 branch January 22, 2024 16:36
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@ZhongRuoyu ZhongRuoyu ZhongRuoyu approved these changes

@github-actions github-actions[bot] github-actions approved these changes

Assignees
No one assigned
Labels
bump-formula-pr PR was created using `brew bump-formula-pr` CI-published-bottle-commits The commits for the built bottles have been pushed to the PR branch. go Go use is a significant feature of the PR or issue nodejs Node or npm use is a significant feature of the PR or issue
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.

None yet
3 participants
@chenrui333 @ZhongRuoyu @BrewTestBot