Skip to content

Conversation

@JuliaRegistrator
Copy link
Contributor

@JuliaRegistrator JuliaRegistrator commented Dec 3, 2025

## Breaking changes

-  Refactor TOML file, most important changes include: there is now a distinction between static, cyclic and forcing input (`[input.static]`, `[input.cyclic]` and `[input.forcing]`) without the need to specify the internal cyclic and forcing variables in a list (only an external name mapping is required), state variables are listed below the `[state.variables]` TOML section and use of more clearly defined TOML output sections.
- Mapping of internal model variable and parameter names based on the CSDMS Standard Names, changing the required names in the TOML file.
- Refactor `SimpleReservoir` and `Lake` structs by introducing a `Reservoir` struct that combines data and functionality of both structs. For the simple reservoir a rating curve type (4) has been added. To represent reservoirs, (natural) lakes or other water storage features that can be represented by the available functionality the common name `reservoir` is used, also for the standard names of associated model variables and parameters.
- Replaced the variables that can exchange through `BMI` (list of model components) by a list of standard names below the `[API]` TOML section.
- Removed default values for the following (sensitive) input parameters: `khfrac`, `kv_0`, `kv`, `f`, `c`, `theta_s`, `theta_r`, `soilthickness`, `canopygapfraction`, `rootingdepth` and `pathfrac`.
- Removed support for one layer models, and therefore also removed the `topog_sbm_transfer__flag` option. With this removal, the default soil layer thickness is set to `[100, 300, 800]`.
- The infiltration capacity of soil, represented by parameter `infiltcapsoil`, is now determined from the actual saturated hydraulic conductivity at the soil surface using parameters `kv_0` and `kvfrac`, better linking it to soil properties. Setting `infiltcapsoil` directly by an external netCDF variable is not supported anymore.
- Removed the `GroundwaterExchange` component that can be used to replace the kinematic wave lateral subsurface flow routing with an external groundwater model (e.g. Modflow).
- Removing of `HBV` and `FLEXTopo` vertical concepts.

The full list of changes can be found in the [changelog](https://deltares.github.io/Wflow.jl/v1.0.0/changelog.html#v1.0.0---2025-12-03) in the documentation.

@github-actions
Copy link
Contributor

github-actions bot commented Dec 3, 2025

Hello, I am an automated registration bot. I help manage the registration process by checking your registration against a set of AutoMerge guidelines. If all these guidelines are met, this pull request will be merged automatically, completing your registration. It is strongly recommended to follow the guidelines, since otherwise the pull request needs to be manually reviewed and merged by a human.

1. AutoMerge Guidelines which are not met ❌

  • This pull request modified at least one file that it is not allowed to modify. It is only allowed to modify the following files (or a subset thereof): W/Wflow/Compat.toml, W/Wflow/WeakCompat.toml, W/Wflow/Deps.toml, W/Wflow/WeakDeps.toml, W/Wflow/Versions.toml

2. Needs action: here's what to do next

  1. Please try to update your package to conform to these guidelines. The General registry's README has an FAQ that can help figure out how to do so.
  2. After you have fixed the AutoMerge issues, simply retrigger Registrator, the same way you did in the initial registration. This will automatically update this pull request. You do not need to change the version number in your Project.toml file (unless the AutoMerge issue is that you skipped a version number).

If you need help fixing the AutoMerge issues, or want your pull request to be manually merged instead, please post a comment explaining what you need help with or why you would like this pull request to be manually merged. Then, send a message to the #pkg-registration channel in the public Julia Slack for better visibility.

3. To pause or stop registration

If you want to prevent this pull request from being auto-merged, simply leave a comment. If you want to post a comment without blocking auto-merging, you must include the text [noblock] in your comment.

Tip: You can edit blocking comments to add [noblock] in order to unblock auto-merging.

UUID: d48b7d99-76e7-47ae-b1d5-ff0c1cf9a818
Repo: https://github.com/Deltares/Wflow.jl.git
Tree: 86a8b25a5042a60e21cf9b54dae6e205820d4ebc

Registrator tree SHA: 50f504d641745716a5b3eabaf681d3a4937d2ae3
@JuliaRegistrator JuliaRegistrator force-pushed the registrator-wflow-d48b7d99-v1.0.0-0f036679af branch from 6bef6f1 to 1b81b0f Compare December 3, 2025 16:14
@vers-w
Copy link

vers-w commented Dec 3, 2025

Is it possible to merge this PR manually? We have moved the Wflow package to a subdir (Wflow) of the repos, but it is not allowed to modify the Package.toml file with this PR.

@JuliaTagBot JuliaTagBot added the AutoMerge: last run blocked by comment PR blocked by one or more comments lacking the string [noblock]. label Dec 3, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

AutoMerge: last run blocked by comment PR blocked by one or more comments lacking the string [noblock]. BREAKING major release

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants