-
Notifications
You must be signed in to change notification settings - Fork 0
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
GDP-2719 Update to 0.13.1 #53
Conversation
Co-authored-by: Peng Gao <[email protected]>
…-project#9819) Co-authored-by: Peng Gao <[email protected]>
…site (datahub-project#9603) Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
Co-authored-by: gaurav2733 <[email protected]>
…charts, data jobs, data flows (datahub-project#9710) Co-authored-by: John Joyce <[email protected]> Co-authored-by: John Joyce <[email protected]> Co-authored-by: John Joyce <[email protected]>
Co-authored-by: Tamas Nemeth <[email protected]>
⚠ SAST ReportWarnings (2)Fingerprint: ee3fb18b6ffc7208620dd66d5eacf3ebeb266769ce02af99a38e01b0101bf046
Untrusted user input in Fingerprint: 04233b2ef9aaaca982f57651e47dfa40f8fe1d6a044e8691a5f4a09274e6285f
Untrusted user input in For more details, please check code annotations on the changed files. To create an exception, follow this guide. For help, join #coberos-help. |
Changed strategy and went for merging master (0.13.1 release commit) instead of rebasing. We have a lot of FC-specific tweaks now in the codebase that I can't see us moving off of the fork anytime soon. My thinking is that it's more important to be able to upgrade to new datahub releases more frequently, and re-fixing the same conflicts over and over gets tedious.
If we're happy with this, I'll update docs in fc-datahub accordingly