-c conda-forge lipid17.xml does not match GitHub version

[MiloszGrabski]

Hi,
I was investigating issues I had running bespoke membranes and discovered that conda distributed lipid17.xml version does not match the github version.
To be sure I have created a fresh environment.
conda create -n openmmforcefields -c conda-forge openmmforcefields
The version installed by conda-forge is marked as 0.14.2, so would match github version.

I have checked files and they do not match.

The GitHub version header of lipid17.xml is:
https://github.com/openmm/openmmforcefields/blob/main/openmmforcefields/ffxml/amber/lipid17.xml

    <DateGenerated>2025-04-30</DateGenerated>
    <Source Source="oldff/leaprc.lipid17" md5hash="52abaf4be36f148c288fada7d8ab0752" sourcePackage="AmberTools" sourcePackageVersion="24.8">oldff/leaprc.lipid17</Source>

Whereas one distributed is:
...\conda\envs\openmmforcefields\lib\python3.13\site-packages\openmmforcefields\ffxml\amber

  <Info>
    <DateGenerated>2021-01-26</DateGenerated>
    <Source Source="leaprc.lipid17" md5hash="1b1941936011f6f0089a47b809331723" sourcePackage="AmberTools" sourcePackageVersion="20.15">leaprc.lipid17</Source>

Not sure if this is done on purpose.

[mattwthompson]

I don't think this is an accident - the main branch is typically ahead of the most recent release. In this case is was a particularly large change that is not yet in a release: https://github.com/openmm/openmmforcefields/pull/368/files

If you point GitHub to the tag of the most recent release you can see that the contents of the conda packages match what are meant to be associated with the release (note the slight difference in URLs): https://github.com/openmm/openmmforcefields/blob/0.14.2/openmmforcefields/ffxml/amber/lipid17.xml