Conda upgrade package8/15/2023 When a package’s version is not changed, but other metadata or parts of the recipe are changed, increase the build number by 1. Please follow the following guidelines while updating recipes:Īlways use a fork of the feedstock while updating the recipe. Push the branch with changes to your fork on GitHub: git push origin Ĭreate a pull request via the web interface by navigating to with your web browser and clicking the button create pull request. Pushing your changes to GitHub and propose a PR Where are a whitespace separated list of filenames you changed.Ĭreate a commit by git commit -m, where can be updated feedstock to version 1.0.1 Pull in the latest changes into your main branch: git rebase upstream/mainĬreate and switch to a new branch: git checkout -b. Register conda-forge’s feedstock with git remote add upstream įetch the latest updates with git fetch upstream Make sure you are on the main branch: git checkout main This step is only required if you have forked some time ago and your fork is missing commits from the feedstock at conda-forge. Syncing your fork with conda-forges feedstock You now have a clone of the feedstock in under your control.Ĭonnect to the feedstock from your computer by using git clone. Navigate to in your favorite web browser and click the fork button. be replaced by numpy-feedstock.īefore you can submit your first PR, you have to fork conda-forge’s feedstock. Here we assume that you would like to update the feedstock. Example workflow for updating a package ¶ The package’s maintainer should close or merge those PRs for the bot to work correctly for future version updates. The bot stops making version update PRs when the package feedstock has three or more open version update PRs. If you can’t find a version here, then the chances are that the bot couldn’t find it either. These version updates are pending either because an updated version was found, but a PR wasn’t opened yet, or because the bot might have had an error while making the PR. You can also check status of version updates for all the pending version updates. Sometimes the bot may take several hours to search for these updates. This may help maintain packages with frequent requirements changes or specific requirements version pins, however this feature is not as extensively verified and proposed updates should be reviewed. The bot creates updates via inspection of the upstream release and will always update the source section and build version in the recipe metadata.Īs an experimental feature, the autotick bot can also be configured to verify or update the recipe’s requirements for Grayskull-compatible recipes. The source code that gets executed in the loop comes from the cf-scripts repository, which contains the code to detect versions and submit PRs. The regro-cf-autotick-bot continuously searches on a loop for any PyPI releases, GitHub releases, and any other sources of versions when any updates are released. How does regro-cf-autotick-bot create automatic version updates? ¶ Using Github’s hub tool (which conda-forge ships! conda install hub -c conda-forge):Ĭlone the conda-forge feedstock repositoryĬheckout the correct branch with remote: hub pr checkout 12 where 12 is the ID of the PR.Ĭommit and push on this branch, the remote is automatically set up to push to regro-cf-autotick-bot’s fork. If there are multiple remotes with this branch name, you need to first checkout the remote branch and then turn it into a local branch: git checkout regro-cf-autotick-bot/ & git checkout -b Ĭommit and push on that branch, if the remote was not correctly setup, use git push -u regro-cf-autotick-bot. See Which remote URL should I use?įor instructions on using the protocol if you haveįetch the remote: git fetch regro-cf-autotick-botĬheckout the branch of the PR, git should automatically link it to the regro-cf-autotick-bot remote if this is the only remote with a branch of that name. It is not possible to push to a GitHub repository using the This means if you push a version update to a branch and then create a PR, conda packages will be published to before the PR is merged. This means that a maintainer can create branches in the main repo.įor updates, using a branch in the main repo is discouraged because, Forking and pull requests ¶Īll maintainers are given push access to the feedstocks that they maintain. If you need to remove a package, please see the section on marking packages broken. Upload packages which already exist on the conda-forge channel. Note that because of this policy, our upload scripts will refuse to Policy is very important as it increases the reliability and reproducibility of conda environments Maintaining packages ¶ Important notes ¶ Packages on conda-forge are immutable ¶Īs a matter of policy, we do not allow edits or the deletion of packages on conda-forge.
0 Comments
Leave a Reply.AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |