github.devotd.
ReleaseCoding agents

code-yeongyu/oh-my-openagent v5.1.38 — raised executable file size cap

oh-my-openagent v5.1.38 is a release that raises the executable file size limit which had been blocking npm publication for the Linux build.

Repositorycode-yeongyu/oh-my-openagent ↗

OmO: Just type "mass ulw" keyword with your prompt. Now you are the master of graph engineering.

stars
★ 70.2K
Forks
5.8K
Language
TypeScript
License
NOASSERTION
Latest release
v5.1.38
Read original source ↗View on GitHub ↗

code-yeongyu/oh-my-openagent v5.1.38 is a release addressing the problem where the Linux build hit an executable file size limit and could not publish the main package to npm. According to the release notes, this version includes that change and raises the allowed size for the per-platform shipped executable from 160 MiB to 182 MiB. The repository description mentions typing a "mass ulw" keyword in the prompt and graph engineering, but the point of this release is not that usage style — it is the deployment size limit.

The direct scope of this fix is the size cap that accepts the executable file. The background for the change is that in the previous version the Linux executable exceeded the existing allowed size and therefore could not be published to npm as the main package. Raising the cap adjusts that deployment constraint, and the release notes do not state that any feature was added or that the behavior of an existing feature was changed. So the only new thing to confirm in this version is the change to the size criterion that had been blocking package deployment.

That said, the release information does not give the actual size of the executable or whether the npm deployment succeeded after the change. It also does not say why the executable exceeded the previous limit, nor how much of the raised cap ends up being used. There are no figures indicating that installation or performance changed. Therefore the confirmable conclusion ends there: the allowed size was adjusted from 160 MiB to 182 MiB, and this change alone does not let one conclude that deployment completed or that anything changed for users.