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

Release 2.14.0 #1998

Merged
merged 2 commits into from
Jan 31, 2023
Merged

Release 2.14.0 #1998

merged 2 commits into from
Jan 31, 2023

Conversation

cdce8p
Copy link
Member

@cdce8p cdce8p commented Jan 31, 2023

Added an additional changelog entry for #1978

@cdce8p cdce8p added the Maintenance Discussion or action around maintaining astroid or the dev workflow label Jan 31, 2023
@cdce8p cdce8p added this to the 2.14.0 milestone Jan 31, 2023
@codecov
Copy link

codecov bot commented Jan 31, 2023

Codecov Report

Merging #1998 (84617a2) into main (01b09cb) will not change coverage.
The diff coverage is 100.00%.

Additional details and impacted files

Impacted file tree graph

@@           Coverage Diff           @@
##             main    #1998   +/-   ##
=======================================
  Coverage   92.77%   92.77%           
=======================================
  Files          94       94           
  Lines       10931    10931           
=======================================
  Hits        10141    10141           
  Misses        790      790           
Flag Coverage Δ
linux 92.53% <100.00%> (ø)
pypy 88.50% <100.00%> (ø)
windows 92.37% <100.00%> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files Coverage Δ
astroid/__pkginfo__.py 100.00% <100.00%> (ø)

@cdce8p cdce8p merged commit b644c1e into pylint-dev:main Jan 31, 2023
@cdce8p cdce8p deleted the release-2.14.0 branch January 31, 2023 14:39
@cdce8p
Copy link
Member Author

cdce8p commented Jan 31, 2023

@Pierre-Sassoulas The release are all done, label and maintenance branch created. Will update pylint later.

One other thing, I would suggest we remove the old backport maintenance/2.xx.x labels. In the end, they are just confusing and don't add much value. I've added a new label https://github.com/PyCQA/astroid/labels/backported which we can add to PRs once the backport is done. But aside from that, if the original PR does have a milestone attached, I think the backport label isn't necessary anymore.

@Pierre-Sassoulas
Copy link
Member

Make sense especially as we set the milestone too.

@Pierre-Sassoulas
Copy link
Member

Thank you for releasing 😄 !!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Maintenance Discussion or action around maintaining astroid or the dev workflow
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants