Skip to content

Set the version back to 1.5.2 for the release tag - #183

Closed
mgrossmann wants to merge 1 commit into
release-1.5.xfrom
release-1.5.2-version
Closed

mgrossmann wants to merge 1 commit into
release-1.5.xfrom
release-1.5.2-version

Conversation

@mgrossmann

Copy link
Copy Markdown
Contributor

Closes #182

release-1.5.x is at 1.5.2-rc1 since #181. release3.yml refuses a tag that does not match [project] version, so v1.5.2 cannot be built from that tree. This sets version = "1.5.2"; the head of release-1.5.x after the merge is the tag commit.

Only mbt.toml changes, one line. FMID TUFS152 and DELETE(TUFS151) are explicit and unchanged.

Checked locally on this branch: mbt ci-info reports PROJECT_VERSION=1.5.2; mbt package builds ufsd-1.5.2-{load.xmit,samplib.xmit,alloc.jcl,inst.jcl,dist.zip,dist.tar.gz,lib.tar.gz} with FMID TUFS152; tools/check-module-data.py is clean. Against ufsd-1.5.2-rc1 the shipped JCL differs only in the version text.

Docs: none.

release3.yml refuses a tag that does not match [project] version, and v1.5.2-rc1 is published. With 1.5.2 in the tree the release tag v1.5.2 can be built from the head of release-1.5.x. Only mbt.toml changes; FMID TUFS152 and DELETE(TUFS151) are explicit and stay as they are.

Refs #182
@mgrossmann mgrossmann added this to the 1.5.2 milestone Oct 27, 2026
@sonarqubecloud

Copy link
Copy Markdown

@mgrossmann

Copy link
Copy Markdown
Contributor Author

Superseded: the release is cut with mbt release 1.5.2 --next 1.5.3-dev on release-1.5.x, which sets the version itself. This PR is not needed.

@mgrossmann mgrossmann closed this Oct 27, 2026
@mgrossmann
mgrossmann deleted the release-1.5.2-version branch October 27, 2026 05:21
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant