Skip to content

Release fireSense 1.1.0 - #2

Merged
eliotmcintire merged 8 commits into
mainfrom
development
Oct 8, 2026
Merged

eliotmcintire merged 8 commits into
mainfrom
development

Conversation

@eliotmcintire

@eliotmcintire eliotmcintire commented Oct 8, 2026 •

Copy link
Copy Markdown
Contributor

This releases the fireSense parent module as 1.1.0, the first release of the fireSense family as one set. The parent's list of child versions now names the release of each module, so fireSense@v1.1.0 will load exactly these releases.

Affects: projects can list PredictiveEcology/fireSense@v1.1.0 to load this set (needs SpaDES.project >= 1.2.0.9013); @main and @development behave as before.

Technical details
  • Version 1.0.0.9000 -> 1.1.0 in fireSense.R; its version list names the released child versions (ELFs 1.2.0, dataPrepFit 1.3.0, ignitionFit 1.2.0, spreadFit 1.2.0, dataPrepPredict 1.1.0, ignitionPredict 1.2.0, spreadPredict 1.2.0, burn 2.2.0) and fireSense_summary 1.0.5, the version on modsForFireSense.
  • Depends-on behaviour, not code: getModule(): a parent at a version tag fetches each child at its listed version SpaDES.project#193 makes a child of a parent at a version tag come at v<its listed version>. Without it, fireSense@v1.1.0 asks each child for its own v1.1.0, which seven of them lack.
  • fireSense_summary@modsForFireSense names its own branch, so it is not pinned.
  • README.md and NEWS.md describe this.
  • To be merged with a merge commit; then tag v1.1.0 and the release, and check with SpaDES.project::getModule("PredictiveEcology/fireSense@v1.1.0").

🤖 Generated with Claude Code

https://claude.ai/code/session_01QewQ83bbo8r7SW4WceE29U

eliotmcintire and others added 5 commits September 29, 2026 14:25
childModules are plain names, so SpaDES.project fetches each from the parent's
account and branch: fireSense@development gives every child's development branch,
fireSense@main every child's main. fireSense_summary keeps modsForFireSense. A
module listed in setupProject(modules = ) overrides the parent's entry for it.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01CwcjqqK59FmTJscyi7xUqv
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01CwcjqqK59FmTJscyi7xUqv
…ent-branch

Children follow the parent's account and branch
@eliotmcintire eliotmcintire added enhancement New feature or request backwards compatible Existing code and results keep working unchanged labels Oct 8, 2026
SpaDES.project >= 1.2.0.9013 (PredictiveEcology/SpaDES.project#193) fetches
a child of fireSense@v1.1.0 at v<its version in this list>, so the family
tag fireSense-1.1.0 is no longer needed.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01QewQ83bbo8r7SW4WceE29U
@eliotmcintire eliotmcintire changed the title Release fireSense 1.1.0 (family tag fireSense-1.1.0) Release fireSense 1.1.0 Oct 8, 2026
test-metadata.R:24 expected exactly "1.0.0.9000", so every version bump
failed it (the 1.1.0 release did). It now checks that the parent's version
is valid and that every child has a valid version in the list, which
SpaDES.project uses to fetch children of fireSense@v<x>.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01QewQ83bbo8r7SW4WceE29U
@eliotmcintire
eliotmcintire merged commit 089b593 into main Oct 8, 2026
7 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

backwards compatible Existing code and results keep working unchanged enhancement New feature or request

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant