-
Notifications
You must be signed in to change notification settings - Fork 5
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
Newer snakemake version #12
Comments
See also snakemake changelog |
xref #6 (comment) |
Hi @amakunin, please feel free to make a PR with an upgrade to the snakemake version. If you want to also upgrade other packages while you are at it, that would also be fine, equally fine if you just want to upgrade snakemake and leave other upgrades for later. |
Hi @alimanfoo. On it. Still, I cannot push to the binder repo. Could you give me the writing rights? |
@amakunin I've given vector-core write permissions and Resource Centre read. Hopefully you can now push - let me know if not |
Thanks @podpearson. I gave @malariagen/resource-centre write too, in case anyone outside vector-core wants to make a PR. FWIW this repo is public and so you can also fork it to your own account and make a PR from there. But also happy for PRs to come in from branches within malariagen/binder. And also makes sense for others to have write access so they can merge PRs (e.g., @podpearson, @hardingnj, @amakunin, happy for you to merge PRs). |
Hi @alimanfoo @hardingnj
Just realized I was using a newer version of snakemake for my workflows. The newest version is
snakemake=5.3.1
, which seemingly has CWL export option. But feature that I used (directory
output type) was added insnakemake=5.2.0
. Can we update the environment.yml:L51 to either of those?As a side-effect it might be needed to introduce a couple of changes in the pipelines, as the
directory
usage is not backwards compatible, i.e. mandatory in newer versions and cannot be used in older versions.Here's the line: https://github.com/malariagen/binder/blob/7c0086d14bbdf6d0e3bbf18f55cc2df1e8801238/environment.yml#L51
The text was updated successfully, but these errors were encountered: