Repository navigation
Conversation
A bot pushes the release branch and opens the release pull request, and neither a push nor a pull_request event fires for a bot using the workflow token, so the 1.0.1 pull request carried no checks at all. Preparing the release ran a single job's worth of tests in passing, which is not the matrix that guards develop. Continuous integration is now callable and takes the ref to test, and the release workflow calls it against the branch it just pushed. Preparing the release no longer runs tests itself, and the pull request is drafted in a separate job that waits for the matrix, so a release that fails the tests never reaches review.
Reset develop after release 1.0.1
The feedstock bot updates the version number and the checksum and nothing else, so a release that changes dependencies needs the recipe corrected by hand. Both releases so far did: 1.0.0 for the move from setuptools to hatchling, 1.0.1 for the pandas lower bound. The guide described the release as finished once develop was reset, and said nothing about conda-forge at all.
#128) MODFLOW 6.8.2 reads SFR packagedata through IDM and keeps HK, ROUGH, and USTRF only as deprecated API aliases, so every SFR model run through modflowapi writes three deprecation warnings to mfsim.lst. The packagedata hk, rough, and ustrf columns are now read from __INPUT__/<model>/<sfr>/BEDK, MANNING, and UPSTREAM_FRAC when libmf6 has those addresses, and from the legacy names otherwise; the column names are unchanged. * adv_input_vars in datamodel.py maps a column to its input context name. * test_sfr_input_context_names checks the addresses, values, and a write that persists into the next stress period, against a small SFR model whose input files the test writes as text; it passes against 6.8.1 and current MODFLOW 6 develop.
SPEC 0 recommends dropping numpy <=2.1.0 (as of 2026 Q3) and pandas <=2.2.0 (as of 2026 Q1), numpy 2.2.0 and pandas 2.3.0 are now the minimum supported versions
SPEC 0 recommends dropping Python 3.11 as of 2025 Q4, leaving 3.12 as the minimum supported version
wpbonelli
marked this pull request as ready for review
November 2, 2026 17:13
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Release 1.0.2
The release can be approved by merging this pull request into
main. This will tag anddraft a GitHub release, publish the package to PyPI, and open a follow-up pull request
resetting
developfrommainwith the version incremented.Changelog
Bug fixes