According to the release notes this is a critical update that will change some calls.
I copied the file from 6.2.1 and updated the version number and the database commit hash.
The full diff:
diff tbprofiler/6.2.1/Dockerfile tbprofiler/6.3.0/Dockerfile
6c6
< ARG TBPROFILER_VER="6.2.1"
---
> ARG TBPROFILER_VER="6.3.0"
10,11c10,11
< # this was the latest commit as of 2024-05-10
< ARG TBDB_COMMIT="97b5876a1a9d2f06e8bb6076ed88baf481ef5fe5"
---
> # this was the latest commit as of 2024-08-29
> ARG TBDB_COMMIT="4907915526b52ac2f20f1324613f5d4dc951e0bd"
45,47d44
< # In 5.0.1 updating_tbdb does not work with tb-profiler update_tbdb --commit ${TBDB_VER}
< # ^^ this was resolved in 6.2.1
< #RUN tb-profiler update_tbdb -h && whatever
50d46
<
Pull Request (PR) checklist:
[x] Include a description of what is in this pull request in this message.
[x] The dockerfile successfully builds to a test target for the user creating the PR. (i.e. docker build --tag samtools:1.15test --target test docker-builds/samtools/1.15 )
[x] Directory structure as name of the tool in lower case with special characters removed with a subdirectory of the version number (i.e. spades/3.12.0/Dockerfile)
[x] (optional) All test files are located in same directory as the Dockerfile (i.e. shigatyper/2.0.1/test.sh)
[x] Create a simple container-specific README.md in the same directory as the Dockerfile (i.e. spades/3.12.0/README.md)
[x] If this README is longer than 30 lines, there is an explanation as to why more detail was needed
There's a new version of tbprofiler!
According to the release notes this is a critical update that will change some calls.
I copied the file from 6.2.1 and updated the version number and the database commit hash.
The full diff:
Pull Request (PR) checklist:
docker build --tag samtools:1.15test --target test docker-builds/samtools/1.15
)spades/3.12.0/Dockerfile
)shigatyper/2.0.1/test.sh
)spades/3.12.0/README.md
)