Skip to content

Conversation

@pjfanning
Copy link
Member

Description

This PR...

Fixes: #5939

Types of changes

  • Breaking change (fix or feature that would cause existing functionality to change)
  • New feature (non-breaking change which adds functionality)
  • Bug fix (non-breaking change which fixes an issue)
  • Enhancement (improves an existing feature and functionality)
  • Cleanup (Code refactoring and cleanup, that may add test cases)

Feature/Enhancement Scale or Bug Severity

Feature/Enhancement Scale

  • Major
  • Minor

Bug Severity

  • BLOCKER
  • Critical
  • Major
  • Minor
  • Trivial

Screenshots (if appropriate):

How Has This Been Tested?

@yadvr
Copy link
Member

yadvr commented Feb 6, 2022

@pjfanning can you change the base branch to 4.16 and rebase your PR branch to 4.16?

@pjfanning pjfanning changed the base branch from main to 4.16 February 6, 2022 13:50
@pjfanning pjfanning changed the base branch from 4.16 to main February 6, 2022 13:50
@pjfanning
Copy link
Member Author

@rohityadavcloud I'm going to close this - master and 4.16 are so different that a rebase is taking forever - I'll create a new PR from scratch

@pjfanning pjfanning closed this Feb 6, 2022
@pjfanning pjfanning deleted the patch-1 branch February 6, 2022 13:57
@pjfanning
Copy link
Member Author

@rohityadavcloud I created #5942

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.

upgrade commons-compress to 1.21

2 participants