Update seacas to 2025-02-27 release

[cticenhour]

Refs #21665

[cticenhour]

@loganharbour Looks like the Versioner output decided to format the "to hash" for this change (067e220) as a number in scientific notation. Odd!

[moosebuild]

Job Documentation, step Docs: sync website on a0f0f33 wanted to post the following:

View the site here

This comment will be updated on new commits.

[moosebuild]

Job Coverage, step Generate coverage on a0f0f33 wanted to post the following:

Framework coverage

Coverage did not change

Modules coverage

Coverage did not change

Full coverage reports

Reports

• framework
• chemical_reactions
• combined
• contact
• electromagnetics
• external_petsc_solver
• fluid_properties
• fsi
• functional_expansion_tools
• geochemistry
• heat_transfer
• level_set
• misc
• navier_stokes
• optimization
• peridynamics
• phase_field
• porous_flow
• ray_tracing
• rdg
• reactor
• richards
• scalar_transport
• solid_mechanics
• solid_properties
• stochastic_tools
• subchannel
• thermal_hydraulics
• xfem

This comment will be updated on new commits.

[loganharbour]

Will need to rebase due do #30042. otherwise, all good

[cticenhour]

Yeah - I just wanted to see how the testing shook out, since there were some failures last time that I wasn't sure where they were coming from.

[loganharbour]

Yeah - I just wanted to see how the testing shook out, since there were some failures last time that I wasn't sure where they were coming from.

oh, sorry. wasn't a draft so I assumed you were good

[cticenhour]

I think it was un-related, just double-checking. I'll ping you when libMesh goes in and I rebase.

[milljm]

#29884 affects this PR as well. Depending on "who wins".

But because the above PR changes the entire stack, yours will most likely make it in before mine.

[cticenhour]

@milljm Given the exact content of this, I feel that this PR can be merged absolutely whenever. I know you've been waiting on that .GOV PR for a bit now.

[milljm]

The only conflict I can think of, is the scripts/tests/versioner_hashes.yaml file.

Because of the "changes everything" attribute of my PR, I feel we should do those sorts of merges while Next is locked down, as well as being able to merge such a PR early in the day.

TLDR;
I think you should be able to merge your's in ASAP. I'll rebase my PR, and we will try again tomorrow.

[milljm]

👍

[moosebuild]

Job Precheck, step Versioner verify on a0f0f33 wanted to post the following:

Versioner templates

Found 16 templates, 0 failed

Versioner versions

Found 10 packages, 1 changed, 0 failed

package	status	hash	to hash	version	to version
seacas	CHANGE	2dd352c	6.7e+221	2024.08.15 build 2	2025.02.27 build 0

[cticenhour]

@loganharbour this is ready to go!

[milljm]

looks good to me!

[loganharbour]

Good to go whenever you're ready