Skip to content

Conversation

@yan-3005
Copy link
Contributor

Describe your changes:

Fixes

I worked on ... because ...

Type of change:

  • Bug fix
  • Improvement
  • New feature
  • Breaking change (fix or feature that would cause existing functionality to not work as expected)
  • Documentation

Checklist:

  • I have read the CONTRIBUTING document.
  • My PR title is Fixes <issue-number>: <short explanation>
  • I have commented on my code, particularly in hard-to-understand areas.
  • For JSON Schema changes: I updated the migration scripts or explained why it is not needed.

@github-actions
Copy link
Contributor

TypeScript types have been updated based on the JSON schema changes in the PR

@github-actions github-actions bot requested a review from a team as a code owner November 24, 2025 11:45
@github-actions
Copy link
Contributor

Jest test Coverage

UI tests summary

Lines Statements Branches Functions
Coverage: 63%
63.48% (49653/78213) 40.54% (23693/58448) 44.37% (7532/16974)

@harshach
Copy link
Collaborator

@yan-3005 is this a blocker for 1.11.0?

@sonarqubecloud
Copy link

@yan-3005
Copy link
Contributor Author

yan-3005 commented Dec 1, 2025

@yan-3005 is this a blocker for 1.11.0?

@harshach No, this is not a blocker for 1.11.0

@yan-3005 yan-3005 changed the title Add reviewers to Data Assets [WIP] Add reviewers to Data Assets Dec 2, 2025
@yan-3005 yan-3005 added this to Roadmap Dec 2, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

backend safe to test Add this label to run secure Github workflows on PRs

Projects

Status: No status

Development

Successfully merging this pull request may close these issues.

3 participants