Release nudge: ForecastEnsembles has 101 unreleased commit(s) on main

[github-actions]

Release nudge

Released version: none found (no prior release or registry entry) Could not determine the version registered in the General registry (unregistered, or the lookup failed); showing Git tag information only.

Project.toml version: 0.1.0-DEV

main has 101 commit(s) since the first commit (no release found yet) that are not yet released.

Most recent commits:

• d908b42 Merge pull request ci: add registrability and release-nudge workflows #33 from epiforecasts/chore/add-registrability-nudge
• 3881b3a ci: add registrability and release-nudge workflows ahead of release
• efd8e6e Merge pull request chore: depend on registered EpiAwarePackageTools 0.3 instead of the git main pin #32 from epiforecasts/chore/ept-registered-dependency
• ac93c56 Drop stale [sources]-pin comments now EpiAwarePackageTools is registered
• 5ef61d1 Remove stale git-pin comment from benchmark [sources]
• 8753d9b Bump the R package SystemRequirements to Julia >= 1.11
• 1fbbb8f Merge remote-tracking branch 'origin/main' into chore/ept-registered-dependency
• 5827228 ci: pin the review workflow to a current model (the action default was retired)
• b993b2d Bump the R bridge and R-CI to Julia 1.11 to match the package floor
• 5e22403 Drop Julia 1.10/LTS to match the registered kit (require Julia 1.11)

Does the version need bumping?

Project.toml is already ahead of the released version; only registration is outstanding.

What to do

1. If a version bump is still needed, comment the slash command /version patch, /version minor, or /version major (whichever applies) on the pull request that should ship next. The Version On Demand workflow commits the bump onto that PR branch.
2. Update NEWS.md with a summary of the unreleased changes, then merge that pull request into main. The Register workflow and the /register slash command always act on main's current HEAD commit, never on a PR branch, so the bump must land on main first.
3. Once main carries the version to release, either comment the slash command /register on an issue or pull request, or run the Register workflow manually from the Actions tab.

No DOCUMENTER_KEY

This repository has no DOCUMENTER_KEY secret, so TagBot will tag with the Actions app token. GitHub raises no push event for such a tag, so the release will publish no versioned docs, and a tagged commit that touches a workflow file is refused outright. Add the deploy key before releasing: https://epiawarepackagetools.epiaware.org/dev/getting-started/infrastructure#documenter-key