Skip to content

Commit

Permalink
Update version
Browse files Browse the repository at this point in the history
  • Loading branch information
susannasiebert committed Mar 7, 2018
1 parent e416d42 commit 7e1567a
Show file tree
Hide file tree
Showing 3 changed files with 21 additions and 8 deletions.
2 changes: 1 addition & 1 deletion docs/conf.py
Original file line number Diff line number Diff line change
Expand Up @@ -69,7 +69,7 @@
# The short X.Y version.
version = '1.0'
# The full version, including alpha/beta/rc tags.
release = '1.0.1'
release = '1.0.2'

# The language for content autogenerated by Sphinx. Refer to documentation
# for a list of supported languages.
Expand Down
25 changes: 19 additions & 6 deletions docs/index.rst
Original file line number Diff line number Diff line change
Expand Up @@ -38,12 +38,25 @@ New in version |release|

This is a hotfix release. It fixes the following issues:

- Additional data, like example data and VEP plugins were not included in the
package correctly so the commands to download these files would fail. This
has been corrected.
- Class II predictions would fail if the protein sequences used for binding
predictions in IEDB were shorter than 15 peptide sequences. This has been
fixed.
- The epitope length used for generating the peptide fasta when running with
multiple epitope lengths was incorrect. This would potentially result in including
fasta sequences that were shorter than the largest epitope length which
would cause an error during calls to IEDB.
- pVACseq would fail with a nondescript error message if the input VCF was not
annotated with VEP before running. A more descriptive error message has been
added.
- IEDB changed the format of class II IEDB alleles which would cause an error
when running with those alleles. pVACtools will now handle transposing the
affected alleles into the new format.
- The standalone binding filters had a few bugs that would result in syntax
errors during runtime.
- The indexes created for each fusion entry with pVACfuse had the potential to
not be unique which would result in parsing errors downstream.
- pVACseq had the potential to use the incorrect VEP allele for positions with
multiple alternate alleles which would result in the incorrect CSQ entry
getting used for some of those alternate alleles.
- pVACseq would throw an error if the chosen peptide sequence length exceeds
the wildtype protein sequence length of a transcript.

Coming soon
-----------
Expand Down
2 changes: 1 addition & 1 deletion setup.py
Original file line number Diff line number Diff line change
Expand Up @@ -45,7 +45,7 @@

setup(
name="pvactools",
version="1.0.1",
version="1.0.2",
packages=["tools", "tools.pvacfuse", "tools.pvacvector", "tools.pvacseq", "lib", "utils.pvacapi", "utils.pvacapi.controllers"],
entry_points={
"console_scripts":[
Expand Down

0 comments on commit 7e1567a

Please sign in to comment.