Skip to content

CI updates #104

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
maddenp-cu merged 3 commits into from
Feb 13, 2026
Merged

CI updates #104

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
8f52f6d
Update release procedure in README.md
maddenp-cu Feb 13, 2026
21cb7d5
Add channels to conda create command
maddenp-cu Feb 13, 2026
cfa3f6a
Simplify test.sh
maddenp-cu Feb 13, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
19 changes: 1 addition & 18 deletions .github/scripts/test.sh
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,26 +1,9 @@
. $(dirname ${BASH_SOURCE[0]})/common.sh

run_tests() {
echo TESTING PYTHON $PYTHON_VERSION
env=python-$PYTHON_VERSION
devpkgs=$(jq .packages.dev[] recipe/meta.json | tr -d ' "')
conda create --yes --name $env --quiet $devpkgs
conda activate $env
conda install --yes python=$PYTHON_VERSION
set -x
git clean -dfx
pip install --editable src # sets new Python version in entry-point scripts
make test
status=$?
set +x
conda deactivate
return $status
}

SUPPORTED_PYTHON_VERSIONS=( 3.13 )

ci_conda_activate
for version in ${SUPPORTED_PYTHON_VERSIONS[*]}; do
PYTHON_VERSION=$version
CONDEV_SHELL_CMD=run_tests condev-shell
done
CONDEV_SHELL_CMD=run_tests condev-shell
13 changes: 7 additions & 6 deletions README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -430,12 +430,13 @@ In the GitHub web interface:

1. Click **Releases**.
2. Click **Draft a new release**.
3. Set **Target** to `main`.
4. Click **Choose a tag**, then enter the version number with a "v" prefix, e.g. `v1.2.3`. Click **+** below the text-entry field to create the new tag when the release is published.
5. Set **Release title** to match the tag (e.g. `v1.2.3`).
6. Click **Generate release notes** to pre-populate the release-description text box.
7. Edit the pre-populated notes. Follow the style established in previous release notes.
7. Click the green **Publish release** button.
3. Click **Tag: Select tag**, enter the version number with a "v" prefix, e.g. `v1.2.3`, then click **Create new tag**. The pop-up that appears should inform you that the tag will be created on publish. Click **Create**.
4. Ensure that **Target** is set to `main`.
5. Enter the tag value (e.g. `v1.2.3`) as the **Release title**.
6. Click **Generate release notes**.
7. Edit the **Release notes** text box, follwing the style established by previous release notes.
8. Ensure that **Set as the latest release** is selected.
9. Click the green **Publish release** button.

### Publish a conda Package

Expand Down