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

feat: update dashboard to v0.4.2 #2882

Merged
merged 1 commit into from
Dec 6, 2023
Merged

feat: update dashboard to v0.4.2 #2882

merged 1 commit into from
Dec 6, 2023

Conversation

ZonaHex
Copy link
Contributor

@ZonaHex ZonaHex commented Dec 6, 2023

Update dashboard to v0.4.2

@waynexia waynexia enabled auto-merge December 6, 2023 08:35
Copy link

codecov bot commented Dec 6, 2023

Codecov Report

Merging #2882 (c3f375c) into develop (f9e7762) will decrease coverage by 0.04%.
The diff coverage is n/a.

Additional details and impacted files
@@             Coverage Diff             @@
##           develop    #2882      +/-   ##
===========================================
- Coverage    84.73%   84.69%   -0.04%     
===========================================
  Files          749      749              
  Lines       117900   117900              
===========================================
- Hits         99900    99858      -42     
- Misses       18000    18042      +42     

@waynexia waynexia added this pull request to the merge queue Dec 6, 2023
Merged via the queue into develop with commit a415685 Dec 6, 2023
13 checks passed
@waynexia waynexia deleted the dashboard/v0.4.2 branch December 6, 2023 09:23
@tisonkun
Copy link
Collaborator

tisonkun commented Dec 6, 2023

@ZonaHex how do we manage this version and how does it relate to crate's version? I wonder if this is derived from the crate version and we should do some simultaneous updates.

@waynexia
Copy link
Member

waynexia commented Dec 6, 2023

@ZonaHex how do we manage this version and how does it relate to crate's version? I wonder if this is derived from the crate version and we should do some simultaneous updates.

Dashboard's version is not coupled with database's. Thus the version number in that VERSION file is used as an anchor to map a specific commit in database to corresponding dashboard's version

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants