Skip to content
Prev 17762 / 21312 Next

[Bioc-devel] Accessing updated package through Devel and priming package for next release

Have you pushed your changes to git.bioconductor.org? I see

HPAStainR master$ git remote -v
origin	git at git.bioconductor.org:packages/HPAStainR (fetch)
origin	git at git.bioconductor.org:packages/HPAStainR (push)
HPAStainR master$ git pull
Already up to date.
HPAStainR master$ grep Version DESCRIPTION
Version: 1.1.3



?On 3/2/21, 4:50 PM, "Bioc-devel on behalf of Tim Nieuwenhuis" <bioc-devel-bounces at r-project.org on behalf of tnieuwe1 at jhmi.edu> wrote:

    Hello,

    I am the maintainer of the package HPAStainR. We are about to respond to reviewer comments on the package's associated paper, and I am trying to have an updated accessible version of the package for the reviewers to use. I currently have the updated version of the package as version 1.1.4 on the master branch, however when I try to download the developer version of my package with

    install.packages("BiocManager")
    BiocManager::install(version='devel')
    BiocManager::install("HPAStainR")

    I end up downloading the previous devel version of HPAStainR which is version 1.1.3. I am unsure if I did something wrong in either my versioning, git pushes, or in my downloading of the developer version. I know I can just have the reviewers acquire the package through github, but I also want to make sure that these changes are primed to be entered into the next Bioconductor release. Any assistance would be greatly appreciated, and pardon my naivet? on the subject.

    Github repository:
    https://github.com/tnieuwe/HPAStainR

    Many thanks,

    Tim Nieuwenhuis
    4th Year Graduate Student
    Human Genetics
    Halushka Laboratory
    Johns Hopkins University SOM
Message-ID: <BN8PR04MB62410B0C618192CBF7163318F9999@BN8PR04MB6241.namprd04.prod.outlook.com>
In-Reply-To: <MN2PR01MB5600062E3CE9057A68093F36E6999@MN2PR01MB5600.prod.exchangelabs.com>