Update submodules for 2026.01.beta1 release

[singhd789]

Release Versioning Procedure

Note: fre-cli and fre-workflows are versioned together. When fre-cli deploys a new release, a corresponding release is deployed in fre-workflows.

Checklist

fre-workflows changes

• 1. Update the package release number in the fre-workflows repository:

  • Edit FRE_VERSION in flow.cylc

• 2. Create corresponding tag in fre-workflows (See fre-cli changes (4) for how to tag)

fre-cli changes

• 3. Verify that git submodules in the fre-cli reflect the latest state (or certain commit/tag) of the upstream repositories.

  • If not, consult the manager of the upstream repository and determine whether the update should be included in this FRE release.
  • If so, ask the sub-project maintainer to tag the upstream repository

  Open a PR to commit the submodule updates in fre-cli, solicit a review, and merge the PR.

  • Submodules:
    • fre/gfdl_msd_schemas
    • fre/mkmf
    • fre/tests/test_files/cmip6-cmor-tables
    • fre/tests/test_files/cmip7-cmor-tables

  Note: The release schedules of these submodules may vary from that of fre-cli

• 4. Create a tag in the fre-cli repository (testing tag or release tag)

  Locally this can be done with:

  git tag -a <release>
  git push origin <tag name>
  

  • For the testing tags, follow the structure: [year].[major].[minor].[testing tag]

    • [year].[major].[minor].alpha[iteration]: alpha tags include major code breaking changes
    • [year].[major].[minor].beta[iteration]: beta tags include releases candidates for testing

  • For the full release tag, follow the structure: [year].[major].[minor]

  After the tag is pushed, CI will trigger the creation of a PR changing any reference to the previous tag with the new tag.
  Verify the tagged release is present here

• 5. For a full release (only), create a the github release associated with the correct tag and generate the release notes.

  • In the release notes, be sure to link any alpha and beta tags that were tested for the release

• 6. Navigate to noaa-gfdl conda channel and verify that the last upload date corresponds to the date of this release and that the release number is correct.

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 82.03%. Comparing base (bb9919c) to head (92ec481).

Additional details and impacted files

@@           Coverage Diff           @@
##             main     #911   +/-   ##
=======================================
  Coverage   82.03%   82.03%           
=======================================
  Files          67       67           
  Lines        3736     3736           
=======================================
  Hits         3065     3065           
  Misses        671      671           

Flag	Coverage Δ
unittests	82.03% <100.00%> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

Files with missing lines	Coverage Δ
fre/__init__.py	100.00% <100.00%> (ø)

---

Continue to review full report in Codecov by Harness.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update bb9919c...92ec481. Read the comment docs.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

[ceblanton]

looks great, thank you