Skip to content

CONDA-FEEDSTOCK.md

Latest commit

 

History

History
121 lines (81 loc) · 3.03 KB

CONDA-FEEDSTOCK.md

File metadata and controls

121 lines (81 loc) · 3.03 KB

CONDA-FEEDSTOCK.md

This note is for maintainers. It explains how to bump the conda-forge/monitors4codegen-feedstock to publish a new version.

Throughout this document, replace 0.0.X with your target version and v0.0.X with the corresponding Git tag.

0) Prerequisites (in the main repo)

  1. Bump the version in pyproject.toml to 0.0.X.

  2. Push a matching Git tag:

    git tag -a v0.0.X -m "monitors4codegen v0.0.X"
git push origin v0.0.X

1) Fork and clone the feedstock

  1. Fork conda-forge/monitors4codegen-feedstock to your account/org.

  2. Clone your fork and add the upstream remote:

    git clone https://github.com/<your-user-or-org>/monitors4codegen-feedstock.git
cd monitors4codegen-feedstock
git remote add upstream https://github.com/conda-forge/monitors4codegen-feedstock.git
git fetch upstream

  3. Create a bump branch from the current conda-forge main:

    git checkout -b bump-0.0.X upstream/main

2) Compute the sha256 for the tagged source tarball

Use the GitHub tag tarball for the new version:

curl -L "https://github.com/Software-Analytics-Visualisation-Team/monitors4codegen/archive/refs/tags/v0.0.X.tar.gz" | openssl dgst -sha256
# Output looks like: (stdin)= <SHA256_HASH>

Alternative (if openssl is not available):

python - <<'PY'
import hashlib, urllib.request
u="https://github.com/Software-Analytics-Visualisation-Team/monitors4codegen/archive/refs/tags/v0.0.X.tar.gz"
print(hashlib.sha256(urllib.request.urlopen(u).read()).hexdigest())
PY

3) Edit recipe/meta.yaml

Update version, source URL (it points to the tag tarball), and sha256. For a version bump, reset build: number to 0.

{% set name = "monitors4codegen" %}
{% set version = "0.0.X" %}

package:
  name: {{ name }}
  version: {{ version }}

source:
  url: https://github.com/Software-Analytics-Visualisation-Team/monitors4codegen/archive/refs/tags/v{{ version }}.tar.gz
  sha256: <PASTE_SHA256_FROM_STEP_2>

build:
  number: 0
  noarch: python

# ...rest of the recipe unchanged...

4) Commit, push, and open the PR

git add recipe/meta.yaml
git commit -m "monitors4codegen: v0.0.X"
git push -u origin bump-0.0.X

On GitHub, click “Compare across forks” and open a PR:

  • base repository: conda-forge/monitors4codegen-feedstock (branch main)
  • head repository: your fork (branch bump-0.0.X)

Add a brief description; let the conda-forge bots run.

5) Verify after merge

Once the PR is merged and the build completes on conda-forge:

conda search -c conda-forge monitors4codegen
conda install -c conda-forge monitors4codegen

Notes & Pitfalls

  • Make sure the Git tag v0.0.X exists before computing the sha256.
  • The source.url in meta.yaml must match that exact tag tarball.
  • Use build: number: 0 for version bumps; increment the build number only for recipe-only changes (no version change).
  • If runtime dependencies changed, update them in meta.yaml.