Closed cwschilly closed 10 months ago
@nlslatt @ppebay Should I create an issue for the dependabot PR to fix (in hindsight) and then rebase/rename the commit?
The other failing pipeline is because the branch of this PR is develop
@nlslatt @ppebay Should I create an issue for the dependabot PR to fix (in hindsight) and then rebase/rename the commit?
The other failing pipeline is because the branch of this PR is
develop
@lifflander?
@nlslatt @ppebay Should I create an issue for the dependabot PR to fix (in hindsight) and then rebase/rename the commit? The other failing pipeline is because the branch of this PR is
develop
@lifflander?
I think it's worth doing that although it will break everyone's develop if we force push to it.
@nlslatt @ppebay @lifflander This should be ready to go now; the only remaining failure is because the branch name is not formatted correctly
I was going to ask if we updated the version number in the VERSION
file mentioned in the LICENSE
file, but it seems we don't have one yet. We should probably create one before merging into master.
I was going to ask if we updated the version number in the
VERSION
file mentioned in theLICENSE
file, but it seems we don't have one yet. We should probably create one before merging into master.
I have created a VERSION file in PR #473
@ppebay @nlslatt @lifflander We've now merged all relevant PRs to v1.0.1 -- once we merge this PR I can go ahead with the release
I think only either @lifflander or @nlslatt can merge this PR
Fixes #468