Repository navigation
chore(release): prepare json-logging 1.7.0 - #163
Conversation
Ship 1.7.0 as the final release instead of an rc, since the rc never went to PyPI.
|
ⓘ Qodo reviews are paused because the subscription is no longer active. Ask your workspace admin to reactivate the subscription to resume reviews. Manage billing |
|
No actionable comments were generated in the recent review. Walkthrough
Merge Risk:
|
|
@suppagoddo moved to real version instead of RC. Once you're done with review/changes, I will make the release. |
|
Hey @cvas22, I saw that #163 is merged and master is now at 1.7.0. Are you planning to publish it soon? Can we do a sync on the final release checks. I will do the package verification post publishing. Happy to coordinate so we don't duplicate anything. Sorry I did not time last weekend to review the merged PRs but I have bandwidth after Thursday this week. |
|
@cvas22 - I was tied up over the weekend, but I'll finish reviewing the 1.7.0 changes and leave any comments by Sunday, Nov 22. |
|
@suppagoddo Please review and create a PR if you find any non-breaking issues. Requesting to hold off on deletions (PR 158, PR 162) for this release. Those have regression potential. |
|
I mean, as-in, code changes (non-breaking) that are unlikely to cause any regressions as our install base is pretty wide. 😄 |
Bumps setup.py to 1.7.0 and renames the 1.7.0rc0 changelog heading to 1.7.0, dated today.
Notes
The rc from #161 never got tagged or pushed to PyPI, so I'm going straight to the final release with the same notes. Once this is in I'll tag 1.7.0 and publish it.
Summary by CodeRabbit