Skip to content

Conversation

Shivs11
Copy link
Member

@Shivs11 Shivs11 commented Feb 6, 2025

What changed?

  • ForceCAN bug fix

Why?

How did you test it?

Potential risks

Documentation

Is hotfix candidate?

@Shivs11 Shivs11 requested a review from a team as a code owner February 6, 2025 22:41
Copy link
Contributor

@carlydf carlydf left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

nice! Does the same have to be done in the Worker Deployment workflow?

@Shivs11 Shivs11 merged commit 23fa945 into versioning-3.1-merge Feb 6, 2025
47 checks passed
@Shivs11 Shivs11 deleted the ss/fix-forceCAN branch February 6, 2025 22:49
ShahabT pushed a commit that referenced this pull request Feb 6, 2025
## What changed?
<!-- Describe what has changed in this PR -->
- ForceCAN bug fix

## 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? -->

## 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) -->
ShahabT pushed a commit that referenced this pull request Feb 6, 2025
ShahabT pushed a commit that referenced this pull request Feb 6, 2025
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