Add releases endpoint

[bilalebi]

Description

Add /releases endpoint which returns all the releases (for now)

Related JIRA Issue(s)

https://www.ebi.ac.uk/panda/jira/browse/ENSWBSITES-2908

Example(s)

Request

/api/metadata/releases

Response

[
  {
    "name": "2023-10-18",
    "type": "partial",
    "is_current": false
  },
  {
    "name": "2024-09-18",
    "type": "partial",
    "is_current": false
  },
  {
    "name": "2024-10-28",
    "type": "partial",
    "is_current": false
  },
  {
    "name": "2023-10",
    "type": "integrated",
    "is_current": true
  },
  {
    "name": "2025-01-16",
    "type": "partial",
    "is_current": true
  },
  {
    "name": "2025-02-28",
    "type": "partial",
    "is_current": false
  }
]

Dependencies

This PR needs to be merged and deployed first: Ensembl/ensembl-metadata-api#128

[azangru]

• If the shape of release here is the same as the shape of release coming out of the /releases endpoint, then shouldn't line 444 just reference the release object on line 1076?
• I am confused about the meaning of the is_current field here. It may mean:
  • that the release itself is current (i.e. latest integrated/partial), or
  • that the genome/release combination is current

[bilalebi]

If the shape of release here is the same as the shape of release coming out of the /releases endpoint, then shouldn't line 444 just reference the release object on line 1076?

Yes, you're right, thank you for pointing that out, I've done the changes

I am confused about the meaning of the is_current field here.

It's the one attached to a release, would you like me to call it somthing more explicit like release_is_current?

[bilalebi]

@azangru as we agreed, this commit cad0c07 removes release is_current from /explain and /details.

FFR: We agreed to remove is_current from those two endpoints for the following reason

• release is_current form a genome perspspective doesn't provide any useful inforrmation
• It's confusing, see the seconfbullet point in the comment above