Replies: 1 comment
-
Product and release names are the only unique identifiers on endoflife.date so far. They are not guaranteed to stay unchanged, but we try to minimize such breaking changes so they are relatively stable. Note that we're currently thinking about how to handle such changes, see https://github.com/endoflife-date/endoflife.date/wiki/Breaking-Changes. I recently updated the constraints on product and release names, so I had to perform many changes (see #7340). That's what you observed with the samsung renames. Now that this is done you should not observe many changes if the future. If by release data you refer to https://github.com/endoflife-date/release-data, such data is internal to endoflife.date and we make no promise on the schema. If you need something stable consider using our official API : https://endoflife.date/docs/api/v1/. We guarantee no breaking change on the API specification. There may be non-breaking changes though, such as the addition of new fields. If you used our "old" API it's still there and won't be removed anytime soon. But if you'd like to migrate to the new API see https://github.com/endoflife-date/endoflife.date/blob/master/CHANGELOG_API.md. |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
We are storing the EOL Data in a DWH with historization and we would need unique identifieres for the product and releases which are not changing. Actually we are trying product name and release name but I am recognizing changes e.g. "galaxy-s10 plus" was renamed to "galaxy-s10+".
As well I was searching for an entry regarding EOL API itself in the release data. Basically I want to know how long the actuall api version of EOL + schema structures are guaranteed to stay unchanged.
I found similary requests regarding ids in
Beta Was this translation helpful? Give feedback.
All reactions