What how this URL should look like?
The URL can look any way you like, provided that it is consistent with the production rules defined in RFC 3986.
You'll probably want a range of resource identifiers, where the resources vary by release date alone. That suggests that you want to use an identifier pattern that you can describe using a URI template.
If users interact with your resources using a web browser, then you'll likely want URI that work the way that HTML forms expect, with application/x-www-form-urlencoded key value pairs as the query part.
For long lived resources, you'll want URI that doesn't need to change - see this guidance from TBL in 1998
But beyond simple mechanical rules like these, the machines don't care what spelling conventions you use -- so you should choose spellings that make the life easier for some humans you care about (ie: choosing a spelling that meets the needs of OPS reviewing an HTTP access log, or choosing a spelling that is easy to document, or choosing a spelling that is easy to recognize in a browser history....)
For the release date part, you'll probably want the date fields to match one of the ISO 8601 formats; for example, see the documentation for java.time.format.DateTimeFormatter.
If the HTML use case is important, then make sure you review date inputs.