Skip to content

reset drainageInfo#7276

Merged
carlydf merged 2 commits intoversioning-3.1-mergefrom
ss/update-local-state-after-drainage
Feb 6, 2025
Merged

reset drainageInfo#7276
carlydf merged 2 commits intoversioning-3.1-mergefrom
ss/update-local-state-after-drainage

Conversation

@Shivs11
Copy link
Copy Markdown
Member

@Shivs11 Shivs11 commented Feb 6, 2025

What changed?

  • reset drainageInfo to nil after workflow starts accepting new workflows again

Why?

How did you test it?

  • existing suite

Potential risks

Documentation

Is hotfix candidate?

@Shivs11 Shivs11 requested a review from a team as a code owner February 6, 2025 18:23
@carlydf carlydf merged commit 217337a into versioning-3.1-merge Feb 6, 2025
@carlydf carlydf deleted the ss/update-local-state-after-drainage branch February 6, 2025 19:56
ShahabT pushed a commit that referenced this pull request Feb 6, 2025
## What changed?
<!-- Describe what has changed in this PR -->
- reset drainageInfo to nil after workflow starts accepting new
workflows again

## Why?
<!-- Tell your future self why have you made these changes -->

## How did you test it?
<!-- How have you verified this change? Tested locally? Added a unit
test? Checked in staging env? -->
- existing suite

## Potential risks
<!-- Assuming the worst case, what can be broken when deploying this
change to production? -->

## Documentation
<!-- Have you made sure this change doesn't falsify anything currently
stated in `docs/`? If significant
new behavior is added, have you described that in `docs/`? -->

## Is hotfix candidate?
<!-- Is this PR a hotfix candidate or does it require a notification to
be sent to the broader community? (Yes/No) -->

---------

Co-authored-by: Carly de Frondeville <[email protected]>
ShahabT pushed a commit that referenced this pull request Feb 6, 2025
## What changed?
<!-- Describe what has changed in this PR -->
- reset drainageInfo to nil after workflow starts accepting new
workflows again

## Why?
<!-- Tell your future self why have you made these changes -->

## How did you test it?
<!-- How have you verified this change? Tested locally? Added a unit
test? Checked in staging env? -->
- existing suite

## Potential risks
<!-- Assuming the worst case, what can be broken when deploying this
change to production? -->

## Documentation
<!-- Have you made sure this change doesn't falsify anything currently
stated in `docs/`? If significant
new behavior is added, have you described that in `docs/`? -->

## Is hotfix candidate?
<!-- Is this PR a hotfix candidate or does it require a notification to
be sent to the broader community? (Yes/No) -->

---------

Co-authored-by: Carly de Frondeville <[email protected]>
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.

2 participants