Update PSReadLine to 2.0.0-beta3#7711
Conversation
anmenaga
left a comment
There was a problem hiding this comment.
This seems to be a common pattern:
A dependency package releases a new version, and in-response every time we have to: 1) learn about it 2) manually update our stuff by a PR like this one.
I'm curios if (at least) the discovery part can be automated...
|
I've restarted failed 'PowerShell-CI-macos'. |
|
@anmenaga in this particular case, I worked with Jason to publish beta3. I agree that we could have some automation to detect new versions were published and we can decide if we should move to it. |
|
@anmenaga @SteveL-MSFT We already have #7661. |
Update PSReadLine shipped with PSCore6 to 2.0.0-beta3
Renovate has (experimental?) support for Nuget: https://renovatebot.com/docs/nuget/ |
|
@felixfbecker We can rarely take anything but revsion updates without making at least packaging changes (at least for windows). Can Renovate be configured to only take revision changes? |
|
What is a revision update? I know you can configure it only update patch/minor/major versions with npm, but I haven't tried with nuget. |
|
Yeah, I think Renovate/SemVer calls it patch. Sorry, I'm used to calling it revision. I found https://renovatebot.com/docs/configuration-options/#updatetypes, but I also found that it can create separate PRs for each type, which may be a better option. |
|
Currently Renovate classifies both patch version updates (e.g. You could configure Renovate to either:
|
|
Yeah usually you just let it open its PRs, if CI passes, you can merge directly (you can even configure Renovate to automerge if you are confident in your tests), if it doesn't, you can make manual edits on the branch before merging. |
|
I've enabled Renovate on a mirror of this repository so that you can see how it looks without needing to install it directly. Here's an example PR: https://github.com/renovate-mirrors/PowerShell/pull/2 |
PR Summary
Update PSReadLine shipped with PSCore6 to 2.0.0-beta3
cc @edyoung @jianyunt
PR Checklist
.h,.cpp,.cs,.ps1and.psm1files have the correct copyright headerWIP:to the beginning of the title and remove the prefix when the PR is ready.[feature]if the change is significant or affects feature tests