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

RavenDB-22360 Bump Npgsql from v5 to v8 Raven.Server #18501

Merged
merged 2 commits into from May 14, 2024

Conversation

arekpalinski
Copy link
Member

@arekpalinski arekpalinski commented May 10, 2024

Issue link

https://issues.hibernatingrhinos.com/issue/RavenDB-22360

Additional description

It's #18497 for 5.4 with fixing the tests (which still need to run on 5.0.18)

Type of change

  • Bug fix
  • Regression bug fix
  • Optimization
  • New feature

How risky is the change?

  • Low
  • Moderate
  • High
  • Not relevant

Backward compatibility

  • Non breaking change
  • Ensured. Please explain how has it been implemented?
  • Breaking change
  • Not relevant

Is it platform specific issue?

  • Yes. Please list the affected platforms.
  • No

Documentation update

  • This change requires a documentation update. Please mark the issue on YouTrack using Documentation Required tag.
  • No documentation update is needed

Testing by Contributor

  • Tests have been added that prove the fix is effective or that the feature works
  • Internal classes added to the test class (e.g. entity or index definition classes) have the lowest possible access modifier (preferable private)
  • It has been verified by manual testing

Testing by RavenDB QA team

  • This change requires a special QA testing due to possible performance or resources usage implications (CPU, memory, IO). Please mark the issue on YouTrack using QA Required tag.
  • No special testing by RavenDB QA team is needed

Is there any existing behavior change of other features due to this change?

  • Yes. Please list the affected features/subsystems and provide appropriate explanation
  • No

UI work

  • It requires further work in the Studio. Please mark the issue on YouTrack using Studio Required tag.
  • No UI work is needed

@arekpalinski arekpalinski force-pushed the RavenDB-22360 branch 3 times, most recently from fa016cf to bac1fad Compare May 13, 2024 11:29
…ests. This way we're still able to run those test (regardless RavenDB-17749 still not being fixed).
@arekpalinski arekpalinski force-pushed the RavenDB-22360 branch 2 times, most recently from 880cc4b to 0c3bc4e Compare May 14, 2024 09:31
@arekpalinski arekpalinski merged commit 0e52520 into ravendb:v5.4 May 14, 2024
15 of 16 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants