`eo-version-up` workflow neglects to update `home-tag.txt`, causing build failures similar to #982

[morphqdd]

What happens

.github/workflows/eo-version-up.yml (lines 21-24) bumps only eo-version.txt when a new objectionary/eo release comes out. home-tag.txt is never touched by any workflow (grep -rn "home-tag" .github/ finds nothing).

Git history confirms the automated bump commits touch a single file:

$ git log --oneline -12 -- eo-version.txt
bacf6a2 new version of eo maven plugin
1c20008 new version of eo maven plugin (#975)
9031991 new version of eo maven plugin
...
$ git log --oneline -12 -- home-tag.txt
(none of the above commits appear here)

This is exactly the situation issue #982 diagnosed: "eo-version.txt was bumped to 0.61.0 in commit 9031991 while home-tag.txt stayed at 0.59.7", which broke the itest build. That issue was closed by manually realigning the two files by hand, but the workflow that caused the drift was never changed, and there is still no CI guard asserting the two files agree.

What should happen

Either eo-version-up.yml should bump home-tag.txt alongside eo-version.txt in the same commit, or a CI check should fail the build when the two files disagree. As it stands, the next automatic version bump will reintroduce the exact failure #982 already diagnosed once.

[morphqdd]

@yegor256, please take a look when you have a moment.

[0crat]

@morphqdd Thanks for reporting a new bug! You've earned +12 points. By reporting bugs, you help our project improve its quality. If you find anything else in the repository that doesn't look as good as you might expect, do not hesitate to report it. Your running score is +6543; don't forget to check your Zerocracy account too).