module-versioning

Set the version in the Module Builder designer via the Module Settings stereotype's Version property, then run the Software Factory to regenerate the .imodspec file. Confirm with get_file_diffs that only the version line changed.

The Software Factory only writes the version when the designer value sorts strictly higher than the one on disk; a lower value is skipped silently. Hand-edit the .imodspec version line down to a safe value, then set your target version in the designer and regenerate.

Most of .imodspec is hand-authored by design, but six elements—including version, summary, description, iconUrl, id, and migrations—are owned by the Software Factory. Hand-editing those is silently discarded on the next run.

Update the Component Module's Version in metadata.iatspec for architecture templates after confirming publication via search_available_modules, and update the dependency version attribute in other modules. Keep .csproj NuGet package versions aligned to avoid NU1605 errors.

Do not use it to decide whether, when, or which component should receive a version bump—that decision belongs to the module-version-increment skill. This skill only executes a specific version string already supplied by the caller.