-
Notifications
You must be signed in to change notification settings - Fork 45
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
v1.4.4 Release PR #998
v1.4.4 Release PR #998
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
lgtm
I see that the automated build is bundling MM 4.2.1 rather than the current 4.2.2. Also the .version files in RS and RS+ need updating to v1.4.4 just prior to merging. Should probably have referred to the release documentation: https://github.com/PorktoberRevolution/ReStocked/wiki/Release-Procedure 😄 |
Opened PR with MM 4.4.2 updates to build config files. Ready to be merged once MM 4.4.2 is confirmed to be available on distribution platform to be included. |
* Update ReStock build config file for MM 4.4.2 * Update ReStock Plus build config file for MM 4.4.2
Unfortunately, I think Nertea has to give us merge authorisation for the prod branch before we can proceed with this, @drewcassidy. I have spoken to him last week about this and other bits of the build process but he is understandably very busy right now. 😄 |
Not sure why this is failing now in 1877cec compared to c6cf162. Seems to be linked to https://github.com/post-kerbin-mining-corporation/build-deploy/blob/master/src/ksp_deploy/helpers.py#L26 |
It was complaining in the past about a deprecation in the python library, and I guess Nert never pinned the version so eventually it used one where it needs |
I resolved the issue with the package |
It also seems that the external MM reference worked to download and bundle with the package:
So that's good news. Thank you for fixing the above python library issue. If there are no further issues for this release, could drewcassidy and I get merging authorisation so that we can push releases going forward, please? |
The only outstanding issue I foresee could be fixed prior to the next build release could be #997 but there is a fair bit of transform repositioning to fix the issue.
Would there be anything else that anyone would like to include before the next build?